Posts

wordpress_tips_full1

How to Fix WordPress Blank White Screen | WordPress, blank white screen

So your WordPress site is suddenly Not Working,

http://blog.gameznet.biz/wp-content/uploads/wordpress_tips_full114.jpg

All Your seeing is a blank White Screen

Don't worry all is not lost!

These tips apply for all WordPress version. WordPress is one of the most used and powerful blog engines. And with the all community support, many plugins are developed to make WordPress more powerful and feature rich. But not all plugin developers code their plugins to WordPress standards and sometimes this will create problems with the most annoying problem being a blank page error.

No error message, just a white blank screen. The first tip is “don’t panic“.

Analyze your website in these steps:
1. Check your hosting server

The first step is check your hosting server by going to your server administration (usually cpanel). Check if that’s live or not. If not then contact your hosting server support.
If alive then the problem is likely to be on your blog.

2. Check wp-admin

Check your wp-admin folder by go to http://www.yoursite.com/wp-admin
See if it is alive and not blank.
If it is not blank, then your WordPress doesn’t have a problem.
You can check your themes and files on the root folder. If it is blank, then there are lot of possibilities, but most of the time it is plugins and themes.

3. Check for index.html and .maintenance files
Yes, check if there is a blank index.html in your root folder.
I know it seems odd but if there is a blank index.html in the root then it may be the culprit. Delete it and check your site again.

If your wordpress site is stuck with a "Maintenance Message" go to the root of your instalation and delete the file .maintenance and check your site again, that may fix the problem, if not keep going.

 

4. Check error_log

Open your favorite FTP client program then downoad error_log file at the root of your blog. Analyze it, see what make your blog errors. Usually i found out what make it errors in this file. Usually it will be a memory problem, file not found problem, and so on. Pay more attention to the error message and fix it.
5. Fix: WordPress Memory Exhausted Error – Increase PHP Memory

If you see sometimes a WordPress Memory Exhausted error showing up after activating or updating a new plugin or doing some other task. Usually the error looks like this:
Fatal error: Allowed memory size of xxxxxxx bytes exhausted (tried to allocate xxxxxx bytes) in /home4/xxx/public_html/wp-includes/plugin.php on line xxx

This error occurs as WordPress tries to access more memory then it is allowed to by the “Server PHP configuration” or “WordPress Setting”. Increasing the Memory Limit will solve it.

There are numerous solutions for it, but for this article lets just look at the simplest one of all. Open your wp-config.php which is located in the root WordPress directory.

Look for the following line: $table_prefix = 'wp_';

imediatly after that line add the following line:
define('WP_MEMORY_LIMIT', '64M');

(or higher value if required)

If you still get the error after this fix, you may have to contact your host and ask them to increase your memory limit.
This is not a complete fix since your blog will be using more resources than it should which if you have a lot of traffic may become a major problem and could get your hosting account suspended so it is best to resolve this issue properly. The memory problem is most commonly caused by a plugin so you might want to remove the last plugin that you installed by deleting the plugins folder from your wordpress /plugins directory or moving it temporarily outside of the plugin directory.

Next go back and change the memory limit back to 32 by commenting out the line you entered into your wp-config.php and then see if things work, if they do then it definately is that particular plugin giving you the memory issue. Best not to use it but also best to contact the plugin creator and let them know of the issue so they can work on it.

Depending on your needs, server condition, plugins installed, and size of your site, you could use 32M, 96M, 128M, 256M, 512M, 1024M, 2048M, 4096M.
Make sure your server allows you to use that much dedicated memory, if your unsure contact your host and ask.

If you have access to your PHP.ini file, change the line in PHP.ini
If your line shows 32M try 64M:
memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)

If you don’t have access to PHP.ini try adding this to an .htaccess file:
php_value memory_limit 64M

If all else fails contact your webhost support or the person managing your server.

 

6. Rename plugin dir

To check if there is an error with any individual plugin, rename your /plugins/ folder and create a new empty one.
Now access your wp-admin. If the wp-admin show up, then it is definatly a plugin error. Now it’s your job to find out which plugin is causing the issue.
You can move your plugins back into the new plugin folder one at a time . Make sure its active and then check your site.

 
7. Check all the plugins

To check all the plugins, use cpanel to move all plugins into a temp directory.
(I usually just rename the plugin directory from plugins to plugins_OFF then create a new folder called plugins)
Now put them back one by one into the empty plugins folder, and check wp-admin each time until the blank page error comes back.
When it does you will know "that is the offending plugin"
Get rid of it, if you think you need it then contact the plugin creator for support.

So like i said please don’t panic, check all your installation, plugins and themes folder.
If it is still not working, contact your hosting support and ask them to help you.

Cannot Upgrade Plugins

If your having trouble Upgrading a Plugin and in particular getting an error when you run the automatic update feature for plugins and themes that says something like: could not create directory. /public_html
Try deleting the upgrade directory found within wp-content/upgrade and then recreate it manualy.
Also chmod wp-content/upgrade to 777 and see if that fixes the problem.

I have had to do this on several wordpress 3.0 sites, not sure why it happens but this has fixed the issue for me.