Posted: September 13, 2024 at 8:59 am
Hi! Activating EE is causing the WordPress Dashboard to crash (it logs me off the Dashboard with this error: “There has been a critical error on this website. Please check your site admin email inbox for instructions.” |
|
Hi there, This:
Is the ‘pretty’ version of a fatal error, WordPress shows that on front end when the error is thrown but your server should log the ‘real’/’full’ error in the error logs. We need that error to be able to troubleshoot this as the above could be related to anything currently.
Thats a “we can’t be bothered helping” kind of answer and personally, would have me questioning if it’s the right host to use. Without the full error I can’t tell you whats happening, but your hosts control panel will often have a section to view PHP errors on the server. Check for those, search for ‘fatal error’, post that here. Do you have FTP/File Maneger access? |
|
This reply has been marked as private. | |
Hmm, ok, strange. Which specific version number of Event Espresso do you currently have installed? I’d like to take a look at this but I’ll need both WP Admin and FTP credentials to troubleshoot, if you are ok with sending those over you can do so using this form: |
|
I completed the form and sent it. Let me know if you need anything else. Thank you. |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
This reply has been marked as private. | |
This reply has been marked as private. | |
Hi there, I’ve updated Event Espresso to 5.0.26.p and that has fixed the issue on your site, however, I can’t see why that fixed it so I’ve asked one of our developers if they have any feedback so I can double check. I don’t want to say it’s all fixed and then you get the same issue on the next update so I’m trying to figure out how it happened (I can’t reproduce this locally). |
|
Thanks, Tony! Appreciate your help to have it back up. |
|
You’re most welcome 🙂 I’ll let you know with whatever feedback the developers come back with here. |
|
This reply has been marked as private. | |
Yes, thank you. We can see why the code failed but not what caused the condition for it to happen, so we’ve applied a fix within core to prevent it from happening again and will so that goes and if more investigating is required from there. |
|
This reply has been marked as private. | |
You’re most welcome. If you run into any further issues, please do let me know. Hopefully not and have a great week! |
|
You must be logged in to reply to this support post. Sign In or Register for an Account