LTD is back · Limited time only

How to Disable All Updates in WordPress

Last updated on July 24, 2026

Key Takeaways

• Single toggle, no nested options

• Quick WordPress optimization with one click

• No configuration required (just enable/disable)

• Does not affect core WordPress functionality

• Reversible (disable to restore default behavior)

What Is this feature?

Disable All Updates in Classic Monks prevents WordPress core, plugin, and theme updates from being applied. Updates must be managed manually via the database or WP-CLI. This is one of many WordPress optimization features available in the Performance tab.

Why You Need It

Automatic updates can break custom code, change functionality, or introduce conflicts. Disabling updates gives you full control over when and how updates are applied.

How to Enable this Feature in WordPress

Step 1: Navigate to Settings

Click into the Classic Monks plugin settings in your WordPress dashboard.

Step 2: Go to the Performance Tab

Click on the Performance menu, then click the WP Optimizations subtab.

Step 3: Enable the Feature

Toggle on the feature.

Step 4: Save Changes

Click Save Changes.

Step 5: Test

Clear your browser cache and visit the frontend. Verify the feature is working as expected.

Configuration Options

Option Description Default
This feature Master toggle. Off

No nested options.

What Gets Affected

  • The feature behavior: enabled as configured
  • The site performance: improved as described

What Does NOT Get Affected

  • The WordPress admin: unchanged
  • The site content: unchanged
  • The plugin functionality: unchanged

Common Use Cases

Production sites with custom code

Sites with custom code that may break on update need manual control. Disabling all updates ensures no unexpected changes break the site.

Staging-to-production workflows

For sites that test updates on staging first, disabling updates on production ensures only tested updates are applied.

Troubleshooting

The feature is not taking effect

Cause: The toggle is off, or a caching plugin is serving the old page.
Fix: Verify the toggle is on. Clear all caching layers.

The feature breaks another plugin

Cause: Another plugin depends on the functionality that this feature disables.
Fix: Disable this feature if it breaks another plugin. The features are designed to be toggled independently.

Developer integration

This feature registers 6 WordPress hooks in disablers.php:

Filters:

  • auto_update_core calls __return_false() (Disables core auto-updates)
  • auto_update_plugin calls __return_false() (Disables plugin auto-updates)
  • auto_update_theme calls __return_false() (Disables theme auto-updates)
  • automatic_updater_disabled calls __return_true() (Signals automatic updater is disabled)
  • pre_http_request calls cm_block_wordpress_org_requests() (Blocks WordPress.org API requests)
  • pre_site_transient_update_core calls __return_null() (Prevents core update checks)
// Hooked in disablers.php
add_filter( 'auto_update_core', '__return_false' );

The feature modifies WordPress behavior by registering or removing hooks. Disabling it reverses those changes and WordPress returns to its default behavior.

Before you enable this feature

  1. Test on staging first to verify no conflicts with your theme or other plugins
  2. Check dependent plugins that may rely on the functionality being modified
  3. Monitor after enabling for any unexpected behavior on the frontend

How it works under the feature

This feature runs during the WordPress initialization phase. When enabled, its PHP code registers hooks that modify specific WordPress behaviors. The changes are non-destructive and reversible.

No database schema changes are made. The feature state is stored as a boolean value in the wp_options table and can be toggled at any time from the admin settings.

Sumit Your Ideas or Feature Requests

All submissions go through a manual review, so not every idea will be published. That said, the most upvoted ideas are given priority on our official roadmap.Please check if your idea already exists before submitting. If you find it, simply upvote it to help us prioritize it.