|
dapaevent
|
November 30, 2023 at 4:23 pm
We’re getting a server error 500 when activating event espresso as a plug in.
|
|
Rio
|
November 30, 2023 at 6:17 pm
I did try on my localhost and my test site and everything is fine. Can we get more information, Do you see any error message aside from error 500? Does it only shows up on specific page or all the site is affected? Did you try to enable your log? can you send the error message here?
I’m looking on your site, did you reverse the update? can you tell us your system information too? MySQL and php version.
thanks
|
|
Tony
|
December 1, 2023 at 2:33 am
Hi there,
A 5XX is usually a PHP Fatal error and those will be logged in your server’s PHP error logs.
Your host will usually have a section in your control panel you can use to view PHP errors, if you can see the error here we can investigate further from there.
|
|
gailsiegert
|
December 1, 2023 at 2:46 am
I just updated to 5.0.12p from 5.0.11p and immediately got the Server 500 crash error as well so there is something horrendously wrong with some part of the update. I had to restore everything from a complete backup to get the site back online so there is no way to “pull” the php error log. Not willing to be the guinea pig to try it again. This is a commercial business site.
|
|
Tony
|
December 1, 2023 at 4:37 am
You had to restore the site? So just disabling Event Espresso didn’t bring the site back up?
Without an error, we have no idea what is happening on the site. None of my sites (both live and test sites) are throwing any errors with the update to 5.0.12.p but I’ve rolled the update back as a precaution whilst we investigate.
|
|
gailsiegert
|
December 1, 2023 at 4:47 am
We use SiteGround specifically for this reason – when something blows up, we simply restore everything. Looks like I am going to need to make it a policy to create a new backup set before any future EE updates just in case. Just disabling EE was not an option since we have events being booked.
|
|
Tony
|
December 1, 2023 at 5:11 am
Sure, it’s good practice to create a backup before updating any plugins.
Just disabling EE was not an option since we have events being booked.
In your above post, you mentioned you had to restore a backup to get the site back online, so I’m trying to narrow down the cause further here and wondered if disabling EE brought the site back. Disabling EE would not have removed the events but registrations wouldn’t work on them whilst disabled.
However, that’s not something you tried as you went straight to a backup so doesn’t help in this situation.
—
I’ve been reviewing the error logs from another user who reported this and their site is an issue with adding an index to the DB, which is, odd!
I don’t know if that’s the same issue on your site as there’s no error log but that is currently what we are working on.
|
|
gailsiegert
|
December 1, 2023 at 5:17 am
Yes, we are in the middle of a rather large registration for a conference and it needs to be active. Just seeing the event would not have helped.
I’ll sit tight and wait for a fix, timing is not critical since you’ve pulled the update anyway. I’ll keep an eye out for more info here.
If all else fails on your end, let me know and I might be able to dupe up a staging site in SiteGround and try the update there. I’ll at least have the php error log then.
|
|
Tony
|
December 1, 2023 at 5:26 am
To be honest, you may be best doing that either as I currently can’t guarantee that whatever issue we find with the index issue will be the same issue on your site.
Meaning we push another update with a fix for that, you update and it ftill fatals as your sites issue isn’t related.
—
Side note – I run multiple test sites across multiple different setups ranging from really cheap shared hosting to a dedicated box. 5.0.12.p was tested on all of those without any fatals.
I’m currently guessing the index issue is a config/MySQL version issue but still digging.
|
