- Most plugin issues are fixable in under an hour
- Why Is My Plugin Not Working in WordPress?
- Plugin and Theme Conflicts
- Outdated Plugin or WordPress Version
- PHP Version Mismatch
- Cache and CDN Issues
- Corrupted Plugin Files or Hosting Limits
- Common Signs of a Broken WordPress Plugin
- How to Fix a Plugin Not Working in WordPress
- Clear Your Website Cache First
- Update the Plugin and WordPress Version
- Disable All Plugins to Find Plugin Conflicts
- Switch to a Default WordPress Theme
- Check Your PHP Version
- Reinstall the Plugin
- Enable WordPress Debug Mode
- Most Common WordPress Plugin Errors and Fixes
- How to Disable a Broken Plugin Without Access to WordPress Admin
- Disable Plugin Using File Manager
- Disable Plugin Using FTP
- Best Practices to Prevent Plugin Problems
- Keep Your Plugin Count Lean
- Avoid Abandoned Plugins
- Use Staging Sites for Major Updates
- Back Up Before Every Update
- When You Should Replace a Plugin
- When to Contact a WordPress Expert
- Plugin Issue Still Not Resolved?
- Frequently Asked Questions
- Final Thoughts on Fixing WordPress Plugin Issues
- Prevention is cheaper than recovery
A plugin not working in WordPress is one of those moments that can feel mildly terrifying for any site owner. One minute things work fine. The next, your contact form’s gone, your dashboard throws an error, or the whole site loads to a blank white screen.
Honestly, this happens more often than people realise. Plugin problems usually show up after a WordPress core update, a PHP upgrade, a fresh plugin install, or a theme switch. Sometimes there’s no obvious trigger at all.
Most plugin issues are fixable in under an hour
Around 70 percent of WordPress plugin failures trace back to just three causes: plugin conflicts, outdated PHP versions, and cache issues. You rarely need a developer for the basics. This guide walks through every common cause and how to recover your site without losing your data or your patience. The Yoast troubleshooting guide covers some of the same ground if you want a second take.
Why Is My Plugin Not Working in WordPress?
Before touching anything, it helps to know what you’re dealing with. Plugin failures in WordPress almost always trace back to one of these causes:
Plugin and Theme Conflicts
Two plugins fighting over the same hook, or a theme using outdated WordPress functions, breaks compatibility faster than anything else. This single cause alone explains the majority of plugin failures we see in real troubleshooting.
Outdated Plugin or WordPress Version
Plugins built for older WordPress versions break when the core updates. Plugin developers usually patch this within days, but only if you install the update. Sites that delay updates by months are the ones that crash hardest.
PHP Version Mismatch
Modern plugins need modern PHP. Sites still running PHP 7.2 or below silently break newer plugins, and the error messages rarely make this obvious. Worth checking even when nothing else seems to be wrong.
Cache and CDN Issues
Cached pages keep serving the broken version even after the underlying issue is fixed. Cloudflare, LiteSpeed, WP Rocket, and browser cache each hold their own copy. Clearing one isn’t enough.
Corrupted Plugin Files or Hosting Limits
A dropped connection during install, low PHP memory limit, or low execution time on shared hosting can leave plugin files in a broken state. The files look fine but behave erratically.
Common Signs of a Broken WordPress Plugin
Some symptoms are obvious. Others are easy to miss. The Imagely team has a detailed breakdown of plugin malfunction symptoms as well. Watch for:
- White screen of death (a blank page with no error)
- Website slow to load or partially loading
- Admin dashboard freezing or showing critical errors
- Plugin settings disappearing from the menu
- “There has been a critical error” messages from WordPress
- Broken layout or missing styles on the front end
- Sudden drop in site speed right after activating a plugin
- Checkout, contact forms, or login pages not submitting
If two or more of these show up after the same change, that’s your signal. Treat it as a plugin issue first.
How to Fix a Plugin Not Working in WordPress
Work through these in order. Don’t skip ahead. The fastest fixes sit at the top for a reason. The Elementor team’s fix guide follows similar logic if you want to cross-reference.
Clear Your Website Cache First
This sounds too simple to matter. It often does matter. Cached pages keep showing the broken version of your site even after the plugin issue is fixed.
Clear three layers: browser cache (hard refresh with Ctrl+Shift+R or Cmd+Shift+R), your WordPress cache plugin (WP Rocket, LiteSpeed Cache, or W3 Total Cache all have a “Purge All” button), and your CDN cache from Cloudflare, Bunny, or KeyCDN. Sometimes the plugin’s already working. The cache just hasn’t caught up.
Update the Plugin and WordPress Version
Outdated plugins are one of the top reasons things break after a core WordPress update. Plugin developers usually release a patch within days, but you have to actually install it.
Before updating anything, take a backup. UpdraftPlus or your hosting provider’s built-in backup tool both work. Without one, recovery gets ugly fast. Update WordPress core first, then plugins, then themes.
The single biggest mistake we see during plugin updates is people updating everything at once. When something breaks after a bulk update, you have no idea which plugin caused it. Update in small batches of three to four plugins, then test the site before moving to the next batch.
Disable All Plugins to Find Plugin Conflicts
This is the single most useful step in the whole list. Plugin conflicts cause more issues than every other cause combined.
Go to Plugins, select all, deactivate everything. Check if the site or feature works again. If yes, reactivate plugins one by one and test the broken feature after each one. When the issue returns, you’ve identified the conflict.
A tip from real troubleshooting experience: activate security and caching plugins last. They tend to be the most aggressive about hooking into other plugins.
Switch to a Default WordPress Theme
Plugin issues sometimes aren’t plugin issues at all. They’re theme issues pretending to be plugin issues.
Temporarily switch to Twenty Twenty-Four or Twenty Twenty-Three. If the plugin starts working, your theme’s the problem. Often it’s a custom theme that wasn’t updated for the latest WordPress version. From there you’ve got two choices: update the theme, or contact the theme developer.
Check Your PHP Version
This one catches people off guard. Older PHP versions silently break modern plugins.
WordPress officially recommends PHP 7.4 or higher, but in practice you want PHP 8.1 minimum and PHP 8.2 preferred for newer plugins and better security. Check your version from your hosting control panel. Most hosts let you switch PHP versions with one click. For supported versions, see the official PHP support page.
Reinstall the Plugin
Plugin files get corrupted more often than people think. A dropped connection during an update or a partial install can leave you with files that look fine but behave erratically.
Deactivate the plugin (don’t delete first), then delete it, download a fresh copy from the WordPress.org repository or the developer’s site, and install again. Only download from trusted sources. Nulled plugins are one of the fastest ways to get malware on your site.
Enable WordPress Debug Mode
If nothing above worked, it’s time to look at what WordPress is actually complaining about.
Open your wp-config.php file via File Manager or FTP, and change define('WP_DEBUG', false); to define('WP_DEBUG', true);. Add define('WP_DEBUG_LOG', true); and define('WP_DEBUG_DISPLAY', false); too. Errors will now log to /wp-content/debug.log, usually naming the exact plugin causing trouble.
Just remember to turn debug mode off once you’re done. Detailed error logs on a live site are a security risk. The full walkthrough is in the WordPress debugging documentation.
Most Common WordPress Plugin Errors and Fixes
Quick reference for the patterns that come up most often:
How to Disable a Broken Plugin Without Access to WordPress Admin
This is the one that saves you when things really go wrong. Locked out of /wp-admin? Site showing the dreaded “critical error” with no way in? You can still disable the broken plugin manually.
Disable Plugin Using File Manager
If your host has cPanel or a similar control panel, open File Manager and navigate to public_html/wp-content/plugins/. Find the folder of the plugin you suspect, and rename it (for example, woocommerce becomes woocommerce-disabled). Try logging in again.
WordPress automatically deactivates any plugin it can’t find. Once you’re back in the dashboard, rename it back or delete it cleanly. Not sure which plugin’s causing the issue? Rename the entire plugins folder to plugins-off. That disables everything at once.
Disable Plugin Using FTP
Same process, different tool. Connect with FileZilla or your host’s FTP credentials, navigate to /wp-content/plugins/, and rename the problem plugin folder. Refresh your site and log back in.
FTP’s useful when File Manager isn’t available, or when you’re working from a development machine.
Best Practices to Prevent Plugin Problems
Most plugin disasters are predictable. A few habits stop them from happening:
Keep Your Plugin Count Lean
15 to 25 quality plugins are fine for most sites. 60 lightweight ones still slow you down. Audit your plugin list every quarter and remove anything you no longer use. Deactivated plugins still take up server space and remain a security risk.
Avoid Abandoned Plugins
If a plugin hasn’t been updated in over 12 months, it’s risky. Check the “Last Updated” date and recent reviews on WordPress.org before installing anything new. Active maintenance matters more than feature count.
Use Staging Sites for Major Updates
Most quality hosts include staging environments for free. Test plugin updates there first. If something breaks, your live site stays untouched. This single habit prevents more emergencies than any other practice on the list.
Back Up Before Every Update
Daily automated backups are even better. UpdraftPlus, BlogVault, or your host’s built-in backup tool all work. Without a recent backup, every failed update becomes a potential disaster.
For a deeper preventive routine, our WordPress maintenance checklist covers what to review monthly.
When You Should Replace a Plugin
Sometimes troubleshooting isn’t the answer. The plugin itself is the problem.
Consider replacing a plugin when it hasn’t been updated in 12+ months, recent reviews mention security issues or unresolved bugs, it’s noticeably slowing your site (test with GTmetrix or Pingdom), it’s no longer compatible with your current WordPress version, or the developer has stopped responding to support requests.
There’s almost always a better-maintained alternative. Just take a backup before swapping.
When to Contact a WordPress Expert
Some situations are worth handing off. Don’t sink eight hours into a fix when a developer can resolve it in 30 minutes.
Bring in an expert if you’re dealing with recurring crashes that come back after every fix, ecommerce issues affecting checkout or payments (revenue’s bleeding while you debug), malware or security conflicts, database corruption or missing records, or custom-coded plugins where standard troubleshooting doesn’t apply.
For complex setups or business-critical sites, our WordPress development team and WordPress support plans handle these daily. The WordPress.org support forums are also worth checking for community-driven solutions.
Plugin Issue Still Not Resolved?
Some plugin conflicts run deeper than standard troubleshooting can reach. Our WordPress team has spent more than a decade fixing exactly these kinds of crashes, conflicts, and update headaches for sites of every size.
Frequently Asked Questions
Why is my plugin not working in WordPress?
Usually it’s a conflict with another plugin, an outdated PHP version, or a recent WordPress core update. Clear your cache, deactivate other plugins one by one, and check that your PHP version is 8.1 or higher. These three checks resolve most plugin issues without any developer involvement.
How do I fix plugin conflicts in WordPress?
Deactivate all plugins, then reactivate them one at a time. Test your broken feature after each one. When the issue returns, you’ve identified the conflicting plugin. Activate security and caching plugins last since they tend to be the most aggressive about hooking into other plugins.
Can a WordPress update break plugins?
Yes, especially major version updates. Plugin developers usually patch compatibility within days. Always back up your site before updating, and update WordPress core first, then plugins, then themes. Update in small batches so you can identify what broke if something does.
How do I disable a broken WordPress plugin manually?
Access your site via File Manager or FTP, go to /wp-content/plugins/, and rename the broken plugin’s folder. WordPress will automatically deactivate it the next time it loads. You can then log back into your admin dashboard and remove or reinstall the plugin cleanly.
What causes the white screen of death in WordPress?
Most often it’s a PHP fatal error from a plugin or theme. Enable debug mode in wp-config.php to see the exact error, then disable the offending plugin via FTP if needed. Low PHP memory limits on shared hosting can also trigger this issue, especially with heavier plugins.
Should I delete inactive plugins?
Yes. Deactivated plugins still take up server space and remain a security risk if they’re not updated. Delete anything you don’t actively use. If you might need a plugin again later, you can always reinstall a fresh copy from WordPress.org.
How many plugins are too many in WordPress?
There’s no fixed number, but each plugin adds load. Most well-built sites run smoothly with 15 to 25 quality plugins. Quality matters far more than count. A single poorly coded plugin can slow your site more than 20 well-built ones combined.
Final Thoughts on Fixing WordPress Plugin Issues
Most plugin issues in WordPress look worse than they actually are. Clear your cache, deactivate plugins one by one, check your PHP version, and most problems sort themselves out in under an hour.
Prevention is cheaper than recovery
Regular backups, a lean plugin list, staging environments, and timely updates stop the majority of issues before they happen. Treat your WordPress site the way you’d treat any other critical system, with a bit of routine care. The sites that rarely crash aren’t lucky. They’ve just built better habits around maintenance.
And if something stays broken after working through this guide, that’s usually a sign it’s bigger than a plugin. Get a second pair of eyes on it. Talk to our WordPress team and we’ll walk through your specific situation.
