Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My WordPress site is just a blank white page or says there was a critical error

Short answer

A blank page or a critical error means PHP stopped before it could draw the page. The WordPress handbook lists the usual causes: a faulty plugin or theme, or too little memory. It suggests deactivating plugins, switching to a default theme and turning on debugging. Before that, make a copy of the site and check the admin email for a recovery message.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The whole site, or only the admin area, is a white page.
  • It says there has been a critical error on this website.
  • It started right after I installed, updated or edited something.
  • Some pages work and others are blank.
  • I got an email from WordPress with a recovery link.

Why does this happen?

  1. A plugin crashed

    The WordPress handbook says for a white screen to deactivate all plugins, then reactivate them one at a time to find the faulty one. Plugin updates, or two plugins that clash, are the most common trigger.

  2. The theme is at fault

    The same page suggests switching to a default WordPress theme, or renaming the active theme's folder, to test whether the theme is the cause.

  3. PHP ran out of memory

    The handbook lists insufficient memory as a recurring cause, with the Allowed memory size exhausted error. The limit is raised in wp-config.php or php.ini, or on shared hosting by the host.

  4. A PHP version change

    Hosts upgrade PHP, and older plugins or themes may not run on the new version. The page goes blank rather than showing a message.

  5. The error is hidden

    Servers are usually set not to show errors to visitors, so you see white. The handbook advises enabling WP_DEBUG and reading wp-content/debug.log for the exact failure.

What can I do about it today?

  1. Check the administrator emailFor critical errors the handbook says to look at the site admin email first. WordPress may have sent a message naming the plugin or theme and a recovery link.
  2. Remember the last thing that changedWrite down which plugin, theme, update or edit came just before the problem, and the time. It narrows the search.
  3. Ask your host for a restore pointMost hosts keep backups. Ask for a copy of the current files and database first, then find out what restore points exist.
  4. Do not keep reloading or updatingFurther updates stack changes on top of the fault. Pause everything until you know the cause.
  5. Do not delete plugin or theme foldersThe handbook describes renaming them to deactivate them, which is reversible. Deleting is not. If you are not comfortable with FTP, leave it for a developer.
  6. Tell customers if you take ordersIf the shop is down, say so on social media or by email so people do not think the order failed.

When should I bring someone in?

  • The error remains after the plugin and theme test, or you cannot reach your files.
  • It is an online shop and orders are being lost.
  • A debug log shows database errors or files you do not recognise.

How do I handle it?

  1. Copy before changingFiles and database are saved, so every test can be undone.
  2. Turn on logging, privatelyI enable the error log so nothing is shown to visitors, and read the exact error.
  3. Isolate by switching things off in orderPlugins, then theme, then PHP version and memory, one at a time, with a note of each result.
  4. Fix the cause, not only the symptomThat means updating or replacing the faulty plugin, adjusting PHP or the limit, or repairing the file.
  5. Test the whole siteHome, forms, checkout and admin are checked after the fix, and logging is turned back off.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is my data gone?

Usually not. A white screen means PHP stopped, and the content in the database is normally still there. That is why a copy first matters.

Can I fix it myself?

The handbook describes renaming folders via FTP and editing wp-config.php. These are safe only if you have a backup and know what you are changing.

Why only the admin area?

Admin loads different code from the public pages, so a plugin that only runs in one of them can break just that part.

Will it come back?

It can if the cause is an outdated plugin or a hosting limit. Finding that cause is what prevents a repeat.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.