WordPress Plugin Not Working? A Step-by-Step Fix Guide (2026)

A WordPress plugin not working looks different every time. Sometimes you install it and nothing happens. Sometimes the settings will not save. Sometimes the contact form stops sending email. And the scariest version: you click update and the whole site turns white.

The good news is that the causes come down to a handful of things, and you can work through them methodically. This guide goes from the easiest, lowest-risk checks to the ones that involve server files. Follow the order and stop as soon as you find the cause.

Before you start: always back up your files and database. If you can still reach the dashboard, use a backup plugin or your host’s backup tool. If you have no backup system at all, set one up first.

Pin Down the Symptom First

Fixing goes much faster when you know which group the problem falls into.

Step 1: Clear Every Layer of Cache

A lot of “I changed the setting but nothing changed” cases are not broken plugins at all. You are just looking at an old cached page. Cache can live in several layers:

1. Browser cache: try a private/incognito window
2. Caching plugin: such as WP Rocket, LiteSpeed Cache or W3 Total Cache. Purge everything.
3. Host-level cache: many hosts have a purge button in the control panel
4. CDN: such as Cloudflare. Use Purge Cache.

Also, caching plugins set to “combine and minify JavaScript” often break other plugins that rely on JS. Temporarily turn off file combining and test again.

Step 2: Check for a Plugin Conflict

A plugin conflict is one of the top reasons a plugin is not working in WordPress. The safest way to find one is on a staging copy, if your host offers it. If not, do it during low-traffic hours.

1. Deactivate every plugin except the problem one
2. Test whether the problem plugin now works
3. If it does, reactivate the others one at a time, testing after each
4. The one that brings the problem back is the conflicting partner

With many plugins, use halving: reactivate half. If it breaks, split that half again. It is far faster than one by one.

Another option is the Health Check & Troubleshooting plugin from the WordPress team. Its Troubleshooting mode disables plugins only for your session while visitors still see the normal site, which is ideal when you cannot switch plugins off on a live site.

Step 3: Check the Theme and JavaScript Errors

Sometimes the conflict is with the theme, not another plugin.

• Temporarily switch to a default theme such as Twenty Twenty-Five (in Troubleshooting mode this does not affect visitors)
• If the plugin works on the default theme, your theme has conflicting code

For buttons or forms that do nothing when clicked, open your browser’s Developer Tools (F12), go to the Console tab and reload. Red messages usually include a file path that tells you which plugin or theme is involved.

Step 4: Check the PHP and WordPress Versions

Each plugin lists its minimum versions on WordPress.org under “Requires PHP” and “Requires at least”.

• See your current versions under Tools > Site Health > Info > Server
• If your PHP is older than the plugin needs, it may refuse to install or break the site
• Conversely, if you just upgraded PHP and an old plugin broke, that plugin does not support the new version

The right fix is to find a plugin that is still actively maintained, not to stay on an old PHP version. Unsupported PHP versions no longer get security patches. You can change the PHP version in your hosting control panel.

Step 5: Raise the Memory Limit

Heavy plugins such as page builders, shops or image processing can use more memory than the server allows. The symptom is a white screen or the message “Allowed memory size exhausted”.

Add this line to wp-config.php, above the line that says “That’s all, stop editing”:

define( 'WP_MEMORY_LIMIT', '256M' );

If nothing changes, your host has locked the value. Adjust it in the control panel or ask the host. And if a single plugin uses abnormal amounts of memory, it may be time to find a lighter one (see our WordPress speed optimization guide).

Step 6: Turn On the Debug Log to See the Real Error

When guessing stops working, let WordPress tell you. Add these lines to wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Then trigger the problem again and open wp-content/debug.log.

How to read it quickly:

• Look for Fatal error first, since that is what breaks the page
• Check the path in the message. If it is wp-content/plugins/plugin-name/, that is your culprit
• Warning and Deprecated messages rarely cause a crash, but they tell you the code is outdated

Important: when you are done, set debug back to false and delete debug.log. The file can expose paths and internal details to outsiders.

Step 7: Disable a Plugin by Renaming Its Folder (When You Are Locked Out)

If the site is so broken you cannot reach the dashboard, disable plugins from the file side using your host’s File Manager or SFTP.

1. Go to wp-content/plugins/
2. Find the suspect plugin folder and rename it, for example by adding -off to the end
3. WordPress can no longer find the plugin and deactivates it automatically
4. Try the site and dashboard again

If you do not know which one, rename the entire plugins folder to plugins-off. Every plugin will be disabled. Then rename it back and reactivate plugins one at a time from the dashboard.

This does not delete plugin settings, which live in the database. If you are also locked out of the admin area, see how to fix wp-admin login problems.

Other Commonly Overlooked Causes

• Expired or unactivated licence: some premium plugins limit features until you enter a key
• Security plugin or firewall blocking requests: saving some settings can look suspicious. Check the firewall log.
• Wrong file permissions: installs or updates fail with permission errors
• Plugin removed from the directory: if WordPress.org says the plugin is closed, stop using it and find a replacement
• Nulled plugins: pirated versions are often tampered with and carry malware risk
• Plugins doing the same job: two SEO plugins or two caching plugins at once will overwrite each other’s output

Prevent It From Happening Again

Our website maintenance checklist builds these habits into a monthly routine.

When to Call for Help

You can try this yourself if you can still reach the dashboard and have a backup. Get someone experienced involved when:

• The site has been down for a while and it is affecting sales or bookings
• You have no backup and are not sure whether a fix might make things worse
• The debug log points to the theme or custom code
• You suspect a hack, such as unfamiliar plugins you did not install or the site redirecting elsewhere

The Southern Whale freelance team fixes problems like this for businesses in Southern Thailand regularly, both one-off fixes and ongoing website maintenance. If you want a leaner site built with fewer plugins that is easier to maintain, see our WordPress service. Send us the symptoms and a screenshot on LINE OA.

Frequently Asked Questions

Do I lose my settings if I deactivate a plugin?

No. Deactivating or renaming the folder does not touch the database. However, clicking “Delete” on some plugins also wipes their data, so read the warning before deleting.

A plugin update broke my site. Can I roll back?

Yes. The safest route is restoring from a backup, or using a rollback plugin for plugins from the WordPress.org directory, then waiting for the developer to release a fix.

Why does a plugin work on desktop but not on mobile?

Usually separate caches, a theme that hides that section on mobile, or a caching plugin that builds a separate mobile cache. Clear every cache layer first.

How many plugins is too many?

There is no fixed number. Quality and avoiding overlap matter more than count. Several well-written plugins can be lighter than one badly written one.

Is it dangerous to turn on WP_DEBUG on a live site?

With WP_DEBUG_DISPLAY set to false, errors are not shown on the page. Still, turn it off and delete debug.log when you finish, because the file may be readable from outside.

My form plugin does not send email. Is the plugin at fault?

Usually it is the server’s mail sending, not the form. Sending through properly authenticated SMTP usually fixes it.