|
Florian Werner
|
February 24, 2017 at 6:53 am
Good morning,
my webmaster and our hosting support have been investigating issues with our site lately causing error 500 and making the site inaccessible from both front and backend.
THe investigation from my liquidweb hosting support has led him to make the following statement and recommandation to contact you for further assistance:
Ok, I disabled the wordpress-seo and that still didn’t make the site available. I disabled the event-espresso-core-reg plugin and the site was available. Re-enabling the wordpress-seo the site is still live so it appears that event-espresso-core-reg is to blame. I would contact their dev and see if there’s a known issue with it or a configuration that needs to be tweaked with it on an FCGI server.
|
|
Florian Werner
|
February 24, 2017 at 6:53 am
sorry forgot to mention the site is theatrelacbrome.ca
|
|
Tony
|
February 24, 2017 at 7:44 am
Hi Florian,
If you check your servers error logs you should find the full error that’s being thrown, Server error 500 is just a generic error that means ‘something went wrong’ and doesn’t really help identify the problem.
To narrow down whats actually happening we need the full error message, if there is nothing within the error logs you’ll need to enable WP_DEBUG on the site, if you don’t want to display errors to your users you can use this snippet:
https://gist.github.com/Pebblo/8787f5530ea777c84aaf62f075e55b32
Which will store the errors within /wp-content/debug.log
If Event Espresso is causing a fatal error when activated it may just be another symptom of the problem rather than the cause, it really just depends on the error.
|
