0

Such a generic problem would obviously have numerous solutions on the Web, right?

My company uses a custom purchased wordpress template, which worked fine till yesterday, for unknown reasons.

I am perfectly assured this is a template related WSOD, which is problematic, because they still wish to use the same template.

I'd be glad to finally solve the problem, but without error output it is only a wild guess what had happened.

How to hit the nail of the head without the following:

define('WP_DEBUG', true);

or reading the error_log in the root of a host? Because both failed to show anything, with latter being empty.

What are the other commands to force WP to show the error output?

krzy
  • 5
  • 1

1 Answers1

1

The configuration of your server will be preventing the errors from being shown even with WP_DEBUG on.

Try this in wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

This will log the errors to a file inside wp-content titled debug.log.

Further reading: http://codex.wordpress.org/Editing_wp-config.php#Configure_Error_Logging

Nathan Dawson
  • 18,138
  • 3
  • 52
  • 58
  • Thank you very much! it turned out to be suddenly undefined variable in a custom php script of the template. But now that's my task to solve it... \ – krzy May 04 '14 at 18:24