|
wfinley
|
November 8, 2022 at 5:14 pm
I have a wait list email caught in a loop…. it attempted to send over 1K times and keeps trying. This error popped up over 1K times. What’s going on?
Stack trace:
#0 /home/alaskaav/public_html/wp-content/plugins/eea-wait-lists/domain/services/messages/EE_Recipient_Waitlist_Shortcodes.lib.php(72): EED_Wait_Lists::wait_list_checkout_url(Object(EE_Registration))
#1 /home/alaskaav/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Shortcodes.lib.php(183): EE_Recipient_Waitlist_Shortcodes->_parser(‘[RECIPIENT_WAIT…’)
#2 /home/alaskaav/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php(232): EE_Shortcodes->parser(‘[RECIPIENT_WAIT…’, Object(EE_Messages_Addressee), Array)
#3 /home/alaskaav/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php(72): EEH_Parse_Shortcodes->_parse_message_template()
#4 /home/alaskaav/public_html/wp-content/plugins/event-espres in /home/alaskaav/public_html/wp-content/plugins/eea-wait-lists/domain/services/modules/EED_Wait_Lists.module.php on line 644
[08-Nov-2022 14:16:36 UTC] PHP Fatal error: Uncaught Error: Call to a member function reg_url_link() on null in /home/alaskaav/public_html/wp-content/plugins/eea-wait-lists/domain/services/modules/EED_Wait_Lists.module.php:644
Stack trace:
|
|
Tony
|
November 9, 2022 at 3:06 am
Hi there,
So, the error shown means that the registration the email is being generated for has no ‘Primary Registration’ assigned to it which is unexpected within EE, every registration should return a primary reg.
Do you know which registration this email is being generated for? We can troubleshoot this further if so.
To stop the message trying to generate, go to Event Espresso -> Messages.
At the top of the list table you’ll see some ‘views’ (Links to different messages) to change the view of the table.
Forgot about ‘All’ and ‘Sent’ for the time being, if you view the others, can you see the message sitting there? Based on the error I’m assuming its sitting in ‘Queued For Generating’.
If you fid it there, select it and delete it to stop the message trying to generate and throwing the error.
|
|
wfinley
|
November 9, 2022 at 12:21 pm
Couldn’t find the primary registration that this had been generated for. Perhaps it got deleted after the message was queued for generating?
This has happened to us before. I’ve passed along instruction on how to stop the loop – but sometimes it will be several days before they catch it and we’ll have over a thousand bad emails. Seems there should be a catch to stop this from going in an endless loop.
|
|
Tony
|
November 14, 2022 at 5:40 am
We do catch most errors thrown within the message system and set the message to failed, however, currently, it depends at what point in the request the fatal is thrown.
For the above, it is not expected to have a registration that has no primary registrant assigned to it so the fatal is thrown relatively early during the message generation but I’ll create a ticket to see if we can catch those errors.
|
