If there’s a 500 internal error, chances are it’s in your PHP error log, OR, if you have debug log enabled on your site, it may be there as well.
Every server is different, especially hosts, so your log may not be in the same place as mine – my log is at /var/log/httpd/error_log and can be read with notepad, or if you’re SSH savvy, just tail -f error_log and watch when the error happens.
If you’re on a managed or shared host, chances are you’ll have to contact them to get a copy of your log.
Alternatively, if you have access to your wp-config.php file ( you should! ) just enable debug there. With WP_DEBUG on, you’ll get a file located at wp-content/debug.log which you can read yourself.
Once you find the bug that’s causing the error, you’ll either A have to disable the plugin, or B, fix it yourself / or contact the dev.
If you need some debug snippets, or even some in-depth debugging tips, check this out: Debugging WordPress, Tips & Snippets
Hi Jerry, As you suggested, I checked out for error log file and did debug mode true also,there are a lot of errors are occuring how to fix them all?
I tried to fix the errors but one of the errors are:
Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
__construct()
instead.
But I’ve been updated my wordpress to 4.3.1, so why this error is coming ?
Your theme or a plugin has extended WP_Widget class to create a unique widget in addition to WP defaults. Their class declaration is using an outdated constructor method. You can identify the source by selectively deactivating plugins that add widgets or by switching to a default theme. When the notice stops you’ve found the source of obsolete code. Contact the author and request they update their code.
Note this is just a Notice level “error”, it does not cause any problems letting it persist — at least for now. It is rather annoying, but harmless. There is a way to have PHP not log such notices by editing php.ini, but not all hosts allow access to this file.
