|
Andy
|
December 12, 2017 at 5:47 am
I upgraded EE4 this morning and now when trying to generate messages get the following error:
An EE_Error exception was thrown! code: EE_Messages_Registrations_incoming_data – __construct – 36
“The EE_Message_Registrations_incoming_data class expects an array of EE_Registration objects.”
click to view backtrace and class/method details
/nas/content/live/****/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/data_class/EE_Messages_Registrations_incoming_data.class.php ( line no: 36 )
|
|
Josh
|
December 12, 2017 at 8:47 am
Hi there,
May I ask how many messages did you try to generate in one request?
|
|
Andy
|
December 12, 2017 at 9:14 am
Hi Josh
Initially it was 3 and the second time was 9.
|
|
Josh
|
December 12, 2017 at 11:07 am
May I ask are you trying to generate the messages from the Event Espresso > Messages > Messages Activity page or from the Event Espresso > Registrations page?
|
|
Andy
|
December 12, 2017 at 1:31 pm
From the Event Espresso > Messages > Messages Activity page
|
|
Josh
|
December 12, 2017 at 3:26 pm
That’s good to know. Along with that, do you know which message types? e.g were they payment reminders, registration approved messages, ticket notifications? If you check the Event Espresso > Registrations page, do the related registrations to those messages have a specific registration status?
We’re looking to try to replicate this issue so the specific information you can reply with will help.
|
|
Andy
|
December 12, 2017 at 4:13 pm
They were all registration approved, either for the registrant or event admin with the exception of one which was a batch email. I took a pdf copy of the additional text which came up when I clicked “click to view back trace and class / method details” if this helps at all.
|
|
Andy
|
December 12, 2017 at 4:30 pm
By way of more information all are custom message types, linked to event registration with the exception of the batch email. On closer examination, some of the messages were set for generation from before the update whilst the rest were after so this may have triggered something?
|
|
Josh
|
December 14, 2017 at 9:01 am
What you could try instead is make a note of the registrations, then delete those messages from the queue, then go to Event Espresso > Registrations and resend the registration details for those registrations.
|
