What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To find a WordPress plugin conflict, note the exact failure and recent changes, then test plugins one at a time while repeating the action that triggers the problem. If you can access the dashboard, use Health Check Troubleshooting mode to test privately for your admin session. If you cannot, disable the likely plugin by renaming its folder through FTP or your host’s file manager. A plugin update or an error naming a plugin file is a clue—not proof—that the plugin is responsible.
Before testing, record what is failing
Write down where the problem occurs—on the public site, in wp-admin, in the editor, or in a particular feature—and copy the exact error text. Note whether the failure is repeatable and what changed just before it began, including plugin or theme installs and updates and configuration changes. A recent change or an error that names a plugin file can help narrow the search, but you still need to test whether disabling that component changes the symptom. WordPress’s plugin-management documentation describes these clues and recommends isolating a suspected plugin.
How to check for a plugin conflict when wp-admin works
Use Health Check Troubleshooting mode for a private test
Health Check Troubleshooting mode lets you test a basic setup without changing what ordinary visitors see. In the Health Check plugin, open the Troubleshooting tab and enable Troubleshooting Mode. For your administrator session, plugins are deactivated and WordPress switches to a default theme; the normal active plugins and theme remain in place for other visitors. Then enable plugins one at a time, returning to the affected page or repeating the failing action after each activation. The Learn WordPress lesson on plugin and theme conflicts and the WordPress Support Handbook guide explain this session-specific approach.
- Open the Health Check plugin’s Troubleshooting tab and start Troubleshooting Mode.
- Repeat the original action in the simplified setup. If the problem remains, that is evidence against the tested plugins and theme being the only cause.
- Enable one plugin, then repeat the action or refresh the affected page. Continue until the issue returns or you have tested the plugins relevant to the feature.
- Record which plugin was enabled when the symptom returned, along with the exact steps that reproduce it.
Use one-by-one deactivation as an alternative
If you do not use Troubleshooting Mode, go to Plugins > Installed Plugins, deactivate plugins, and reactivate them individually, checking the affected behavior after each activation. This changes the site-wide active plugin state while you test, so visitors may be affected while components are disabled. For a production site, use the session-specific mode or test on a staging site if available. WordPress outlines sequential plugin deactivation in its plugin-management documentation.
Test the theme as well
Troubleshooting Mode also lets you compare the current theme with a default theme. If the problem disappears only when the default theme is active, the theme may be involved; that result does not establish a plugin-only conflict. Record the theme and plugin combination and, where practical, test relevant combinations before reporting the issue to the theme developer. The Learn WordPress lesson describes testing both plugins and themes.
What if I can’t access wp-admin?
Rename a suspected plugin folder
Use FTP or your hosting provider’s file manager to open wp-content/plugins and rename the folder belonging to the suspected plugin. WordPress should treat the renamed plugin as disabled. Check whether the site or affected feature recovers. If it does, restore the folder name and test the plugin through the dashboard when access returns, or seek help from the plugin author or host. WordPress documents this recovery method in its troubleshooting FAQ.
Disable all regular plugins if the culprit is unknown
If the site is broadly broken and you cannot identify a likely plugin, rename the entire wp-content/plugins directory. This disables regular plugins. After recovery, restore the directory’s original name; restoring it does not automatically reactivate the plugins. Enable them individually in wp-admin and check the affected behavior after each one. WordPress also describes the FTP or file-manager method in its troubleshooting FAQ.
Use the database method only if you can manage it safely
WordPress documents changing the active_plugins value in the options table through phpMyAdmin as another way to disable plugins when the admin screens are unavailable. This requires database access and careful editing. If you are unfamiliar with phpMyAdmin or unsure how to recover the setting, ask your hosting provider for assistance rather than experimenting on the live database. See the WordPress troubleshooting FAQ.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
Compare the available methods
| Method | Best fit | What it changes | Main limitation |
|---|---|---|---|
| Health Check Troubleshooting mode | Dashboard works; you want a private admin-session test | Plugin and theme setup for the troubleshooting administrator’s session | Requires the Health Check plugin and wp-admin access. WordPress Support Handbook |
| Deactivate and reactivate one by one | Dashboard works; straightforward isolation | Site-wide plugin activation state | Visitors may be affected while plugins are disabled. WordPress plugin-management documentation |
| Rename one plugin folder | Dashboard is unavailable and a likely culprit is known | Disables that plugin | Requires FTP or file-manager access. WordPress troubleshooting FAQ |
| Rename the plugins directory | Dashboard is unavailable and you need to disable regular plugins broadly | Disables all regular plugins until the directory is restored and plugins are reactivated | Requires file access and careful recovery. WordPress troubleshooting FAQ |
Edit active_plugins in phpMyAdmin |
Dashboard is unavailable and you can safely manage the database | Changes the stored active plugin list | Database-editing risk; ask the host for help if unfamiliar. WordPress troubleshooting FAQ |
What to do after finding a likely conflict
When the symptom returns after enabling a component, preserve the details rather than stopping at the plugin name. Record the plugin and theme combination, their versions, your WordPress and PHP versions if available, the exact error, and the steps that reproduce it. Check the plugin’s documentation and support forum, search for the exact error message, and contact the plugin author or hosting provider as appropriate. WordPress recommends using plugin support resources when troubleshooting; see Manage Plugins.
If disabling or enabling a single plugin does not change the behavior, the issue may involve the theme, another part of the setup, or more than one factor. A simplified test narrows the possibilities; it does not prove the root cause in every case.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Handle error logs carefully
Debug output and logs can help explain a hard failure, but do not display errors to site visitors or leave logs somewhere publicly accessible. WordPress warns that these configurations can expose information. Before sharing a log in a public support request, remove secrets and personal data. See the WordPress Site Health documentation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
