Plugin Not Working in WordPress? 15 Proven Fixes for 2026

A plugin not working in WordPress can cause anything from a missing button or broken contact form to a blank page, critical error, checkout failure or complete loss of access to the WordPress dashboard.

The problem does not always mean the plugin itself is defective. WordPress plugins depend on compatible versions of WordPress, PHP, themes, other plugins, server modules, REST API connections, scheduled tasks and correctly loaded JavaScript files. A failure in any of these areas can stop a plugin not working in WordPress issue from being resolved until the underlying cause is identified.

This guide explains how to identify the cause and fix a WordPress plugin safely. The steps cover simple configuration problems, plugin conflicts, PHP errors, server limitations, broken updates, caching issues and advanced recovery methods.

Quick Answer

When a plugin is not working in WordPress, first confirm that it is activated and configured correctly. Then update WordPress, the plugin and your theme, clear all caches, check the plugin’s PHP and WordPress requirements, and test for plugin or theme conflicts.

When the WordPress dashboard is inaccessible, use Recovery Mode, rename the plugin folder through your hosting file manager, or deactivate it with WP-CLI. Enable WordPress debugging to identify the exact PHP file or function causing the failure.

Plugin Not Working in WordPress at a Glance

Why Is a WordPress Plugin Not Working?

A plugin not working in WordPress may stop working because of:

• An incomplete or corrupted update
• Incorrect plugin settings
• An expired license or disconnected external account
• Missing plugin dependencies
• A conflict with another plugin
• A conflict with the active theme
• An unsupported WordPress or PHP version
• Missing PHP extensions
• Browser, page, server or CDN caching
• Broken permalink rules
• JavaScript errors
• Blocked REST API or AJAX requests
• Failed WP-Cron or loopback requests
• Insufficient PHP memory or execution time
• Incorrect file permissions
• Damaged plugin files
• A fatal PHP error

WordPress 7.0, released on May 20, 2026, is the current actively maintained WordPress series as of July 3, 2026. WordPress presently recommends PHP 8.3 or newer, MariaDB 10.6 or newer, MySQL 8.0 or newer, and HTTPS. However, an individual plugin may have different minimum or maximum compatibility requirements, so always check the plugin developer’s documentation before changing PHP versions.

Diagnose the Problem Before Changing Anything

Identify exactly what is failing before you begin troubleshooting.

Record the following details:

• The exact error message
• The page where the problem appears
• When the problem started
• What was updated or changed immediately beforehand
• The plugin version
• The WordPress version
• The PHP version
• Whether the issue affects all visitors or only logged-in users

This information will make conflict testing faster and will help a plugin developer reproduce the problem.

Common WordPress Plugin Error Messages

You may encounter one of these errors while troubleshooting:

Back Up Your Website Before Troubleshooting

Create a complete backup of your WordPress files and database before updating software, changing PHP, editingwp-config.php, modifying file permissions or reinstalling a plugin. This simple precaution can help you recover quickly if a plugin not working in WordPress issue causes unexpected problems during troubleshooting.

WordPress documentation recommends backing up before upgrades because a dependable rollback is difficult without copies of both the site files and database. Perform risky tests on a staging site whenever your hosting account provides one.

1. Check Whether the Plugin Is Activated and Configured

Begin with the most basic checks.

Go to:

WordPress Dashboard → Plugins → Installed Plugins

Confirm that the plugin displays an Active status. If it is inactive, select Activate. This is often the first step in resolving a plugin not working in WordPress issue.

Activation alone may not be enough. Many plugins require additional setup, including:

• Connecting an external service
• Entering an API key
• Activating a paid license
• Selecting a page or post type
• Creating a form, feed or template
• Enabling a module
• Adding a block, widget or shortcode
• Saving the plugin’s settings
• Assigning permissions to user roles

Open the plugin’s settings page and look for warnings, onboarding steps or incomplete configuration notices.

Check Required Plugins

Some plugins depend on a separate parent or companion plugin. For example, an extension may not work unless its main e-commerce, form, membership or page-builder plugin is active.

Modern WordPress versions can validate information provided through a plugin’s Requires at least, Requires PHP and Requires Plugins headers. When a dependency is missing or inactive, WordPress may display an administrative warning or prevent normal activation.

On a WordPress Multisite installation, also check whether the plugin must be activated on an individual site or network-activated by a Super Admin.

2. Update WordPress, the Plugin and Your Theme

Version incompatibility is one of the most common reasons behind a plugin not working in WordPress after a site change.

Go to:

Dashboard → Updates

Check for updates to:

• WordPress core
• The affected plugin
• Other active plugins
• The active theme

Install one update at a time and test the affected feature after each update. This makes it easier to identify which change resolves or causes the problem.

Do not assume that updating only the broken plugin is sufficient. A plugin may depend on a function added by a newer WordPress version, while an outdated theme may use code that conflicts with newer plugin files. Keeping every component updated is an important step in resolving a plugin not working in WordPress issue.

WordPress Site Health specifically warns administrators when plugins are waiting for updates and provides details about the WordPress, plugin, theme, database and server environment.

What If the Problem Started After an Update?

If the plugin stopped working immediately after an update:

• Check the plugin’s changelog and documentation.
• Clear every cache layer.
• Confirm that any database-update prompt has completed.
• Check the WordPress admin email for a Recovery Mode message.
• Review the debug log.
• Restore the previous working version only from a trusted backup or an official source.

Avoid downloading old plugin versions from unknown websites. Modified plugin packages may contain malicious code.

Check Whether WordPress Rolled Back a Failed Plugin Update

When an automatic plugin update causes a fatal error, WordPress may restore the previously installed version. Check the website administrator’s email for a message explaining whether the update succeeded, failed or triggered a rollback.

Then go to:

WordPress Dashboard → Plugins → Installed Plugins

Compare the installed plugin version with the latest version shown on the plugin’s official page or changelog. A plugin not working in WordPress may appear to be fixed because WordPress restored the previous files, while the unsuccessful update remains available.

Even when WordPress successfully restores the earlier version, test the plugin’s important functions. A rollback does not guarantee that every database operation, integration, scheduled task or front-end feature is working correctly.

If the plugin update repeatedly fails:

• Check the available disk space.
• Review file ownership and permissions.
• Confirm that WordPress can create temporary files.
• Check the PHP and server error logs.
• Clear the WordPress and server caches.
• Test the update on a staging website.
• Temporarily disable automatic updates for that plugin.
• Contact the plugin developer with the exact error message.

Do not repeatedly force the same update on a live website without first determining why it failed, especially if a plugin not working in WordPress issue continues after multiple update attempts.

3. Check PHP, Database and Plugin Requirements

A plugin may install successfully but fail during activation or use because the server does not meet its requirements. Checking your website environment is an important step when troubleshooting a plugin not working in WordPress.

Open:

Tools → Site Health → Info

Review the sections for:

• WordPress
• Active plugins
• Server
• Database
• WordPress constants
• Filesystem permissions

The Site Health screen provides detailed environment information and can report outdated PHP, missing server modules, blocked HTTP requests, REST API failures, loopback problems and filesystem issues.

Check the Plugin’s Requirements

Review the plugin’s WordPress.org page or official documentation for:

• Minimum WordPress version
• Minimum PHP version
• Tested WordPress version
• Required PHP extensions
• Required companion plugins
• Database requirements
• Web server requirements

WordPress recommends PHP 8.3+, MariaDB 10.6+ or MySQL 8.0+, but that does not guarantee every older plugin is compatible with PHP 8.3. A plugin that has not been updated may use removed or deprecated PHP functions.

Before upgrading PHP on a live website:

• Create a backup.
• Test the new version on staging.
• Update WordPress, themes and plugins.
• Check the plugin developer’s compatibility statement.
• Review the PHP error log after switching.

When the problem started immediately after a PHP upgrade, temporarily testing the previously working supported PHP version can help confirm the cause. Do not remain on an unsupported PHP version as a permanent solution, especially if you are trying to resolve a plugin not working in WordPress issue.

4. Clear Browser, WordPress, Server and CDN Caches

Sometimes the plugin is working, but your browser or caching system continues to display an older version of the page. Clearing cached content is often a simple way to resolve a plugin not working in WordPress issue.

Clear these cache layers in order:

• Browser cache
• WordPress caching plugin
• Page-builder generated CSS or asset cache
• Object cache, such as Redis or Memcached
• Hosting or server cache
• CDN cache
• Security or optimisation proxy cache

Then test the page in:

• A private or incognito window
• A different browser
• A logged-out session
• A different device or network

WordPress documentation notes that browser caching can make it appear that changes have not taken effect because the browser may reload previously stored files instead of downloading updated ones.

Caching is especially likely when:

• A design change does not appear
• A shortcode still shows old content
• Updated JavaScript is not loading
• A plugin works for logged-in administrators but not visitors
• A form or cart behaves differently between sessions

Do not deactivate caching permanently unless testing confirms it is causing the problem. Instead, exclude the affected dynamic page or script according to the caching plugin’s documentation. This approach can help determine whether a plugin not working in WordPress problem is actually caused by outdated cached files rather than the plugin itself.

5. Refresh WordPress Permalink Rules

Plugins that create custom post types, product pages, course pages, directories, forms or API endpoints may stop working when WordPress rewrite rules are outdated. Refreshing the permalink structure can often resolve a plugin not working in WordPress issue caused by incorrect rewrite rules.

Go to:

Settings → Permalinks

You normally do not need to change the selected structure. Visiting the Permalinks screen triggers a rewrite-rule flush. You may also click Save Changes to ensure the current settings are stored.

Test this fix when you see:

• Plugin-generated pages returning 404 errors
• Custom post types failing to open
• Product or course URLs not loading
• Plugin endpoints returning “page not found”
• Problems following a migration or domain change

If the issue continues, check whether WordPress can update the .htaccess file on Apache. WordPress recommends contacting the hosting provider when rewrite modules or server configuration require changes.

Nginx does not use .htaccess, so its rewrite rules must be checked in the server configuration.

Plugin Not Working After a Migration, Domain Change or HTTPS Switch

A plugin may stop working after moving WordPress to another host, domain, subdirectory, or HTTPS address. This is another common reason for a plugin not working in WordPress because the plugin may still contain an old URL, server path, webhook address, license domain, or cached configuration.

Check the following settings:

• Go to Settings → General.
• Confirm that the WordPress Address and Site Address use the correct domain and protocol.
• Go to Settings → Permalinks and save the current structure.
• Clear the WordPress, object, hosting and CDN caches.
• Reconnect the plugin’s licence or external account.
• Update callback and webhook URLs in connected services.
• Check whether the plugin still references the old domain.
• Confirm that the new server has the required PHP extensions.
• Check file ownership and permissions on the new host.
• Inspect the browser console for mixed-content errors after switching from HTTP to HTTPS.

Plugins may store complete URLs inside WordPress database options, widgets, page-builder data, scheduled jobs and custom tables. After a migration, these saved URLs may continue pointing to the previous domain.

Advanced users with WP-CLI can first perform a dry run:

wp search-replace 'https://old-example.com' 'https://new-example.com' --all-tables-with-prefix --skip-columns=guid --dry-run

The dry run reports proposed changes without modifying the database. Review the results carefully.

After creating a complete database backup, run the command without --dry-run only when the proposed replacements are correct:

wp search-replace 'https://old-example.com' 'https://new-example.com' --all-tables-with-prefix --skip-columns=guid

Do not perform a blind SQL replacement across the entire database. A basic text replacement can damage serialized data used by plugins, themes and page builders.

Do not replace values in the WordPress guid column.

6. Deactivate and Reactivate the Plugin

A plugin’s activation process may create database tables, options, scheduled events or rewrite rules. If activation was interrupted, deactivating and reactivating it may repeat part of that setup and help resolve a plugin not working in WordPress issue.

Go to:

Plugins → Installed Plugins

Then:

• Deactivate the affected plugin.
• Clear relevant caches.
• Activate the plugin again.
• Check for setup or database-update prompts.
• Test the affected feature.

WordPress documentation recommends deactivating and activating a plugin again as an initial troubleshooting step.

Be careful with plugins that control:

• Maintenance mode
• Security or firewall rules
• Redirects
• Membership restrictions
• E-commerce checkout
• Two-factor authentication
• Caching
• Database cleanup

Read the plugin documentation before deactivation if disabling it could expose protected content or interrupt transactions.

7. Test for Conflicts With Other Plugins

Two plugins may load competing versions of the same library, modify the same hook, declare the same function or apply incompatible filters. Testing for plugin conflicts is an effective way to identify the cause of a plugin not working in WordPress issue.

To perform a manual conflict test:

• Create a backup or staging copy.
• Deactivate all plugins except the plugin being tested.
• Check whether the problem remains.
• If the plugin now works, reactivate the other plugins individually.
• Test after every activation.
• Stop when the problem returns.

The last plugin activated is not automatically “bad.” The issue may be an interaction between both plugins, and either developer may need to provide a compatibility fix.

WordPress’s official troubleshooting guidance recommends deactivating all plugins and reactivating them one by one to identify the source of a conflict.

Do Not Forget Must-Use Plugins

Must-use plugins are stored in:

/wp-content/mu-plugins/

They appear separately in the WordPress dashboard and cannot be disabled through the standard Plugins screen. To test them, an administrator with server access must temporarily remove or rename the relevant file or folder.

Managed hosting providers sometimes install caching, security or management functions as must-use plugins, so ask the host before changing them.

8. Test for a WordPress Theme Conflict

Themes can contain plugin integrations, custom templates, JavaScript, CSS and functions that alter plugin behaviour.

Temporarily activate a current default WordPress theme and test the affected feature again.

If the plugin works with the default theme, investigate:

• Outdated template overrides
• Custom code in functions.php
• JavaScript errors
• CSS hiding plugin content
• Page-builder integrations
• Theme-specific plugin modules
• WooCommerce or membership template overrides

WordPress’s official error documentation recommends switching to a default theme when diagnosing white screens and other compatibility problems.

Do not delete the active production theme. Activate a default theme temporarily on staging or use a troubleshooting environment that affects only your session.

9. Use Site Health and Troubleshooting Mode

WordPress includes a Site Health tool under:

Tools → Site Health

The Status tab displays critical issues and recommended improvements. The Info tab reports technical details about WordPress, plugins, themes, server software, database versions, permissions and configuration constants. Reviewing this information can help identify the cause of a plugin not working in WordPress issue.

Look for warnings involving:

• REST API availability
• Loopback requests
• HTTP requests
• PHP modules
• PHP version
• Scheduled events
• Filesystem permissions
• Plugin updates
• Debug settings

Troubleshooting Without Affecting Visitors

The official Health Check troubleshooting workflow can create a temporary clean WordPress session for the logged-in administrator. In that session, plugins can be disabled and a default theme activated without changing what ordinary visitors see.

This allows you to:

• Test the affected plugin alone.
• Activate other plugins one by one.
• Switch themes for your session.
• Gather debugging information.
• Exit Troubleshooting Mode when finished.

WordPress’s support handbook recommends this method for isolating plugin and theme conflicts while leaving the public site unchanged.

Use only the official plugin listing and verify that the tool is compatible with your current WordPress installation before installing it.

10. Open WordPress Recovery Mode

When a plugin causes a fatal PHP error, WordPress may send an email to the site administrator containing a special Recovery Mode link. This feature can be especially helpful when troubleshooting a plugin not working in WordPress that prevents access to the dashboard.

The message commonly indicates that the website is experiencing a technical issue and may identify the plugin or theme involved.

Recovery Mode allows an administrator to log in while WordPress pauses the failing component for that session. You can then deactivate or update the problematic plugin without immediately triggering the fatal error again.

Check:

• The administrator email inbox
• Spam or junk folders
• Email delivery logs
• Whether the address under Settings → General is correct

The Recovery Mode link is temporary and should not be shared publicly.

Once logged in:

• Note which plugin WordPress has paused.
• Deactivate the plugin.
• Update or reinstall it.
• Check the debug and server error logs.
• Exit Recovery Mode.
• Retest the website normally.

Recovery Mode may not activate for every type of failure, including some background, scheduled or server-level errors.

11. Disable the Plugin Through File Manager or FTP

When a broken plugin prevents access to wp-admin, deactivate it directly from the server. This method is especially useful when a plugin not working in WordPress prevents you from accessing the WordPress dashboard.

Open your host’s File Manager or connect through SFTP. Navigate to:

/wp-content/plugins/

Find the affected plugin folder and rename it. For example:

contact-form-plugin

to:

contact-form-plugin-disabled

WordPress will no longer find the plugin at its registered location and will treat it as unavailable. WordPress documentation specifically describes renaming a plugin folder as a recovery method when dashboard access is blocked.

After regaining access:

• Open the Plugins screen.
• Confirm that the plugin has been deactivated.
• Restore the original folder name.
• Update, replace or inspect the plugin before reactivating it.

Disable All Standard Plugins

To disable all normal plugins at once, rename:

/wp-content/plugins/

to:

/wp-content/plugins-disabled/

Create or restore the original plugins folder name before reactivating plugins. WordPress’s troubleshooting documentation also describes disabling plugins when administrative menus are unavailable.

Do not delete plugin folders until you have a backup. Some plugins remove settings or database tables during a formal uninstall, while deleting files alone may leave data behind.

12. Deactivate or Update the Plugin With WP-CLI

WP-CLI provides a fast way to manage plugins when you have SSH access, making it a useful option when troubleshooting a plugin not working in WordPress on servers that support command-line access.

List installed plugins:

wp plugin list

Deactivate one plugin:

wp plugin deactivate plugin-slug

Deactivate all standard plugins:

wp plugin deactivate --all

Deactivate all except selected plugins:

wp plugin deactivate --all --exclude=plugin-one,plugin-two

Update a plugin:

wp plugin update plugin-slug

Reactivate it:

wp plugin activate plugin-slug

The official WP-CLI command documentation supports deactivating individual plugins, all plugins or all plugins except specified exclusions.

Run commands from the correct WordPress installation directory or specify its path. On Multisite, confirm whether the plugin is site-activated or network-activated before making changes.

WP-CLI is intended for users comfortable with SSH. A mistyped command may affect the live site, so take a backup and verify the current directory first.

Verify Plugin Files With WP-CLI Checksums

Before deleting and reinstalling a plugin, advanced users can check whether its installed files match the official files distributed through WordPress.org.

Verify one plugin:

wp plugin verify-checksums plugin-slug

Verify all eligible plugins:

wp plugin verify-checksums --all

Use strict verification when you also want changes to additional files, such as readme.txt, to be reported:

wp plugin verify-checksums --all --strict

Unexpected checksum failures may indicate:

• An interrupted or incomplete update
• Corrupted plugin files
• Manual modifications
• Missing plugin files
• Additional unexpected files
• A potentially compromised installation

A checksum mismatch does not automatically prove that a website has been hacked. Some plugins legitimately generate or modify files inside their own directories. Investigate each reported difference before deleting anything.

Premium, custom and privately distributed plugins may not have WordPress.org checksums. For these plugins, compare the installed files with a clean package downloaded from the developer’s official website or customer account.

13. Enable WordPress Debugging and Check Error Logs

Debugging reveals the specific file, function or line causing a failure, making it one of the most effective ways to diagnose a plugin not working in WordPress issue.

Open wp-config.php and add the following before the line that says WordPress editing should stop:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Reproduce the problem, then check:

/wp-content/debug.log

WordPress documents that WP_DEBUG_LOG writes errors to wp-content/debug.log, while WP_DEBUG_DISPLAY can prevent those messages from appearing publicly. The log can also capture errors generated during AJAX and WP-Cron requests.

Look for:

• PHP Fatal error
• Uncaught Error
• Call to undefined function
• Class not found
• Allowed memory size exhausted
• Maximum execution time exceeded
• Permission denied
• Deprecated
• Database error

Pay particular attention to file paths containing:

/wp-content/plugins/plugin-name/

An error path can identify the plugin involved, but the first plugin named is not always the root cause. Another plugin may have passed invalid data or loaded incompatible code earlier.

Turn Debugging Off Afterwards

Do not leave debugging enabled unnecessarily on a production website. Logs may contain filesystem paths or other sensitive technical information. WordPress Site Health warns when errors are displayed publicly or logs may be publicly accessible.

After testing, change the settings back or remove the temporary debugging lines.

14. Inspect JavaScript, REST API, AJAX and WP-Cron Errors

Not every plugin failure produces a visible PHP error. Interactive plugins often depend on browser-side JavaScript, WordPress AJAX, the REST API or scheduled processes. Checking these components can help identify the cause of a plugin not working in WordPress issue.

Check the Browser Console

Open the affected page, then open browser Developer Tools and select Console.

Look for red errors such as:

• Uncaught TypeError
• ReferenceError
• jQuery is not defined
• Failed to load resource
• 403 Forbidden
• 404 Not Found
• 500 Internal Server Error
• Content Security Policy errors
• Cross-origin request errors

WordPress’s JavaScript debugging guide recommends trying another browser, opening Developer Tools and recording the exact console error when interactive features fail.

Also inspect the Network panel. Repeat the failed action and check requests to:

• admin-ajax.php
• /wp-json/
• Plugin API endpoints
• External services
• JavaScript or CSS files

A 403 response may indicate a security rule, firewall or permissions problem. A 500 response usually requires checking PHP or server logs.

Test the WordPress REST API

Open:

https://example.com/wp-json/

A functioning installation normally returns a JSON response describing available REST API routes. WordPress warns against disabling the REST API because parts of WordPress administration depend on it.

Security plugins, server rules or custom code that block REST requests may break:

• Block editor functions
• Form submissions
• Search interfaces
• Product filtering
• Page builders
• Membership dashboards
• External integrations

Check Third-Party APIs, Licences and Webhooks

Some plugins depend on an external service even when their WordPress files are working correctly. Examples include payment gateways, email-marketing platforms, cloud backups, analytics services, social feeds, security scanners and customer relationship management integrations.

A disconnected or unavailable external service can make the plugin not working in WordPress appear to be caused by the plugin itself.

Check:

• Whether the plugin licence is active
• Whether the site is connected to the correct account
• Whether an API key or secret has expired
• Whether an access token needs to be refreshed
• Whether the external account has reached its usage limit
• Whether the external platform is experiencing an outage
• Whether the plugin’s webhook URL is correct
• Whether a webhook signing secret has changed
• Whether the website firewall blocks incoming webhooks
• Whether the host blocks outgoing HTTP requests
• Whether DNS resolution is working
• Whether SSL certificate validation is failing
• Whether the service still supports the installed plugin version

Review the plugin logs, browser Network panel and server logs for HTTP status codes.

After reconnecting an external account:

1. Save the plugin’s settings again.
2. Clear cached credentials or tokens.
3. Send a new test request.
4. Check the plugin log for the response.
5. Confirm that the external platform received the request.

Do not publish API keys, licence codes, access tokens or webhook secrets when asking for support.

Check WP-Cron and Loopbacks

Plugins use WP-Cron for scheduled emails, backups, imports, subscriptions, reports, cleanup and recurring synchronisation. Problems with WP-Cron can contribute to a plugin not working in WordPress issue when scheduled tasks fail to run as expected.

WP-Cron checks for due events during page loads rather than running continuously like a system scheduler. Low-traffic sites, blocked loopbacks or disabled cron settings can delay plugin tasks.

Check Tools → Site Health for:

• Missed scheduled events
• Failed loopback requests
• Blocked HTTP requests
• REST API problems

With WP-CLI, test the cron spawning system using:

wp cron test

Loopback requests are used for scheduled events and for checking whether plugin or theme edits cause site failures. WordPress identifies plugin and theme conflicts as common causes of loopback problems.

Ask your hosting provider to review firewall, DNS, SSL and server-level cron settings when the site cannot connect to itself.

Plugin Works but Emails Are Not Sending

A contact form, membership plugin, order system or notification plugin may process an action correctly even though the expected email never reaches the recipient. This is another situation where a plugin not working in WordPress may actually be caused by email delivery rather than the plugin itself.

In this situation, the plugin’s main function may be working while the email-delivery layer is failing.

Check:

• Whether the submission, order or registration appears in WordPress.
• Whether the recipient email address is correct.
• Spam, junk and quarantine folders.
• The website’s email or SMTP logs.
• The sender name and sender address.
• Whether the hosting server allows outgoing email.
• Whether an SMTP connection has expired.
• Whether the email service API key is still valid.
• Whether SPF, DKIM and DMARC records are configured.
• Whether a security plugin blocks the form request.
• Whether scheduled notifications depend on WP-Cron.
• Whether the email provider rejected or deferred the message.

A successful wp_mail() result does not guarantee that the recipient received the email. It only means WordPress processed the request without detecting an immediate sending error.

Determine where the failure happened:

• The form submission failed.
• WordPress failed to create the email.
• The web server failed to send it.
• The SMTP or transactional email service rejected it.
• The recipient’s email provider filtered it.
• The message was delayed or placed in quarantine.

Developers can inspect the wp_mail_failed hook or email logs for PHPMailer errors. Website owners can contact the hosting provider or email service with the sending time, sender address, recipient address and relevant error message.

Never publish email logs containing customer information, form entries or private email addresses.

15. Reinstall the Plugin and Check Permissions or Server Limits

When configuration and conflict tests do not solve the problem, the plugin files may be incomplete or corrupted. Reinstalling the plugin correctly is often one of the final steps in fixing a plugin not working in WordPress issue.

Safely Reinstall the Plugin

• Create a full backup.
• Export plugin settings when the plugin provides an export tool.
• Deactivate the plugin.
• Delete its files through the WordPress Plugins screen.
• Download a clean copy from WordPress.org or the official developer.
• Reinstall and activate it.
• Complete any database-update prompt.
• Test before restoring custom modifications.

Do not overwrite a live plugin with files from an unknown ZIP package.

Check Plugin Database Tables and Pending Database Updates

Some plugins create custom database tables during activation. Others change their database structure when a new version is installed.

A failed activation, interrupted update, or incomplete migration can leave the plugin files updated while its database structure remains outdated, resulting in a plugin not working in WordPress problem even though the plugin files themselves are correct.

Look for:

• A “database update required” notice
• A plugin setup or migration screen
• Missing forms, reports, orders or settings
• Database errors inside debug.log
• A “table does not exist” error
• A missing database column error
• A plugin version that differs from its stored database version
• A database prefix that changed during migration
• Insufficient permissions for the WordPress database user
• An update process that remains stuck or incomplete

Complete only the database update provided through the plugin’s official interface or documentation. Create a full database backup before starting the process.

Advanced users can check the WordPress database with:

wp db check

If the check reports damaged tables, create another backup and consult your hosting provider before running:

wp db repair

Do not manually create, rename, empty or delete plugin database tables unless the plugin developer has provided exact instructions.

Plugin tables may contain:

• Orders
• Form submissions
• Membership records
• Subscription data
• Customer information
• Licence records
• Scheduled tasks
• Plugin configuration

Database repair is not a universal fix for a plugin not working in WordPress. Use it only when a database check, debug log or server error identifies an actual database problem.

Check File Ownership and Permissions

Incorrect ownership or permissions can prevent a plugin from:

• Creating cache files
• Writing logs
• Uploading files
• Generating CSS
• Updating itself
• Creating directories
• Modifying rewrite rules

Permissions vary by hosting configuration. WordPress documentation explains that files generally need to be owned or writable by the appropriate account and warns that incorrect permissions can take a site offline.

On many standard configurations, directories commonly use 755 and files use 644, but these values are not universal. Never change all WordPress files and directories to 777 as a quick fix. WordPress warns that world-writable permissions can create serious security risks and may contribute to a plugin not working in WordPress issue if files are not managed correctly.

Ask your hosting provider to correct ownership when you are uncertain.

Check PHP and Hosting Resource Limits

Ask the host to review:

• PHP memory limit
• Maximum execution time
• Maximum input variables
• Upload size
• POST size
• Disk space
• Inode limits
• Database errors
• PHP extensions
• Web application firewall logs
• ModSecurity rules
• Server error logs

WordPress’s common-error documentation notes that memory exhaustion and maximum execution time can contribute to timeouts and failures, particularly on shared hosting.

If a plugin not working in WordPress issue continues after checking compatibility and conflicts, review these hosting limits before making additional changes.

Do not increase server limits without investigating why the plugin is consuming excessive resources. A coding loop, oversized query, corrupted job queue or incompatible add-on may be the underlying cause of a plugin not working in WordPress problem.

How to Prevent WordPress Plugin Problems

Troubleshooting becomes easier when every website change can be identified, tested and reversed. A consistent WordPress maintenance process can prevent many plugin failures and reduce the chances of a plugin not working in WordPress issue in the future.

Use these practices:

• Maintain automatic daily or scheduled backups.
• Confirm that your backups can be restored successfully.
• Test major WordPress and plugin updates on a staging website.
• Update one important plugin at a time.
• Read the changelog before installing a major plugin release.
• Avoid using “Update All” on a critical production website.
• Test important website functions after every major update.
• Keep WordPress, themes, plugins and PHP on supported versions.
• Remove inactive plugins that are no longer required.
• Avoid installing several plugins that perform the same function.
• Download plugins only from trusted and official sources.
• Monitor PHP errors and failed scheduled events.
• Monitor website uptime and important transaction pages.
• Record the last known working version of essential plugins.
• Enable automatic updates selectively.
• Maintain a recovery method that does not depend on wp-admin.
• Restrict administrator access to trusted users.
• Review plugin licences and external connections regularly.

Following these best practices can significantly reduce the likelihood of encountering a plugin not working in WordPress problem after updates, migrations or server changes.

Post-Update Testing Checklist

For an e-commerce, membership, service or lead-generation website, test the following after updates:

1. Homepage loading
2. WordPress administrator login
3. Contact-form submission
4. User registration and login
5. Website search
6. Product or content filtering
7. Shopping cart
8. Checkout process
9. Payment gateway
10. Order confirmation
11. Transactional email
12. Scheduled plugin tasks
13. Mobile display
14. Third-party integrations
15. Important landing pages

This process helps identify a plugin problem before it affects a large number of visitors or customers and can prevent a plugin not working in WordPress issue from impacting your live website.

What Not to Do When a WordPress Plugin Fails

Avoid actions that create additional problems when troubleshooting a plugin not working in WordPress issue.

• Do Not Edit Plugin Files on the Live Site: Direct edits are usually overwritten during the next update and can introduce syntax errors. Use hooks, a child theme, a custom integration plugin or the developer’s supported extension method.
• Do Not Set Permissions to 777: World-writable permissions expose files to modification by other users or processes on the server. Use the least permissive setting that works and ask the host to correct ownership.
• Do Not Deactivate Everything Without Planning: Disabling security, maintenance, membership, caching or e-commerce plugins can affect visitors and transactions. Use staging or session-based Troubleshooting Mode whenever possible.
• Do Not Leave Debug Output Visible: Public PHP notices reveal technical details and can break page layouts or API responses. Log errors privately and disable debugging after testing.
• Do Not Install an Abandoned Replacement Without Research: Check the plugin’s update history, compatibility information, support activity, documentation and developer identity before moving important site functionality to another plugin.

When Should You Contact the Plugin Developer?

Contact the developer after completing the basic conflict and environment checks if the plugin not working in WordPress issue still persists.

Provide:

• Plugin name and version
• WordPress version
• PHP version
• Active theme
• Relevant active plugins
• Exact error message
• Debug-log excerpt
• Browser-console error
• Steps required to reproduce the issue
• Whether the problem occurs with a default theme
• Whether the problem occurs when other plugins are disabled
• Whether it happens on staging and production

Remove passwords, licence keys, customer information, database credentials and private server paths before posting logs publicly.

For plugins hosted on WordPress.org, the plugin’s listing normally links to its dedicated support forum. WordPress recommends including the plugin name, relevant keywords and the exact error message when requesting assistance.

Which Fix Should You Try First?

If you’re troubleshooting a plugin not working in WordPress, start with the fix that best matches your issue.

• Plugin won’t activate → Start with Fix 3
• Website crashed → Start with Fix 10
• Can’t access wp-admin → Start with Fix 11
• Plugin stopped after update → Start with Fix 2
• Plugin only fails on one page → Start with Fix 4
• Plugin works for admin only → Start with Fix 7
• Form doesn’t submit → Start with Fix 14
• Plugin after migration → Read the Migration section after Fix 5
• Emails not sending → Read the Email section under Fix 14

WordPress Plugin Troubleshooting Checklist

Use this condensed checklist in order when fixing a plugin not working in WordPress issue:

1. Back up the site and database.
2. Record the exact symptom and error.
3. Confirm that the plugin is active.
4. Complete its configuration and dependency requirements.
5. Update WordPress, plugins and the theme.
6. Check PHP and database compatibility.
7. Clear browser, WordPress, server and CDN caches.
8. Refresh permalink rules.
9. Deactivate and reactivate the plugin.
10. Test for conflicts with other plugins.
11. Test with a default WordPress theme.
12. Review Site Health.
13. Use Troubleshooting Mode or Recovery Mode.
14. Enable WP_DEBUG_LOG.
15. Inspect JavaScript, REST API, AJAX and cron activity.
16. Reinstall clean plugin files.
17. Ask the host to check permissions and server limits.
18. Send complete diagnostic information to the developer.

Real-World Troubleshooting Experience

In many cases, a plugin not working in WordPress is caused by compatibility issues, plugin conflicts, server configuration, caching or PHP errors rather than a problem with the plugin itself.

Following the troubleshooting steps in this guide in order helps identify the root cause more quickly, reduces unnecessary downtime and avoids making changes that could create additional issues.

Expert Tip: Before updating plugins, changing PHP versions or modifying server settings, create a complete backup or test changes on a staging website whenever possible.

Conclusion

When a plugin not working in WordPress issue occurs, avoid immediately deleting files or changing random server settings. Start by confirming activation and configuration, updating the software stack, clearing caches and checking compatibility. Then isolate plugin and theme conflicts in a controlled environment.

For serious failures, WordPress Recovery Mode, File Manager, WP-CLI, Site Health, and debug logging provide reliable ways to regain access and identify the underlying error. Once you know whether the problem comes from the plugin, theme, PHP environment, REST API, WP-Cron or server configuration, you can apply a targeted fix instead of risking unnecessary changes to the entire website and resolve a plugin not working in WordPress issue more effectively.

FAQs

1. Can a plugin not working in WordPress slow down my website?

A. Yes. A malfunctioning plugin can increase server load, trigger PHP errors, create slow database queries or cause JavaScript conflicts that reduce website performance.

2. Why is a plugin not working in WordPress after changing my hosting provider?

A. Hosting changes can affect PHP versions, file permissions, caching, server modules and database settings, all of which may impact plugin functionality.

3. Can browser extensions make a plugin not working in WordPress appear broken?

A. Yes. Ad blockers, script blockers and privacy extensions can prevent JavaScript, forms or external services from loading correctly.

4. Why is a plugin not working in WordPress only on mobile devices?

A. Mobile-specific caching, responsive theme issues, JavaScript errors or CSS conflicts can cause plugin features to behave differently on smartphones and tablets.

5. Can a CDN cause a plugin not working in WordPress issue?

A. Yes. An outdated CDN cache or improperly cached dynamic pages may prevent updated plugin content or scripts from loading correctly.

6. Should I disable automatic updates if a plugin not working in WordPress occurs?

A. Only temporarily while troubleshooting. After identifying the cause, re-enable automatic updates whenever possible to maintain security.

7. Can low server resources cause a plugin not working in WordPress problem?

A. Yes. Insufficient memory, CPU limits, disk space or execution time can prevent plugins from completing tasks successfully.

8. Is it safe to reinstall a plugin not working in WordPress?

A. Yes, provided you create a backup first and understand whether the plugin stores its settings or data after reinstallation.

Kylie Kimberly

Kylie Kimberly is a passionate SEO writer, content strategist, and digital growth enthusiast who helps brands create content that is both useful for readers and optimized for search engines. Her work focuses on building strong content foundations through keyword research, SEO-friendly writing, content optimization, and audience-focused strategy. She believes great content should do more than rank on Google — it should educate, engage, and build trust. Kylie Kimberly enjoys simplifying complex digital marketing ideas into clear, practical content that businesses, bloggers, and creators can use to grow online. With a strong interest in organic visibility and long-term brand growth, she aims to create content strategies that attract the right audience, improve search performance, and support meaningful digital success.

See Full Bio