Have you recently updated WordPress and then noticed that your post area looks blank when you edit existing posts or pages?
I noticed this after going through the hassle of upgrading to WordPress 3.3.1, and manifests itself as white text being displayed on a white background when your post edit page loads. You might also find that switching between ‘Visual’ and ‘HTML’ modes doesn’t work either, and the wysiwyg icons don’t display.
Having looked through loads of forums and support groups, with various suggestions such as uploading the WordPress files again, clearing cache, and switching off plugins, I came across a random suggestion that has appeared to fix the ‘white text on white background’ problem for me.
Use Google Libraries
Try installing the Use Google Libraries plugin, then clear your browser cache and try again. If this works for you then it suggests a problem with one of the WordPress libraries or files in your install, as the plugin will go off to Google’s libraries to get the files it needs instead. This could also improve the performance of your site too, as you will be making use of Google’s content delivery network and it’ll reduce the load on your server too.
Other ways to fix the WordPress blank post area problem
[Updated April 2017] If the above doesn’t fix the problem for you, try one of these other suggestions from people who have commented here….
Check for plugin conflicts
Try deactivating each of your plugins to see if your text editing area becomes visible again. If you use All-in-One SEO, User Access Manager or WP Auto Responder Newsletter, try them first. If this is the problem, then make sure that plugin is up-to-date. If that still doesn’t resolve the problem then try finding a replacement plugin that does the same thing as the one causing the conflict.
Switch your theme back to the default WordPress theme by going to ‘Appearance’–>’Themes’ and activate the default theme. If this resolves your issue, you’ll need to check if there are updates to your theme and apply them. If there aren’t, it’s worth asking your theme developer if they have a solution. You should be able to switch between themes without impacting your site, but do back your site up beforehand just in case.
Does your .htaccess file have a rule that causes the problem?
If your site is hosted on a Linux platform you may well have a file in your site root folder called .htaccess. This can be used to execute various rules whenever visitors reach your site. Use ftp to (temporarily) rename this file and see if your problem is solved. If the problem is resolved you’ll need to rename the file back again and look for a piece of code in there that is causing the issue.
Have you blocked access to wp-content or wp-includes files?
One of our visitors blocked access to his WordPress php files in his web server configuration (nginx) in order to stop hackers getting in. However, this also stopped him getting to his own site! So check you haven’t done the same.
Try installing the jquery updater plugin
Your theme comes with it’s own set of libraries, including jquery. Newer versions of WordPress and some plugins may need more up-to-date versions of the jquery library to work properly. If you regularly update your theme then this library will be updated naturally. If you don’t it can get out of date and break certain things on your site. This plugin makes sure that your site always has the most up to date version of the jquery library. However, it’s possible that it could break your site somewhere else, so check your site thoroughly after you add the plugin.
Add concatenate_scripts(‘false’) to wp-config.php
Another file in your site root folder is called wp-config.php. You’ll need to edit this through FTP. Try adding… define(‘CONCATENATE_SCRIPTS’, false);
into this file. This stops WordPress from concatenating scripts to improve performance. Mostly, concatenating is a good way to speed things up, but sometimes themes and plugins could break this.
If none of the above fixes your problem, don’t forget to clear your cache and force reload your browser. It’s possible that the problem is solved, but you are still looking at a cached version of your site!
If you find another solution, please let us know by commenting below.