WordPress plugin conflicts are a common issue for many website owners. One moment your site is working perfectly, and the next, you’re staring at a blank screen or error message unable to access your WordPress admin dashboard.
This article explains how to detect and fix plugin conflicts without accessing the dashboard, using only your hosting account’s cPanel, which is available on most shared hosting plans. No technical background is required just follow the steps carefully.
What Causes Plugin Conflicts in WordPress?
Plugins are pieces of code that add new features to your site. However, when:
-
Two plugins try to modify the same function
-
A plugin conflicts with your current theme
-
A plugin is poorly coded or outdated
-
A recent update breaks compatibility
…your site may crash or lock you out of the WordPress admin area. This is often referred to as the “white screen of death.”
Tools You’ll Need (All Available in cPanel)
-
File Manager: To rename or remove plugin folders
-
phpMyAdmin (only in rare cases): To check plugin-related database entries
-
Backups (recommended): To restore your site if needed
Step 1: Backup Your Site Before Making Changes
Even though you can’t access WordPress, it’s essential to back up your files and database:
-
Files: Use File Manager → Compress
public_html
folder → Download -
Database: Use phpMyAdmin → Select your site’s database → Export as SQL file
This protects you from accidental data loss while troubleshooting.
Step 2: Log Into cPanel and Open File Manager
-
Go to:
https://yourdomain.com/cpanel
-
Use your hosting credentials to log in
-
In the Files section, click File Manager
-
Navigate to your WordPress folder, usually
public_html/
Step 3: Locate the Plugins Folder
Navigate to:
You will see a list of folders, each representing an installed plugin (e.g., elementor
, contact-form-7
, woocommerce
).
Step 4: Disable All Plugins
Here’s how to disable plugins without the dashboard:
-
Rename the entire
plugins
folder to something likeplugins_old
-
This deactivates all plugins instantly
-
Now, try accessing your WordPress admin at:
https://yourdomain.com/wp-admin
If it works, you’ve confirmed that a plugin was causing the issue.
Step 5: Find the Problematic Plugin
-
Rename
plugins_old
back toplugins
-
Open the
plugins
folder -
One by one, rename individual plugin folders (e.g., rename
contact-form-7
tocontact-form-7_off
) -
After renaming each folder, try accessing your dashboard
When your site starts working again, you’ve found the plugin causing the issue.
Step 6: Update or Replace the Faulty Plugin
Once you’ve identified the problematic plugin:
-
Check for updates: Maybe the conflict was fixed in a newer version
-
Delete and reinstall: If the plugin folder was corrupted
-
Replace it: If the plugin is outdated or unsupported, search for alternatives
Additional Tips
-
If the problem returns after an update, try waiting a few days before updating again. Plugin developers often release quick patches.
-
Avoid using too many plugins the more you have, the higher the chance of conflicts.
-
Always update plugins one at a time, especially major ones like page builders or eCommerce tools.
When Plugins Can Crash the Site Instantly
Some plugins, especially those related to caching, redirection, or security, may break your site immediately upon activation or update. Common examples:
-
Caching plugins like W3 Total Cache
-
SEO tools that modify
.htaccess
-
Redirect managers
Always test these carefully or on a staging site first (if your host provides one).
What If the Theme is Causing the Problem?
If disabling plugins doesn’t solve it, your theme might be the culprit. Here’s how to test it:
-
Go to
/wp-content/themes/
-
Rename your current theme’s folder (e.g.,
astra
→astra_old
) -
WordPress will automatically fall back to a default theme like
twentytwentyfour
if available -
Try logging in again
Conclusion
Even without access to your WordPress dashboard, you can solve plugin conflicts safely using cPanel. With basic file management skills and a backup strategy, clients can confidently fix issues and regain access to their sites.
By following the steps in this guide:
-
You’ll avoid panic during critical downtime
-
You won’t need immediate help from developers
-
And most importantly your site will be back online quickly