WordPress Error Log Explainer

Paste a critical error message or debug.log excerpt and find out which plugin or theme is likely responsible, with steps to fix it.

Describe the result you need. AI will set up the tool and ask for any missing details.

Configure with AI

Enter to submit · Shift + Enter for a new line

Sent to AI. Leave out passwords and private customer data.

Your brief

These form details are sent to our AI provider when you generate. Review the result before publishing.

Reading a fatal error yourself

A PHP fatal error message always names the exact file and line where it happened, for example wp-content/plugins/some-plugin/file.php on line 142. The folder name right after wp-content/plugins/ (or wp-content/themes/) is your first clue: that plugin or theme is the one to look at first, whether that means updating it, checking it against a recently changed plugin, or deactivating it to confirm.

If you don't have an error message yet

A white screen with nothing visible usually still has a real error, just hidden. Add this to wp-config.php, above the "That's all, stop editing!" line, then reproduce the problem and check wp-content/debug.log:

define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false );

Turn WP_DEBUG back off once you've found the answer: leaving it on exposes error details to anyone who can trigger one.

Ruling out plugins and the theme

  • Locked out of wp-admin: rename wp-content/plugins over FTP/SFTP or your host's file manager. If the site comes back, rename it back and reactivate plugins one at a time until it breaks again.
  • With WP-CLI: wp plugin deactivate --all, then reactivate one at a time.
  • Memory exhausted: add define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php. If that doesn't help, your host's PHP-level memory limit may need raising too.

Questions people ask

How do I find debug.log on my server?

It's created at wp-content/debug.log once WP_DEBUG_LOG is turned on in wp-config.php, in the same folder as your wp-content/plugins directory. Access it over FTP/SFTP or your host's file manager.

The error mentions wp-includes, not a plugin. What does that mean?

That's WordPress core code. It usually means a plugin or theme called core code incorrectly further up the stack trace; check the rest of the trace for a plugin or theme path above it.

Should I leave WP_DEBUG on permanently?

No. Turn it off again once you've solved the problem: WP_DEBUG_DISPLAY set to false keeps errors out of visitors' browsers, but the log itself can still reveal information you don't want exposed if left on indefinitely.

What's a "critical error" email from WordPress about?

WordPress core can catch a fatal error and put the site into Recovery Mode, emailing the site administrator a one-time link. Check your inbox (and spam folder) for that email if the front end shows "There has been a critical error on this website."

I'm on WooCommerce specifically; is there a similar check?

Yes, paste your full system status report into the WooCommerce system status analyzer for a broader health check.

Want this builtinto your store?

I'm Emmanuel, a Shopify and WooCommerce developer. If this tool pointed at something you'd rather have fixed for you (a faster store, cleaner product data, a migration, a custom feature), send me a note.

Emmanuel Asika

Emmanuel Asika

Shopify & WooCommerce developer, Dublin

I build and fix online stores: new builds, migrations, speed, SEO and the custom bits apps can't do.

hello@emmanuelasika.com