|
Giant Dwarf
|
March 13, 2018 at 7:45 pm
Upgraded our site to the latest version of EE last Friday, along with the related plugins. Today we experienced a new error on our site that I haven’t come across before.
A customer emailed us saying he encountered an error after making his payment and couldn’t finalise his purchase. Looking at the registrations his booking was marked as abandoned, but the payment was in our account so I manually approved the registration. However, his confirmation emails won’t generate, nor do they appear in the message queue as failed.
Here is the error we have in our logs from his booking:
[Wed Mar 14 04:10:26.522699 2018] [:error] [pid 3409] [client 172.68.144.5:32305] PHP Fatal error: Uncaught Error: Call to a member function email() on null in /var/www/gd2018/wp-content/plugins/eea-mailchimp/includes/EE_MCI_Controller.class.php:208
Stack trace:
#0 /var/www/gd2018/wp-content/plugins/eea-mailchimp/EED_Mailchimp.module.php(198): EE_MCI_Controller->mci_submit_to_mailchimp(Object(EE_Checkout), Array)
#1 /var/www/gd2018/wp-includes/class-wp-hook.php(298): EED_Mailchimp::espresso_mailchimp_submit_to_mc(Object(EE_Checkout), Array)
#2 /var/www/gd2018/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(NULL, Array)
#3 /var/www/gd2018/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#4 /var/www/gd2018/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/finalize_registration/EE_SPCO_Reg_Step_Finalize_Registration.class.php(94): do_action('AHEE__EE_SPCO_R...', Object(EE_Checkout), Array)
#5 /var/www/gd2018/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php(1378): EE_SPCO_Reg_Step_Finalize_Registration-> in /var/www/gd2018/wp-content/plugins/eea-mailchimp/includes/EE_MCI_Controller.class.php on line 208, referer: https://giantdwarf.com.au/buy_tickets/?uts=1520960949
Any ideas what might have caused this error to occur?
|
|
Tony
|
March 14, 2018 at 4:36 am
Hi there,
This isn’t actually an email bug, although the error shows function email() the problem is the code is calling a function on what it expects to be an object when infact its actually nothing (NULL). This is the code in question:
$attendee = $registration->attendee();
$att_email = $attendee->email();
if ( ( $attendee instanceof EE_Attendee ) { .... }
I’ve created a ticket for the MailChimp add-on to confirm it has an object before running functions on it (as you can see above it actually does this right after the above function call, but its too late for that one method above).
However… if you have a registration, you should have an attendee assigned to it at that specific point in the code so this may be a symptom of another problem, do you have caching enabled on the site?
However, his confirmation emails won’t generate, nor do they appear in the message queue as failed.
If they wont generate, what do that show as?
If the registration does not have an attendee object assigned to it that would explain why the messages aren’t generating.
If you go to Event Espresso -> Registrations and find this users registration there, can you see their contact details listed there?
|
|
Giant Dwarf
|
March 14, 2018 at 9:43 pm
G’day Tony, thanks for the feedback. We don’t have caching on the site currently, we’ve opted for Cloudflare instead to take load off the site, though we’ve had that running for about a year or two now and haven’t had an issue.
For the messages, they don’t seem to show anything. Clicking the resend button just reloads the page, searching the message queue shows up nothing, and there’s nothing in the error log.
The contact details do show up, and I’ve had a look in the database at both the attendee (post) entry, the attendee meta and the registration, all of them seem fine as far as I can see, at least in comparison to other entries.
I think for now I’m going to chalk this up to just some gremlin in the setup, as it seems to be a one off. Will let you know though if it happens again.
Thanks!
|
|
Tony
|
March 15, 2018 at 3:49 am
Strange, please do let us know if this comes up again.
With regards to the messages currently sitting in the queue that wont generate, I’d recommend deleting those as EE may continue attempting to generate them on each batch of the message queue, although it really does depend on what status they are sitting on right now.
|
