Quick answer: When a WordPress plugin stops working, first ask what changed — a plugin, theme, WordPress or PHP update. Then work through these steps: clear all caches, update the plugin and WordPress, check the plugin’s settings and requirements (especially PHP version), test for plugin conflicts by deactivating other plugins, switch to a default theme, turn on debug mode to see the error, and reinstall the plugin. If the site is broken and you can’t log in, disable plugins by renaming the folder over FTP. Plugin conflicts, outdated PHP and cache issues cause most problems.
Before you start: back up
Make a full backup (files and database) before changing anything, or test on a staging site. That way you can always undo.
The 12 fixes, in order
1. Check what changed recently
Did you just update a plugin, theme, WordPress or PHP, or install something new? If so, that change is your main suspect. Check the plugin’s changelog for known issues.
2. Clear every cache
Caching plugins, server caching, CDNs and your browser can all show old versions of a page, making a working plugin look broken. Clear them all, then test in a private browser window.
3. Update the plugin, theme and WordPress
The developer may already have fixed the bug. Update the plugin, your theme and WordPress core (backup first).
4. Check the plugin’s requirements
Each plugin page lists the minimum WordPress and PHP versions. If your server runs an old PHP version, newer plugins may fail. WordPress.org recommends PHP 8.3 or newer — check Tools → Site Health → Info → Server.
5. Review the plugin’s settings
Many “broken” plugins are simply not configured: a missing API key, a disabled module or a shortcode that isn’t on the page. Re-read the setup instructions.
6. Test for plugin conflicts
- Go to Plugins → Installed Plugins.
- Deactivate every plugin except the one that isn’t working.
- Test. If it now works, another plugin was conflicting.
- Reactivate the other plugins one at a time, testing after each, until it breaks again — that’s the conflict.
Common conflicts: two caching plugins, two SEO plugins, page builders with optimisation plugins, and security plugins blocking scripts.
7. Test with a default theme
Your theme can also conflict. Temporarily switch to a default theme like Twenty Twenty-Five. If the plugin works, the theme is the problem — contact the theme developer.
8. Turn on debug mode
Add these lines to wp-config.php (above “That’s all, stop editing”) to log errors without showing them to visitors:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reproduce the problem, then open wp-content/debug.log. The error usually names the plugin file and line. Turn debugging off afterwards. Full guide: WordPress debug mode.
9. Check the browser console for JavaScript errors
If buttons, sliders or forms don’t respond, press F12 in your browser and open the Console tab. Red errors often point to a conflicting script or an optimisation plugin that combined or delayed JavaScript.
10. Exclude the plugin from optimisation
Speed plugins that minify, combine or delay JavaScript can break other plugins. Exclude that plugin’s scripts from optimisation, or turn the setting off to test.
11. Reinstall the plugin
Files can be corrupted during an update. Deactivate and delete the plugin, then install a fresh copy. Most plugins keep settings in the database, but check the plugin’s documentation first.
12. Roll back to the previous version
If a new version broke something, roll back to the last working version (from the plugin’s “Advanced View” on WordPress.org or with a rollback tool) and wait for a fix.
Site broken and you can’t log in?
- Connect with SFTP or your host’s file manager.
- Open
wp-content. - Rename the problem plugin’s folder (for example
contact-form→contact-form-off). If you don’t know which one, rename the wholepluginsfolder. - Log in. WordPress deactivates plugins it can’t find.
- Rename the folder back and reactivate plugins one by one.
Also check your email for WordPress’s recovery mode link, which lets you log in and pause the broken plugin. See white screen of death fixes.
Symptom finder
| Symptom | Most likely cause | Try first |
|---|---|---|
| Plugin settings saved but nothing changes on the site | Cache | Clear all caches |
| Broke right after an update | Bug in new version or conflict | Roll back; check changelog |
| “Requires PHP x.x” or fatal error | Old PHP | Upgrade PHP via host |
| Buttons and forms don’t respond | JavaScript conflict or optimisation | Console + exclude from optimisation |
| White screen / critical error | Fatal PHP error | Recovery mode or rename folder via FTP |
| Works for admins, not visitors | Cache or permissions | Clear cache; test logged out |
When to contact the plugin developer
If you’ve found a conflict or a clear error message, open a support ticket on the plugin’s WordPress.org support forum or the developer’s site. Include your WordPress and PHP versions, the error from debug.log, the steps to reproduce and the other plugin involved. Clear reports get faster fixes. You can find any plugin’s forum through the WordPress.org plugin directory.
How to prevent plugin problems
- Install fewer, well-maintained plugins.
- Update regularly, but test big updates on staging first.
- Avoid running two plugins that do the same job.
- Keep PHP up to date.
- Keep automatic backups — see our backup guide.
Frequently asked questions
Why did my plugin stop working after a WordPress update?
The plugin may not be compatible yet. Check for a plugin update or roll back the plugin temporarily.
How do I find which plugin is causing a problem?
Deactivate all plugins, then reactivate them one at a time until the problem returns.
Will deactivating a plugin delete its settings?
Usually not — deactivating keeps settings. Deleting may remove them, depending on the plugin.
Can too many plugins cause problems?
Quality matters more than number, but every plugin adds risk of conflicts and slowdowns.
Final thoughts
Work from easy to hard: cache, updates, settings, conflicts, theme, debug log. Most plugin problems are found within an hour this way. Still stuck? Consider a maintenance service or hiring a developer.
A real-world example
A small online course creator noticed that her booking calendar plugin stopped showing available dates after an update. Rather than deactivating everything on her live site, she created a staging copy through her host. On staging, she switched to a default theme — the calendar still failed. She then deactivated all plugins except the calendar, and it worked. Reactivating plugins one at a time revealed the conflict: a caching plugin was combining JavaScript files and breaking the calendar’s scripts. Excluding the calendar’s script from combination fixed it on staging, so she applied the same setting on the live site. Total time: about 40 minutes, with no downtime for customers.
When the problem isn’t a plugin
Sometimes a plugin stops working because of the server, not the code. A host’s PHP upgrade can break older plugins, and emergency security updates — such as the patches released for the October 2026 PHP2Shell vulnerabilities — sometimes change settings like upload limits. If a plugin broke without any change on your side, ask your host whether the server was updated recently.
WordPressPrime.com is an independent guide and is not affiliated with the WordPress Foundation, WordPress.org or Automattic. Always back up your website before making changes, and check official sources for the latest details.
