Wordpress 'white screen of death' HELP!

Got a call from a client that their site which was working since it went up was suddenly blank. My Googles lead me to conclude that they’ve got ‘the white screen of death’ which is the first time I’ve encountered this issue. I am able to access the WP dashboard and FTP and I tried the recommended usual fixes- activating default theme, renaming plug-in folder etc. to no avail. I’m calling on the experts here who I have more confidence in for their insights for help.

Have you switched on WP_DEBUG in wp-config.php (set it to true) and checked the output? Most of the time that’s the best place to start – if you’ve got a PHP error, it should show up there.

Begin inspecting from the very index. Add stuff root index and see if it displays… then move to the next files in the tree and see where the thing blocks.

It could very well be a lack of php memory, try adding this line to wp-config.php

define(‘WP_MEMORY_LIMIT’, ‘64M’);

@sevenspark: Yes I switched it on as part of the recommended fixes, but there’s no wp-content/debug.log (even displaying hidden files).

@wickedpixel: Do you mean add an index.html file?

@m1chelangel0: Did that, no effect.

CLINE123 said
@sevenspark: Yes I switched it on as part of the recommended fixes, but there’s no wp-content/debug.log (even displaying hidden files).

@wickedpixel: Do you mean add an index.html file?

@m1chelangel0: Did that, no effect.

Try :: define(‘WP_MEMORY_LIMIT’, ‘128M’); or :: define(‘WP_MEMORY_LIMIT’, ‘256M’); even, simply to see if it is the case

The main index file is a simple & minimalist index.php file that imports the rest of the wordpress scripts. Must be where your wordpress is installed or in the root of your website, in case wordpress is located in other folder.
If there are other index files near the php one try renaming them because the server may be set to use those instead by default.

256M- no effect.

@wickedpixel: Oh, do you mean add some code to the root index.php to see if it displays?

As far as I remember I had the same problem in my practise. Look at your server logs

Just a suggestion.