|
Steve
|
October 7, 2018 at 2:22 pm
Bit of an odd one this – wondering if anyone has any tips?
EE4 is happily sending out registration emails etc for those registering through the front end of the website.
However when I’ve registered people manually, its throwing an error and the emails are not being sent.
Anything I should double check/debug e.g. validation with is skipped?
|
|
Josh
|
October 8, 2018 at 7:21 am
Hi,
May I ask what’s the exact text of the error message it’s throwing?
|
|
Steve
|
October 8, 2018 at 11:43 am
Of course:
So in the messages section when I try to “send now” it throws this:
An error has occurred:
No message was sent because of problems with sending. Either all the messages you selected were not a sendable message, they were ALREADY sent on a different scheduled task, or there was an error. If there was an error, you can look at the messages in the message activity list table for any error messages.
and then if I hit the i icon:
Message was not executed successfully.
Messenger and Message Type were valid and active, but the messenger send method failed.
The email did not send successfully.
The WordPress wp_mail function is used for sending mails but does not give any useful information when an email fails to send.
It is possible the “to” address (removed) or “from” address (info@nyswingfling.com) is invalid.
I’ve confirmed that its with multiple email addresses, and also, multiple email types, including ones which are sending out fine automagically (I did think it was because this was registration pending email and perhaps I did something wonky with the design, but its also with manually raised fully approved registration emails and ticket notices as well). I’ve also tried using both our transactional email service (mailjet) and with mailjet off, with the same outcome.
Happy to debug further if you can give any advice on the best way to do so.
|
|
Steve
|
October 8, 2018 at 2:45 pm
Some other evidence. I’ve just tried to do a ticket change, and I’ve got this error:
Catchable fatal error: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /var/sites/n/nyswingfling.com/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /var/sites/n/nyswingfling.com/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 97
Although this is odd, as again, tickets are going out as normal otherwise.
|
|
Josh
|
October 8, 2018 at 3:30 pm
Do you mean change the registration so it’s for a different ticket price/type, like by using the Attendee mover add-on? That last error message would indicate that a ticket type/price has been deleted from the database, which would be very strange if you had just selected that ticket type when moving that registration to a new ticket.
May I ask does this happen if any ticket types are selected in the admin when adding registrations? or does it only happen with specific ticket types?
|
|
Steve
|
October 8, 2018 at 3:36 pm
I may be conflating two things. That error only is appearing when changing ticket type using the attendee mover add on. The ticket is definitely valid – as the person does actually get moved, but that error is thrown.
Doesn’t throw errors when adding registrations manually via the registrations > add new registration screen
Emails as a result of this are also not being sent, but as mentioned may be unconnected.
|
|
Josh
|
October 8, 2018 at 4:12 pm
The same error may be happening in every case. One thing you could do to help narrow things down is go in and temporarily remove the [TICKET_LIST] shortcode from your active email message templates. So basically anywhere it’s included as outlined in this screenshot:
https://slack-files.com/T02SY781D-FD963M66M-3523a979d2
Then save, then try moving a ticket or adding a registration manually to see if the messages send without that shortcode in place.
|
|
Steve
|
October 12, 2018 at 2:24 pm
Hey Josh,
I’ve removed tis and it indeed does not crash, and the emails go out. Any ideas why this may be happening? Wondering if I’ve run into a bug? I can’t think what config option I’d have changed which could affect this, but perhaps there is one?
|
|
Josh
|
October 12, 2018 at 8:09 pm
That could happen if some data was missing from the database. The error message: parse_ticket_list_template() must be an instance of EE_Ticket, null given, is another way of saying “No ticket found”. The error isn’t related to a specific config option.
May I ask were any tickets or related data changed or edited by making direct edits to the database?
|
|
Steve
|
October 13, 2018 at 8:31 am
Hey Josh,
Not that I have done no, wouldn’t do that as it could corrupt the system.
Of course perhaps with this particular customer something went wrong when creating her registration… eg a data blip in my connection.
Anything I can do to safely run DB maintenance or similar?
|
|
Steve
|
October 14, 2018 at 1:46 pm
Yep, still getting this with a new registration, I created the reg, with an amount to pay, then have the system issue messages, which worked ok. Then when they’ve paid, its throwing this error:
Incoming data for the Gateways data handler must have an EE_Transaction object as the value for the first array index. EE_Messages_Gateways_incoming_data – __construct – 36
|
|
Steve
|
October 14, 2018 at 1:53 pm
interestingly, when I then goto the registration and manually send the ticket notice, it works, but the auto-gen one failed.
|
|
Tony
|
October 15, 2018 at 5:12 am
Hi Steve,
I’ve been running some testing on this and so far I haven’t been able to reproduce so as t stands it doesn’t look like a bug but more like something is altering the request on the server.
However, can you provide a full breakdown of the steps you are taking above?
I want to confirm I’m actually testing the same steps you are using.
|
|
Steve
|
October 17, 2018 at 3:57 pm
Hey Tony,
Thanks for trying. The issue is I’m not really doing anything. I have the latest version of EE, running on the latest version of WP.
What I’m finding is that registration approval, ticket emails are being inconsistently generated. Sometimes they are failing with an error, sometimes they go through fine. Sometimes issuing them again solves the problem, sometimes clicking the spanner in the messages console work. Other times the messages throw errors indicating they have nulls in some of the tables.
I’m trying to work out what the right debug routines are. You’re right, it could be something not he server/webhosting (we’re on TSO Host)… so any tips for how I might be able to trace/track the errors through?
|
|
Tony
|
October 19, 2018 at 5:13 am
Ok, sorry but I’m not sure I follow when this error is happening.
Your opening thread state frontend registrations work fine, but admin registrations do not but then above its seemingly random?
The break down of steps I was referring to is these:
Yep, still getting this with a new registration, I created the reg, with an amount to pay, then have the system issue messages, which worked ok. Then when they’ve paid, its throwing this error:
For example, how are the users paying and how are you applying it to EE?
I’m trying to work out what the right debug routines are. You’re right, it could be something not he server/webhosting (we’re on TSO Host)… so any tips for how I might be able to trace/track the errors through?
We can help narrow this down some, but need to know the steps you take on the site to reproduce the problem, otherwise the we can give you steps that would be a general overview of what is happening, so if you add calls to log functions etc your going to get all kinds of ‘valid’ entries mixed in making it harder to narrow down further.
|
