WordPress plugin error

Updated 11 October 2026

Short answer

When a plugin breaks your site, the error message usually names the plugin's folder: look for wp-content/plugins/plugin-name/ in the message or in debug.log. Deactivate that plugin. If you can't reach the admin area, rename the plugin's folder over FTP or your host's file manager, which deactivates it. Then check for an update, a known issue on the plugin's support page, or a replacement.

What's the problem

After installing or updating a plugin, the site shows a critical error, a white screen, a 500 error, or one feature stops working. An error message may mention a plugin's folder.

Why it happens

  • A bug in a new version of the plugin.
  • A conflict between two plugins, or between a plugin and your theme.
  • An incompatible PHP or WordPress version.
  • The plugin needs more memory than PHP allows.
  • A failed or partial update left the plugin's files incomplete.

How to fix it

  1. Find the plugin. The error message, or wp-content/debug.log with WP_DEBUG_LOG on, usually shows a path inside wp-content/plugins/.
  2. Deactivate it in Plugins in the admin area.
  3. If you can't log in, rename its folder in wp-content/plugins. To rule out all plugins at once, rename the whole plugins folder to plugins_old.
  4. If you don't know which plugin, deactivate all, then reactivate them one by one until the error returns.
  5. Fix it properly: install the plugin's latest version, roll back to the previous version, check its support forum, or replace it.
  6. Keep backups before updates, and update plugins one at a time on important sites.

What Preventionlabs checks

One click runs the full report on your domain. For this problem it shows your WordPress version and plugins against the latest releases; script libraries on your homepage with published security holes; whether your site loads, how fast, and where its redirects go; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them. It can't log in to WordPress, so the exact error is in your host's error log or WordPress debug log.

Run your free report

Your first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.

Sources

  1. WordPress: Common WordPress errorsofficial docsIf you can access the Administration Screens try deactivating all of your Plugins and then reactivating them one by one.
  2. WordPress: Common WordPress errorsofficial docsLocate the folder wp-content/plugins and rename the Plugin folder plugins_old .
  3. WordPress: Debugging in WordPressofficial docsThe following code, inserted in your wp-config.php file, will log all errors, notices, and warnings to a file called debug.log in the wp-content directory.

Related

WordPress white screen of death A blank white page means a PHP or database error WordPress didn't show. Turn on debug logging to see it, then disable plugins or the theme to find the cause. WordPress error Read the exact message: a critical error, a database error, maintenance mode, a 500, or a blank page each have their own fix. Here's how to tell them apart. WordPress 500 error On WordPress, a 500 error is most often a corrupted .htaccess file, then a plugin, theme or PHP memory limit. Rename .htaccess first; it's quick and safe. WordPress memory limit "Allowed memory size exhausted" means PHP hit its memory cap. Raise WP_MEMORY_LIMIT in wp-config.php; on shared hosting your host may need to raise it.

Preventionlabs is independent and not affiliated with WordPress. Product names are used only to describe the problem.

← All of WordPress