|
Lawson
|
January 2, 2018 at 7:12 am
Hello,
I am receiving a 500 error with your plugin. I’ve renamed the plugins folder and then activated all the plugins separately. When Event Espresso goes live even after a full reinstall we see 500 errors when trying to edit anything on the dashboard.
Any ideas?
Thanks in advance.
Lawson
|
|
Lawson
|
January 2, 2018 at 7:14 am
Sorry.
http://www.theasap.org.uk
Version: 4.9.53.p
Do you want to see server logs?
|
|
Tony
|
January 2, 2018 at 7:18 am
Hi there,
I replied to the other thread you posted about this after splitting it into its own thread here:
https://eventespresso.com/topic/split-reinstall-because-website-is-down-with-http-error-500/
Error 500 just means ‘something went wrong’ and doesn’t provide enough information to know what the problem is.
If you look in the error logs you’ll likely find a fatal error is being thrown, if you can post that we can investigate further.
|
|
Lawson
|
January 2, 2018 at 10:21 am
Hi,
Just checked
Nothing showing…Any ideas?
Thanks
Lawson
|
|
Josh
|
January 2, 2018 at 11:08 am
Having no errors would be an indication that errors aren’t being logged. Can you follow the steps outlined here that show how to turn on error logging with the WordPress Debug mode?
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
|
|
Lawson
|
January 4, 2018 at 5:02 am
As instructed on https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug we have added the following to our wp-config.php
// Enable WP_DEBUG mode
define( ‘WP_DEBUG’, true );
if ( WP_DEBUG ) {
@ini_set( ‘display_errors’, 0 );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
}
We have then activated Event Espresso Version 4.9.53.p
This causes New Post, New Page, etc. to not work and we have to ftp in and rename event-espresso-core-reg, as deactivating plugin doesn’t work either.
There is no file called debug.log created in the wp-content directory. error_log, in tyhe root doesn’t list an error and php-error.log is completely blank.
What can we do?
|
|
Tony
|
January 4, 2018 at 5:21 am
Try with just define( 'WP_DEBUG', true ); and remove the code after that which should then display the error rather than log it.
Then when you activate EE you should see the error displayed on the page.
|
|
Lawson
|
January 4, 2018 at 6:27 am
Hi,
To begin with we changed false to true “define(‘WP_DEBUG’, true);”
It was after your reply with https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug that we changed it to…
define( ‘WP_DEBUG’, true );
if ( WP_DEBUG ) {
@ini_set( ‘display_errors’, 0 );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
}
Any further things to try?
|
|
Tony
|
January 4, 2018 at 6:30 am
So have you tried with just define( 'WP_DEBUG', true );?
None of the other code.
The additional code tells your site to log the errors, using just the above should show the error on the page.
|
|
Tony
|
January 4, 2018 at 6:32 am
Oh, nvm, I understand.
So with just the above, you didn’t see any errors at all?
Try with:
define( 'WP_DEBUG', true );
@ini_set( 'display_errors', 1 );
It looks your server is set to not display errors (which is a good thing on production) but the above should have overridden that.
|
|
Lawson
|
January 4, 2018 at 6:33 am
We have reset the WP config back to how it was to begin with. We have renamed Event Espresso Core, activated it and had the Error 500 again. In /WPcontent there is no debug.log.
What do we do now?
|
|
Lawson
|
January 4, 2018 at 7:15 am
Just worked our way through all the plugin conflicts and found a conflict with your plugin and https://metabox.io/. We need both working in parallel. Any ideas?
|
|
Tony
|
January 4, 2018 at 7:49 am
We need the error to know what the problem is.
I just installed Meta Box on a test site to see if I could reproduce and get the error myself but I’m not seeing any problems, which extensions do you have installed?
In regards to the error not showing on your site, I’d recommend contacting you host and have them enable error logging on your site, without the errors nothing can be fixed.
|
|
Josh
|
January 4, 2018 at 8:21 am
One other thing about the error with the metabox activated, that might be a case where your server is running low on memory so when both plugin are activated the server hits its memory limit. That will cause a 500 error.
Your host can also help with a memory limit issue by raising the memory limit available for PHP.
|
|
Lawson
|
January 4, 2018 at 8:34 am
Thanks Gents.
I will report back.
|
