309: How to Disable WordPress Plugins
In this tutorial:
When troubleshooting a WordPress issue, it may be necessary to disable the plugins. You can easily disable (deactivate) plugins from the WordPress Dashboard, but this can be an arduous task if you have a large amount of plugins, or do not have access to your Admin Dashboard . The quickest method for disabling all your plugins is to rename the entire folder plugins folder. In this tutorial we will show you how to disable your WordPress plugins from the dashboard, and also by renaming the plugins folder in cPanel.
Disabling Plugins in the Dashboard
- Log in to your WordPress Dashboard.
- Click Plugins in the navigation menu.
- Find the plugin you want to disable, and click the Deactivate link.
You will then see a message stating "Plugin deactivated" and your plugin is now disabled.
Disabling Plugins in cPanel
- Login to your cPanel.
- Click the File Manager in the Files section.
- Navigate to your WordPress installation folder, and open the wp-content folder.
- Right-click the plugins folder, then select Rename.
- Rename the plugins folder, for example "plugins.old" then click the Rename File button.
All of your WordPress plugins are now disabled.
Congratulations, now you know how to disable (deactivate) your WordPress plugins from the Dashboard, and cPanel!
Support Center Login
Social Media Login
2016-12-28 11:02 pm
If you disabled them by renaming the folder, you'll have re-name the folder BACK to what it was before. Then you need to login to the WordPress Admin and go to the plugins section. Then you can activate each plugin that was previously disabled.
If you have any further questions, please let us know.
2017-06-20 1:54 pm
I have a fatal error occuring when I tried to update plug in and wordpress new OS version. Error states:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 88 bytes) in /home/heidishangups/public_html/wp-includes/class-wp-hook.php on line 300
I'm not a tech person so step by step instructions would be ideal.
2017-06-20 3:57 pm
If the error is triggered by that particular plugin then the best thing to do is contact the plugin developer for suggestions and leave the plugin disabled in the meantime.