Tell me more ×
WordPress Answers is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

My entire WP site is now blank? I haven't done anything to it other than add some posts to it today. I can get in the back end and everything is there, it even returns the source code, but in Chrome IE and FF it just shows a blank white page. Does anybody have any ideas as to why this could be happening?

share|improve this question
Enable output of debug messages, by adding define( 'WP_DEBUG', true ); in your wp-config.php file. Then report back with any errors that get output; primarily, report back any Fatal Error: messages. – Chip Bennett Mar 2 '12 at 1:34
<b>Notice</b>: Undefined index: page in <b>/home/hcsc/public_html/wp-content/plugins/advanced-category-excluder/advanced‌​-category-excluder.php</b> on line <b>15</b><br /> – Jonnny Mar 2 '12 at 2:32
<b>Notice</b>: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>init</code> hooks. Please see <a href="codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in <b>/home/hcsc/public_html/wp-includes/functions.php</b> on line <b>3587</b><br /> – Jonnny Mar 2 '12 at 2:33
<b>Notice</b>: add_option was called with an argument that is <strong>deprecated</strong> since version 2.3 with no alternative available. in <b>/home/hcsc/public_html/wp-includes/functions.php</b> on line <b>3553</b><br /> – Jonnny Mar 2 '12 at 2:33
<b>Notice</b>: Use of undefined constant ace - assumed 'ace' in <b>/home/hcsc/public_html/wp-content/plugins/advanced-category-excluder/advanced‌​-category-excluder.php</b> on line <b>310</b><br /> <br /> <b>Notice</b>: Use of undefined constant ace - assumed 'ace' in <b>/home/hcsc/public_html/wp-content/plugins/advanced-category-excluder/advanced‌​-category-excluder.php</b> on line <b>310</b><br /> – Jonnny Mar 2 '12 at 2:34
show 6 more comments

closed as too localized by toscho Nov 6 '12 at 4:26

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.

1 Answer

The way I would approach this is as follows sequentially:

  1. Check your error logs. If you don't have access to them, contact your host and have them check for you to see if there are any clues there.
  2. Disable all plugins to remove offending factors from the list
  3. Check your .htaccess file to make sure there's nothing awry there
  4. Revert back to the default theme (Twenty Twelve). If you're using Twenty Twelve, download and install a fresh copy here.
  5. Backup your wp-content & wp-config.php files and reinstall WordPress as well as remove your .htaccess file (unless you have added custom code there).

If you're on a shared hosting plan, it's quite possible your host has added some code to your functions.php or .htaccess file. (I've had this happen several times) Otherwise, a hacker has jumped over the wall and planted malicious code in your WP install/theme/plugins.

Hope this gives you some clues.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.