A plugin conflict is most likely when a failure began after a plugin or theme change, but timing alone does not prove causation. Record the exact symptom and recent changes, then isolate components systematically: use Health Check Troubleshooting mode when the dashboard works, or disable a plugin through your hosting file access when it does not.
Record the failure before changing anything
Write down the exact error text, the URL or admin screen affected, and the action that triggers the problem. Note whether it affects the front end, wp-admin, the block editor, checkout, login, or one particular feature. Record plugin and theme installations, updates, setting changes, WordPress and PHP versions (if available), and whether the failure is repeatable.
A recently installed or updated plugin, or an error that names a plugin file, is a useful lead—not proof. Isolation is what shows whether the symptom changes when that component is disabled.
How to check for a plugin conflict when the dashboard works
Use Health Check Troubleshooting mode
Health Check & Troubleshooting is the safest option on a live site because its changes apply only to the administrator running the test. Visitors continue to see the site’s normal active plugins and theme.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Install and activate the Health Check & Troubleshooting plugin from Plugins > Add New.
- Open Tools > Site Health > Troubleshooting (the tab may be labeled Troubleshooting).
- Start troubleshooting mode. For your session, WordPress disables plugins and switches to a default theme.
- Re-enable the plugins one at a time. After each activation, refresh the affected page or repeat the failing action.
- When the problem returns, record the plugin, theme, versions, exact steps, and error text. Stop changing components until you have documented that combination.
Use the mode’s theme controls to test the current theme against a default theme. If the problem disappears only with the default theme, the evidence points to a theme or a plugin–theme interaction rather than a plugin acting alone.
Deactivate and reactivate plugins manually
If Health Check is unavailable, go to Plugins > Installed Plugins, deactivate the plugins, and reactivate them individually. Check the affected behavior after every activation. This changes the site’s real activation state, so visitors may see missing features or altered pages while testing. Prefer a staging copy for production sites when possible.
If the issue remains after all plugins are disabled, the tested plugin set is not sufficient to explain it. Test a default theme and investigate WordPress, hosting, PHP, browser, content, configuration, and other causes rather than naming a plugin as the root cause.
What if I cannot access wp-admin?
Disable one suspected plugin with FTP or a file manager
- Open your hosting control panel’s file manager or connect with FTP/SFTP.
- Browse to
wp-content/plugins. - Rename the suspected plugin’s directory—for example, append
-disabledto its folder name. - Reload the failing page. WordPress should treat the renamed plugin as inactive.
- If the site recovers, restore the original folder name only when ready to test; then leave the plugin inactive while you review its documentation, support forum, and compatibility information.
Folder names must be changed carefully. Renaming a directory does not repair the plugin or prove it is the only cause; it simply gives you a controlled comparison.
Rank #3
Disable all regular plugins when the culprit is unknown
- In
wp-content, renamepluginsto a temporary name such asplugins-disabled. - Try to load the site or sign in again.
- If it works, restore the directory’s exact original name,
plugins. - Reactivate plugins individually from wp-admin, testing after each one.
Restoring the directory name does not automatically reactivate every plugin. Must-use plugins in wp-content/mu-plugins are managed separately and are not disabled by this procedure.
Use the database only if you are qualified
WordPress also documents changing the active_plugins value in the options table through phpMyAdmin. This edits the stored active-plugin list directly. Database mistakes can damage a site, so take a verified backup and ask your hosting provider for help if you are not comfortable identifying the correct database, table prefix, and serialized value.
Compare the isolation methods
| Method | Best fit | What changes | Main limitation |
|---|---|---|---|
| Health Check Troubleshooting mode | Dashboard works; private test needed | Plugins and theme for the troubleshooting administrator’s session | Requires wp-admin and the Health Check plugin |
| Deactivate/reactivate one by one | Dashboard works; simple isolation | Site-wide plugin activation state | Visitors can be affected while plugins are disabled |
| Rename one plugin folder | Dashboard unavailable; likely culprit known | Disables that plugin | Requires FTP, SFTP, or file-manager access |
| Rename the plugins folder | Dashboard unavailable; culprit unknown or site broadly broken | Disables all regular plugins until the folder is restored and plugins are reactivated | Requires a careful recovery sequence and file access |
Edit active_plugins in phpMyAdmin |
Dashboard unavailable; database administrator available | Changes the stored active-plugin list | Database-editing risk; obtain hosting help if unfamiliar |
Confirm the conflict and decide what to do next
Repeat the original action—not just a different page—after each change. A conflict is strongly indicated when the failure disappears with a component disabled and reliably returns when that same component is enabled under the same conditions. Record the working and failing plugin/theme combinations, versions, environment details, and reproduction steps.
- Search the exact error message together with the plugin name and version.
- Read the plugin’s documentation, changelog, support forum, and author notices for known compatibility issues.
- Update WordPress, the plugin, theme, and PHP only after making a backup and checking compatibility; an update can also introduce a new conflict.
- Contact the plugin author or hosting provider with the complete reproduction record rather than a general claim that “WordPress is broken.”
If disabling one plugin does not change the symptom, it may be one factor among several. Test combinations, especially the active theme with the suspected plugin, and check server or PHP errors before drawing a conclusion.
Recommended Free Tools
Use debug information without exposing the site
Error logs can reveal the file and code path involved in a failure, but debug output should not be displayed to visitors. Public error screens and openly accessible log files can disclose paths, configuration details, credentials, personal data, or other information. Keep logging restricted to administrators, protect the log location, remove secrets and personal data before sharing excerpts, and turn off visible debugging after the test.
When the test points away from plugins
If the issue persists with plugins disabled and a default theme active, the evidence does not implicate the tested plugin set alone. Investigate hosting limits, PHP extensions or version, database errors, custom code, corrupted files, caching, browser behavior, and the specific content that triggers the fault. Preserve the exact error and test record so the next support contact can reproduce the problem.
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.
