Arrrrrghhh! This is getting annoying now…!
I’ve resolved the undefined variable error warning for s2member.
Now, having checked all of your points above, I am confident there is no server-wide php error_reporting enabled and I can’t find any declarations in the theme folder. Plugins however, there may still be an issue.
With WP_DEBUG enabled, the DEBUG plugin is now not reporting any issues other than a notice which I don’t think is affecting anything.
However, Members List won’t activate due to the error in the post above which I can’t resolve without reverting to the original code (which then still has WPUF issues), and the other Members plugin (AMR Users) is not showing errors in the debug console but is in the Firebug one. I’ve emailed you the Firebug output.
The plot thickens….
Whoops! Typo! I accidentally included an extra ‘(‘.
Should be
if(!isset($_REQUEST['page']) or $_REQUEST['page'] !== 'members-list-configure-search') {
return;
}
etc
I have also spoken to my server administrator and he has indicated that warnings for notices were enabled on the main php config
Maybe but WordPress executes the following line at the start of wp-load.php as part of it’s bootstrap code. Note E_NOTICE is not part of this.
error_reporting( E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_ERROR | E_WARNING | E_PARSE | E_USER_ERROR | E_USER_WARNING | E_RECOVERABLE_ERROR );
However turning on WP_DEBUG does enable error_reporting with the E_ALL constant in wp-includes/load.php. Unfortunately this includes E_NOTICE so we may be not on the money as this would cause our problem anyway. So back to the drawing board for the cause of the internal server error.
One thing you do need to do is to turn error logging on as the DEBUG plugin piggybacks on normal returns which in this case doesn’t happen.
Simply set WP_DEBUG_LOG and WP_DEBUG to true in wp-config.php. The log can be found in wp-content/debug.log.
Anyway fix the errors and try again as the true error may be further on in the code.
OK…
Have fixed typo but strangely now getting this warning message in the WP dashboard:-
The plugin generated 314 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.
Also, when I did get the Members List plugin enabled and tried to add new post on WPUF, got the error pop up but can’t copy/paste text here so have emailed screen grab.
I’ve also attached the debug.log as I’ve only just enabled it.
Well we managed to find the problem once we got past the initial errors and it was quite unexpected.
We found this error was repeated in the log and not just for Simple Pie.
PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 122880 bytes) in /home/culture/public_html/wp-includes/SimplePie/File.php on line 139
This type of error results in the 500 error and can be quite random.
To actually see the error you have to enable PHP/WordPress debugging with debug to log enabled and digest the results.
WordPress 3.5.1 uses quite a lot of memory even with the default installation theme and no plugins (32MB on my 64bit server). Add a few plugins and a theme and your topping 64MB and beyond.
To fix increase the memory limit by changing the following lines in your wp-config.php file
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
to
define('WP_MEMORY_LIMIT', '128M');
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
