Plugin not working in WordPress: the usual causes
A plugin not working in WordPress almost always comes down to one of six things: a cached copy of the page hiding your change, a PHP version the plugin does not support, a clash with another plugin or your theme, a JavaScript error in the browser, stale rewrite rules, or a server limit such as memory or file permissions. Work through the checks below in order, because the cheap ones fix most cases, and take a backup before you change anything.
The symptoms look different but share these causes:
- Settings do not save, or revert after you click Save Changes.
- A shortcode such as
[contact-form-7 id="12"]appears on the page as plain text. - The plugin is active but its feature does nothing: no form, no slider, no button.
- Two plugins fight, so one stops working the moment the other is activated.
- A fatal error or "critical error" message after an update.
Quick checklist
- Purge every cache: LiteSpeed Cache, Cloudflare (if you use it) and your browser.
- Compare the plugin's minimum PHP and WordPress versions with your site.
- Run a conflict test with all other plugins off, or use troubleshooting mode.
- Switch to a default theme such as Twenty Twenty-Five.
- Turn on
WP_DEBUG_LOGand readwp-content/debug.log. - Open the browser console and look for red JavaScript errors.
- Flush permalinks, then check file permissions and the memory limit.
- Roll back to the previous plugin version if the problem began after an update.
Step 1: purge the caches
A page cache can keep serving the old version of a page for hours, so a plugin you have just configured looks as if it does nothing. Clear caches from the server outwards:
- LiteSpeed Cache: in the admin toolbar, open the LiteSpeed menu and choose Purge All.
- Cloudflare: in the dashboard, go to Caching, then Configuration, and use Purge Everything, or purge the single URL.
- Browser: press
Ctrl+Shift+R(Cmd+Shift+Ron a Mac), or test in a private window.
Minify and combine options in caching or optimisation plugins also break other plugins' scripts. If a feature works with optimisation off, add that plugin's script to the exclusion list rather than leaving optimisation off for the whole site.
Step 2: check the PHP and WordPress requirements
Every plugin page on WordPress.org shows, in the sidebar, the minimum WordPress version and PHP version the plugin needs. WordPress blocks activation when your site is below the stated minimums, but premium ZIP plugins may not declare them. A plugin written for PHP 8 can throw a fatal error on PHP 7.4, and an old, unmaintained plugin can fail on PHP 8 because functions it relies on, such as create_function() and each(), were removed in PHP 8.0. Check your versions under Tools > Site Health > Info, or with WP-CLI:
wp --info
wp core version
wp plugin list --fields=name,status,version,update
Step 3: run a WordPress plugin conflict test
A WordPress plugin conflict happens when two plugins load the same library, hook the same action or ship clashing JavaScript. To find it, leave only the problem plugin active and test again. If it now works, reactivate the others one at a time until it breaks; the last one you switched on is the culprit.
On a live site, do this without visitors noticing. The Health Check & Troubleshooting plugin from WordPress.org has a troubleshooting mode that disables all plugins and switches to a default theme for your logged-in session only, while visitors see the normal site. You then enable plugins one by one from its admin bar menu. Disabling troubleshooting mode, logging out or clearing your cookies ends it.
With SSH and WP-CLI the same test is quick, but unlike troubleshooting mode it changes the live site for every visitor, so use a staging copy or a quiet hour and take a backup first. Save the list of active plugins so you can restore them:
wp plugin list --status=active --field=name > active-plugins.txt
wp plugin deactivate --all
wp plugin activate problem-plugin
# test, then bring the others back one at a time
wp plugin activate other-plugin
# when you finish, restore the original set
wp plugin activate $(cat active-plugins.txt)
If you cannot reach wp-admin at all, rename the wp-content/plugins folder over FTP or the File Manager, as our white screen of death guide explains.
Step 4: switch to a default theme
Themes bundle their own scripts and sometimes override plugin templates. Activate a default theme from Appearance > Themes, or with wp theme activate twentytwentyfive (if it is not installed, run wp theme install twentytwentyfive --activate), and test again. This also changes the theme for visitors, so prefer troubleshooting mode or staging on a live site. If the plugin now works, the theme is at fault: update it, or report it to the theme's developer.
Step 5: how to fix WordPress plugin errors with WP_DEBUG_LOG
You need the actual error message. Add these lines to wp-config.php, above the comment that begins /* That's all, stop editing!, and replace any existing WP_DEBUG line rather than defining it twice:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Reproduce the problem, then open wp-content/debug.log. The file path in each line, such as wp-content/plugins/some-plugin/includes/class-api.php, names the plugin responsible. Call to undefined function usually means a missing dependency or the wrong PHP version, and Allowed memory size of ... bytes exhausted means the memory limit in Step 7. When you finish, set WP_DEBUG and WP_DEBUG_LOG back to false and delete debug.log, because a log in wp-content can be downloaded by anyone who guesses its URL.
Step 6: look for JavaScript errors in the browser console
When settings will not save or a button does nothing, the fault is often in JavaScript rather than PHP, so debug.log stays empty. Press F12, open the Console tab and reload. A red error naming a plugin's .js file points at the cause. The Network tab shows failed requests: a 403 on admin-ajax.php or /wp-json/ often means a security plugin or firewall rule is blocking the save, while a 500 sends you to the server log and our 500 Internal Server Error guide.
Step 7: permalinks, file permissions and memory
Flush permalinks
Plugins that add custom post types or endpoints, such as shops, events or membership pages, return 404 errors until the rewrite rules are rebuilt. Open Settings > Permalinks and click Save Changes without editing anything, or run wp rewrite flush.
File permissions
If a plugin cannot write its cache, uploads or log files, it often fails quietly. The usual WordPress setting is 755 for folders and 644 for files, owned by your hosting account user. Never use 777, which lets any process on the server change your files:
find wp-content/plugins -type d -exec chmod 755 {} \;
find wp-content/plugins -type f -exec chmod 644 {} \;
PHP memory limit
By default WordPress tries to raise PHP memory to 40 MB on a single site. Page builders, backup tools and WooCommerce extensions often need more. Raise it in wp-config.php, within the limit your hosting allows:
define( 'WP_MEMORY_LIMIT', '256M' );
Plugin not working after update: roll back
If the plugin stopped working after an update, the fastest fix is usually to return to the previous version while the author fixes the bug. Since WordPress 5.2, a fatal error during a normal page load shows visitors a "There has been a critical error on this website" message and WordPress emails the admin address a recovery mode link, which lets you log in with the faulty plugin paused for your session only.
For plugins hosted on WordPress.org, the WP Rollback plugin adds a Rollback link that installs an earlier release. With WP-CLI, install a specific version over the current one:
wp plugin install plugin-slug --version=2.4.1 --force
Turn off auto-updates for that plugin until a fixed release appears, and read its changelog before updating again.
When to contact the plugin author
Contact the developer when the problem remains with every other plugin disabled, a default theme active and a supported PHP version, because then the fault lies in the plugin itself. Use the plugin's support forum on WordPress.org, or the vendor's helpdesk for premium plugins. Include your WordPress, PHP and plugin versions, the exact lines from debug.log or the console, and the steps that reproduce the problem, with any private paths or keys removed.
WordPress plugin not working on Bigdomainhost
Bigdomainhost WordPress hosting runs on LiteSpeed with LSCache in our Mumbai data centre, with the LiteSpeed Cache plugin installed and configured, so Purge All is the first thing to try. Every plan runs cPanel as well, so you can use its File Manager to rename a plugin folder when wp-admin will not load. Nothing is blocked or force-installed; we only disable plugins that duplicate server-level caching, and we tell you before doing it.
Before a risky plugin update, take an on-demand backup; daily backups with self-service restore are kept for 30 days. On Advanced, Master and Elite, one-click staging lets you clone the site, test the update and push it back once it works. SSH access for WP-CLI is available on request on web and cPanel plans. If you are stuck, call +91 75994 50220 during IST hours, WhatsApp the same number at any time, or email support@bigdomainhost.com.
Sources (checked )
- WordPress Developer Resources: Debugging in WordPress
- WordPress Developer Resources: Editing wp-config.php
- WordPress.org Plugins: Health Check & Troubleshooting
- WP-CLI documentation: wp plugin install
- WordPress.org Documentation: Recovery Mode