|
wfinley
|
January 7, 2020 at 3:15 pm
This is the same issue as described here: https://eventespresso.com/topic/messages-failing-to-generate/
However… this time we have not deleted anyone and it is still happening. It is related to the wait list manager. Screen shot of the failed msgs here:
https://alaskaavalanche.org/wp-content/uploads/2020/01/screen1.png
And a screenshot of the data for this email here:
https://alaskaavalanche.org/wp-content/uploads/2020/01/screen2.png
|
|
Josh
|
January 8, 2020 at 8:29 am
May I ask were those registrations promoted from wait list, then changed back to wait list status? Normally the “Registration promoted from wait list” message triggers after a registration’s status is changed from wait list to pending payment. The registrations in your screenshot all have status of wait list, so they shouldn’t be getting a “promoted from wait list” email in the first place.
|
|
wfinley
|
January 9, 2020 at 1:25 pm
I think my client may be missing something in the process which is what is causing this. He has Auto Promote Registrants set to yes – and when a spot opens up it automatically sends the message.
I think where things are messing up is that he only leaves the spot open for 24 hours – then he deletes that person and auto-promotes the next.
Is there a way we can set it up so registrations promoted from wait list are only open for 24 hours?
|
|
Tony
|
January 9, 2020 at 3:47 pm
Not automatically but rather than deleting the registrations you could just set them to have a status of cancelled, that should then trigger the next registration in the queue.
|
|
wfinley
|
January 13, 2020 at 12:49 pm
OK it’s happening again. This is the error. It seems the endless loop is when the waitlist is being sent out for an event that doesn’t exist? What’s happening is people are signing up for multiple wait lists (like 10+ waitlists) and when the system auto-promotes one of the people who have signed up for multiple events it signs them up for the wrong (non existing) event. Would that make sense?
Error Details
=============
An error of type E_ERROR was caused in line 644 of the file /home/alaskaav/public_html/wp-content/plugins/eea-wait-lists/domain/services/modules/EED_Wait_Lists.module.php. Error message: 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:
#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(184): 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(234): 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(74): EEH_Parse_Shortcodes->_parse_message_template()
#4 /home/alaskaav/public_html/wp-content/plugins/event-espres
|
|
Josh
|
January 13, 2020 at 1:52 pm
That actually doesn’t make sense because in order to open up spaces for an event, the event needs to exist in the site’s database.
Also, the error message points to this code:
'e_reg_url_link' => $registration->get_primary_registration()->reg_url_link(),
It’d be more likely that they’re deleting the Wait list’s primary registrant, then later other registrants from the same transaction were getting promoted. Instead of deleting some of the registrations (but not all) from the wait list, what they could do instead is cancel the registrations that they no longer want to have on the wait list.
|
