“You Won’t Believe How Easy it is to Put an End to Auto-Updates on Your WordPress Plugins!”

Perplexing and Bursting Tutorial on How to Stop Auto-Update Plugins in WordPress

WordPress is a wildly popular platform for building both websites and blogs. This CMS is loaded with features and one of the key features is the ability to automatically install and update plugins. However, updating plugins may lead to compatibility issues or worse, breaking your website. As such, many website owners choose to disable this auto-update feature of WordPress. In this tutorial, we’ll guide you on how to stop auto-update plugins in WordPress.

To Update or Not to Update, That is the Question

Plugins should be updated to improve security and ensure proper functionality. But in some cases, an update can ruin your site’s functionality because it’s not compatible with your WordPress version or other plugins. When this happens, you need to identify the cause and find a way to fix it. However, if you decide to disable this auto-update feature, you can manually update your plugins as needed. Another reason some people disable updates is to prevent the update from overriding custom CSS or code. Some plugins automatically add CSS or JavaScript code to your website’s header or footer. If you have customized your codes and changes have been made, the plugin update can wipe off your changes. To avoid this situation, you can disable the automatic update feature and manually update your plugins once you make changes to your codes.

READ MORE  "Slash WordPress Site Size with These Surprising Hacks - You Won't Believe the Results!"

How to Disengage Automatic Plugin Updates

You can disable auto-updates in WordPress in several ways. Below are some common ways to do so:

1. Disable Automatic Updates for All Plugins

To stop automatic updates for all plugins on your website, you can add the following code to your website’s wp-config.php file:

define( 'WP_AUTO_UPDATE_PLUGIN', false );

This code will stop all automatic updates for plugins, including security updates. If you’d like to stop only major updates, you can use the following code instead:

define( 'WP_AUTO_UPDATE_CORE', minor );

This code will allow minor updates but manual intervention will be needed when major updates are released.

2. Disable Automatic Updates for Specific Plugins

If you only want to stop auto-updates for specific plugins, you can use a plugin. Several plugins are available that allow you to selectively disable automatic updates. One of these plugins is the “Easy Updates Manager” plugin.

To use “Easy Updates Manager,” you must install and activate it on your website first. Once activated, go to the “Dashboard” and click on “Updates Options” in the “Easy Updates Manager” section.

From there, you can choose which plugins to disable automatic updates for. You can also choose which types of updates to disable, such as major updates, minor updates, or both.

3. Use a Plugin to Disable Automatic Updates

Another option is to use a plugin dedicated to disabling automatic updates. One such plugin is the “Disable Updates Manager” plugin.

To use this plugin, you must install and activate it on your website. Once activated, go to the “Dashboard” and click on “Disable Updates” in the “Disable Updates Manager” section.

READ MORE  "Master the Art of Moving Your Wordpress Site Like a Pro!"

From there, you can select which updates to disable, including plugin updates, theme updates, or both. You can also choose which types of updates to disable, such as minor, major, or both.


Disabling automatic updates for plugins can prevent compatibility issues and ensure that custom code changes are not overwritten. To stop auto-update plugins in WordPress, you can modify the methods we have listed above, such as adding code to your website’s configuration file, using a plugin or disabling updates for specific plugins. But if you find working with these methods confusing or too complex, it’s always a good idea to hire a WordPress developer for help.

Leave a Reply

Your email address will not be published. Required fields are marked *