|
jessiem
|
May 10, 2021 at 1:45 pm
We are having an issue where our notification emails are not being sent. I have tried setting ‘Generate and send all messages:’ to both options with no luck. The messages are either saying ‘Messenger Is Executing’ or ‘Failed’. When I go to Default Message Templates > Registration Approved > Edit Event Admin then hit the ‘Test Send’ button the screen says ‘There has been a critical error on this website. Please check your site admin email inbox for instructions’. The error message next to the ‘Failed’ messages says ‘Message failed to generate for the following reasons:Incoming data for the Gateways data handler must have an EE_Transaction object as the value for the first array index.’.
|
|
Tony
|
May 11, 2021 at 5:06 am
Hi there,
When you get this message:
“There has been a critical error on this website. Please check your site admin email inbox for instructions.”
Do you get an email with an additional error message in it?
If not can you check your servers error logs (your host will usually have a section you can use to view errors on your site) around the time you are testing the above and see what error is being thrown by Event Espresso?
Did this work previously or is this a new install?
|
|
jessiem
|
May 11, 2021 at 7:51 am
This reply has been marked as private.
|
|
Tony
|
May 11, 2021 at 8:20 am
Note – I marked your reply private as it contains links to your stagin site.
The error posted usually means there is a file missing on your install, I’m assuming you pushed the files from staging to live? (Which would explain why you get that error on both if so)
On the staging site, re-install the Event Espresso 4 plugin.
Download the latest version of EE4 from your account page:
https://eventespresso.com/users/jessiem/
Then on staging go to Dashboard -> Plugins -> Add New -> Upload plugin.
Upload the .zip file you just download from your account page.
(You don’t need to deactivate or delete the current version)
It should say the plugin already exists and then ask if you want to replace the existing version with the new uploaded version, click to do that (if WordPress is updating translations files here, wait until that has finished before clicking).
Once that has done, retest, does that fix it?
|
|
jessiem
|
May 11, 2021 at 1:50 pm
Thank you for marking my reply private. We use a repo and gitlab for our site changes so I have re-uploaded the plugin but there are no differences between what is on our stage and live sites and what is in the plugin I downloaded from my account. So what we have currently is exactly what is in the download and it is not working.
|
|
Tony
|
May 11, 2021 at 2:58 pm
The line throwing the above error is simply:
require_once EE_THIRD_PARTY . 'cssinliner/vendor/autoload.php';
The error is just Error message: require_once(): Failed opening required
The path to the file in that error is correct, so either the file isn’t on the server, or the site doesn’t have permissions to access it (which would be really strange).
I assume you aren’t excluding vendor/* from your repo?
|
|
jessiem
|
May 12, 2021 at 7:06 am
Thank you for your help in troubleshooting this, it looks like we were excluding vendor and although I was seeing that folder in my repo it indeed was not on our server. Looks like all is working now with email notifications.
|
|
Tony
|
May 12, 2021 at 8:20 am
You’re most welcome, any further issues/questions just let us know.
|
