A broken WordPress plugin can do more than create an error message. It can stop contact form leads, interrupt checkout, slow down your website, or leave customers looking at a blank page. These steps to fix a plugin not working in WordPress help business owners identify the real cause quickly, restore essential functions safely, and avoid making a small technical issue more expensive.
The key is not to make random changes. Treat your website like a revenue-generating business asset: protect it first, test one variable at a time, and document what changed.
#1 Start With a Backup
Before updating, deleting, or disabling a plugin, create a full backup of your WordPress files and database. A good backup gives you a reliable rollback point if a repair creates another problem.
If your hosting control panel offers backups, confirm that the latest copy includes both the website files and the database. For eCommerce sites, check how recent the backup is. Restoring an old backup may remove recent orders, customer records, inventory updates, or form submissions.
For a high-traffic business website, a staging site is the safer option. It lets you test updates and plugin changes without exposing visitors to downtime. This takes a little more setup, but it is often worth it when your website supports sales, bookings, or paid advertising campaigns.
#2 Identify What “Not Working” Actually Means
A plugin failure is not always a failure of the plugin itself.
A form may appear broken because an email server is misconfigured.
A payment plugin may fail because the payment provider’s credentials have expired.
A page builder issue may arise from a theme update or insufficient PHP memory, rather than the builder itself.
Start by recording the exact behavior. Does the problem happen on every page or only one? Did it begin after an update? Can administrators see the issue, or only logged-out visitors? Is there an error message, a white screen, a spinning loader, or a missing feature?
This information narrows the diagnosis and prevents unnecessary work. It also makes support requests faster if you need a WordPress specialist to investigate.
#3 Check for Plugin, Theme, and WordPress Updates
Outdated software is one of the most common causes of WordPress plugin problems. Plugin developers update their code to support new WordPress versions, fix bugs, address security vulnerabilities, and maintain compatibility with current PHP versions.
Review available updates in your WordPress dashboard. Update WordPress core, your active theme, and plugins carefully, ideally on a staging copy first. Do not assume every update is harmless, especially on a custom website or WooCommerce store with multiple integrations.
Update in a controlled order. Begin with WordPress core if it is significantly outdated, then update the theme and plugins one at a time. After each update, test key business actions: submitting a lead form, opening service pages, adding a product to cart, completing checkout, and accessing the admin area.
If the plugin stopped working immediately after an update, note the version number. That detail can reveal a compatibility problem and help you decide whether to roll back temporarily while a permanent fix is prepared.
#4 Clear Caches Before Assuming the Plugin Is Broken
Caching improves website speed, but it can also make a fixed feature look broken or a removed feature appear active. Your website may use a WordPress caching plugin, server-side cache, CDN cache, browser cache, or all four.
Clear the cache from your performance plugin and hosting panel. Then open the affected page in a private browser window or a different browser. If you use a CDN, purge its cache as well.
For example, a business may update a form plugin but still see the old form because the cached page is being served to visitors. Clearing the cache solves the visible issue without changing any code. This is why caching should be checked early, before disabling critical functionality.
#5 Test for a Plugin Conflict
Sometimes, two or more WordPress plugins can conflict with each other, causing errors, broken features, or unexpected website behaviour. This is especially common with page builders, caching plugins, WooCommerce extensions, security plugins, and contact forms.
To identify a plugin conflict:
Deactivate the affected plugin and check if the issue changes.
Reactivate it, then disable other plugins one at a time.
Test the affected feature after each plugin is disabled.
If the issue disappears, you’ve likely found the conflicting plugin.
Avoid permanently disabling essential plugins like security, payment, or SEO tools.
Use a staging website for testing to avoid affecting visitors or online sales.
If the conflict persists, consult a WordPress developer for a safe and permanent solution.
Testing plugin conflicts carefully can help you resolve issues without disrupting your live website or business operations.
#6 Rule Out a Theme Conflict
A plugin can also conflict with your active theme. This is more likely if the issue affects page layout, menus, product pages, checkout fields, mobile display, or JavaScript-driven elements.
Temporarily switch to a default WordPress theme on staging and test the plugin again. If the plugin works with the default theme, your current theme, or its custom code needs attention.
Avoid changing themes directly on a live website unless you understand the impact. A theme change can alter layouts, menus, widgets, branding elements, and custom templates. For a business website, an experienced WordPress fixer can isolate the conflict without risking your customer experience.
#7 Check Error Logs and Server Requirements
When WordPress shows “There has been a critical error on this website,” the actual reason is usually stored in an error log. Your hosting panel may provide PHP error logs, and WordPress debugging can reveal errors related to a specific plugin file or function.
Common causes include an unsupported PHP version, insufficient PHP memory, missing server extensions, file permission issues, or an incomplete plugin update. A plugin that worked last month may fail after a hosting environment change, which is why ongoing maintenance matters.
Check that your server meets the plugin’s current requirements. Many modern plugins require newer PHP versions and adequate memory limits, especially if they manage product catalogs, large forms, visual builders, backups, or reporting dashboards.
Be careful with debug mode on a live site. Error messages can expose technical details that should not be visible to customers. Use logs privately and turn off public error display after testing.
#8 Reinstall the Plugin Only When It Is Safe
If the plugin files are corrupted or an update did not complete correctly, reinstalling the plugin may solve the issue. First, confirm whether the plugin stores important settings, submissions, or data in the database, in uploaded files, or within its own folders.
For simple plugins, deleting and reinstalling can be safe. For a form plugin, booking system, membership tool, or WooCommerce extension, deleting it without checking may remove settings or disrupt connected services. Export settings where possible and capture screenshots of configurations before making changes.
Download or install the latest trusted version of the plugin. Never use unofficial or “nulled” premium plugins. They are a major source of malware, backdoors, broken updates, and long-term website risk.
When Should You Hire a Web Developer?
It’s perfectly fine to try a few basic troubleshooting steps when a WordPress plugin stops working. Updating the plugin, clearing the cache, or checking for conflicts may solve the issue. However, if the problem continues, don’t wait too long before seeking professional help. A small plugin issue can quickly turn into a bigger problem that affects your entire website.
Hire a WordPress developer if:
The plugin stops working after an update.
Your website displays errors or a blank page.
Important features or forms stop functioning.
The issue affects your online sales or enquiries.
You suspect a plugin conflict or malware infection.
DIY fixes haven’t solved the problem.
Your website becomes slow or unstable.
You want to avoid data loss or extended downtime.
An experienced developer can quickly identify the root cause, safely repair your website, and restore normal functionality before the issue becomes more expensive and time-consuming to fix.
