|
KIROS
|
March 15, 2021 at 11:28 am
https://eventespresso.com/wiki/create-a-waiting-list-for-your-event/
I have EE 4.10.10 and am trying to follow instructions above. When I search in WP to find Waitlist plug-in, nothing pops up. Any hints on how to find the plug-in to upload? Thanks!
|
|
Tony
|
March 15, 2021 at 12:34 pm
Hi there,
All of your EE downloads are available on your account page here:
https://eventespresso.com/users/kiros/
In the downloads section click on the add-on to download a .zip of that add-on.
Then install it through Dashboard -> Plugins -> Add new -> Upload plugin.
|
|
KIROS
|
March 15, 2021 at 2:30 pm
I followed all the steps then received the message below. How do I fix this? And why does the plug-in cause a fatal error?
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, Event Espresso – Wait Lists (EE4.9+).
First, visit your website (https://kiros.org/) and check for any visible issues. Next, visit the page where the error was caught (https://kiros.org/wp-admin/admin.php?page=espresso_messages&message_type=waitlist_can_register&messenger=email&context=registrant&GRP_ID=79&action=preview_message&preview_message_nonce=0ee419a33e) and check for any visible issues.
|
|
Tony
|
March 16, 2021 at 5:09 am
Ok, so that’s from previewing the waitlist message type rather than installing the waitlist add-on itself.
Does it show the error being thrown?
If you check the servers error log does it show an error from the waitlist add-on around the time you received that email?
|
|
KIROS
|
March 16, 2021 at 9:52 am
Where do I check the servers error log? What does it mean for the error being thrown? At the same time, I see an error message, an email is sent to me that there is a fatal error, and in EE messages, a message is sent to farfaraway@galaxy.sp:
Message failed to generate for the following reasons:
EE_Messages_REG_incoming_data requires the incoming data argument to be an instance of EE_Registration or an array where the first value is an instance of EE_Registration
|
|
Tony
|
March 16, 2021 at 10:19 am
Where do I check the servers error log?
It depends on how you host has the server set up.
Generally your host will have a section in your control panel to view server errors, if not there may be an error_log (or similar) file within the root directory of your server.
What does it mean for the error being thrown?
Without the error, I can’t give you more specifics.
Message failed to generate for the following reasons:
EE_Messages_REG_incoming_data requires the incoming data argument to be an instance of EE_Registration or an array where the first value is an instance of EE_Registration
That normally means the registration linked to the message has been deleted from the site.
Have you been removing registrations?
In Event Espresso -> Messages -> Message activity, can you see the message causing the error listed there? If so, what message type is it?
|
|
KIROS
|
March 16, 2021 at 10:55 am
In Event Espresso -> Messages -> Message activity, can you see the message causing the error listed there? If so, what message type is it?
Registration Promoted From Wait List Notification
This is the same message I’m working on that receives this: At the same time, I see an error message, an email is sent to me that there is a fatal error, and in EE messages, a message is sent to farfaraway@galaxy.sp:
Message failed to generate for the following reasons:
EE_Messages_REG_incoming_data requires the incoming data argument to be an instance of EE_Registration or an array where the first value is an instance of EE_Registration
I have not deleted any registrations.
|
|
KIROS
|
March 16, 2021 at 12:27 pm
I just retried and the server error log shows nothing. Just the screen error: Fatal error: Uncaught Error: Call to a member function reg_url_link() on null in /home/customer/www/kiros.org/public_html/wp-content/plugins/eea-wait-lists/domain/services/modules/EED_Wait_Lists.module.php:644 Stack trace: #0 /home/customer/www/kiros.org/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/customer/www/kiros.org/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/customer/www/kiros.org/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/customer/www/kiros.org/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php(74): EEH_Parse_Shortcodes->_parse_message_te in /home/customer/www/kiros.org/public_html/wp-content/plugins/eea-wait-lists/domain/services/modules/EED_Wait_Lists.module.php on line 644
|
|
KIROS
|
March 16, 2021 at 1:02 pm
6 messages to farfaraway@galaxy.sp
from: Registration Promoted From Wait List Notification
Error message: Message failed to generate for the following reasons:
EE_Messages_REG_incoming_data requires the incoming data argument to be an instance of EE_Registration or an array where the first value is an instance of EE_Registration
|
|
Tony
|
March 16, 2021 at 1:13 pm
6 messages to farfaraway@galaxy.sp
Anything sending to farfaraway@galaxy.sp is from a preview message and should not be triggering an actual message.
Can I take a quick look in the admin to see if anything stands out here?
If so you can send temp login details using this form:
https://eventespresso.com/send-login-details/
|
|
KIROS
|
March 16, 2021 at 3:17 pm
Just received another email:
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, Event Espresso – Wait Lists (EE4.9+).
|
|
KIROS
|
March 16, 2021 at 4:37 pm
Any update on this? When I click Preview, I still receive this message:
Fatal error: Uncaught Error: ……………….
|
|
Tony
|
March 17, 2021 at 9:52 am
Hi there,
So the issue here is based on how the ‘preview’/’dummy’ data is generated to show you an example of the message. It uses ‘real’ data from your site to build out something that looks familiar to how your event would.
The problem above happens if the very first event created within EE has multiple tickets assigned to a single DateTime, the dummy data sets up in such a way that causes the above error.
This will only affect the message previews and not ‘real’ registrations on the site when sending messages.
You can safely delete the messages shown in the message queue that show farfaraway@galaxy.sp, those are dummy messages and can be removed. I’ve created a ticket to fix this in the next release of Event Espresso but for now you can’t use the preview option to view the waitlist messages.
|
|
KIROS
|
March 17, 2021 at 12:03 pm
Hello, I also receive this error when I try to send a test email. How can I see how this email looks?
Also, when someone signs up for the wait list, will they be listed with all the other registration or in a different location?
|
|
Tony
|
March 17, 2021 at 12:48 pm
Hello, I also receive this error when I try to send a test email. How can I see how this email looks?
Both preview and test send use the same dummy data.
To view how these look, create a test event and set up for the waitlist add-on (Set up a datetime with a limit of 1 and register onto it so the event is sold out) then add a registration to the waitlist. Increase the limit on the datetime and EE will trigger the email for your waitlist registration.
If you are comfortable with PHP there’s a fix I can give you which you can apply to yourself in the meantime if that helps?
Also, when someone signs up for the wait list, will they be listed with all the other registration or in a different location?
Waitlist registrations show up in the same location just with a status of ‘waitlist’.
|
