Linux 软件免费装
Banner图

Disable Updates - Version Locker: Stop Automatic Plugin, Theme and Core Updates

开发者 alphadev01
更新时间 2026年8月12日 19:43
PHP版本: 7.0 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

automatic updates rollback plugin updates disable updates update manager

下载

1.2.1 1.2.2 1.2.3 1.3.0

详情介绍:

Version Locker is an update manager that lets you disable automatic updates in WordPress and keep any plugin, theme, or WordPress core itself on the version you are running today. Turn off updates for one plugin, for every plugin at once, for themes, or for WordPress core. Once something is locked it will not update automatically, and the one-click update button is withheld until you unlock it. Every switch is reversible in one click. Stop Automatic Updates, Without Losing Track of Them Most plugins that disable updates simply hide them, and six months later you have no idea how far behind you are. Version Locker still shows you the update it is holding, including the new version number and whether it is a major, minor, or patch release. You can add a note explaining why something is pinned, and set a date for the lock to release itself. What Makes This Different Three things you will not find together anywhere else: Who This Is For Common Problems It Solves Full Feature List How It Works Version Locker uses WordPress filters to hide update notices and refuse update attempts. Locking never touches your files: nothing is added, changed, or removed on disk. The one exception is Roll Back, which only runs when you ask for it. It downloads the version you pick from WordPress.org and replaces the installed files, exactly as a normal update would. You are warned and asked to confirm first. No account, no API key, no external service. Nothing is sent anywhere.

安装:

  1. Install through the WordPress Plugins screen, or upload the folder to /wp-content/plugins/
  2. Activate the plugin
  3. Go to Tools > Version Locker
  4. Toggle the lock on anything you want to keep where it is

屏幕截图:

  • Rolling a plugin back to an earlier version published on WordPress.org
  • The Settings tab, with the waiting period and the site-wide update switches
  • The activity log, showing who changed what and when

升级注意事项:

1.3.0 Adds rollback to an earlier version, a waiting period before new releases are offered, and saving your locks to a file to reuse on another site. Locks are no longer loaded on front-end page views, which removes work every visitor was paying for. On Multisite, a lock set by any site now protects the shared files network-wide. Your locks and settings are preserved on upgrade. 1.2.3 Tested with WordPress 7.0. Fixes the "update available" indicator for locked items, the audit Role column, filter tabs, and on-screen feedback. Email notifications have been removed. Your locks and settings are preserved on upgrade.

常见问题:

How do I stop WordPress from updating plugins automatically?

Install Version Locker and go to Tools > Version Locker. Toggle the lock on any plugin to hold it at its current version, or turn on "Disable all plugin updates" in the Settings tab to stop every plugin update at once. Both are reversible at any time.

How do I disable automatic updates for just one plugin?

Lock that single plugin from the Plugins tab. Every other plugin keeps updating as normal. Locks are per item, so you are not forced into an all-or-nothing choice.

Can I disable WordPress core updates?

Yes. The Settings tab has a separate switch for core updates, which also turns off core auto-updates. It is independent of your plugin and theme locks.

How do I go back to an older version of a plugin?

Lock the plugin, then use the roll back link on its row. You will see every version WordPress.org still publishes, older than the one you have installed. Pick one, confirm, and Version Locker reinstalls it and pins the plugin there so the update you are stepping away from does not come straight back. Take a database backup first: rolling back replaces files, but it cannot undo database changes a newer version already made.

Can I delay updates instead of blocking them completely?

Yes. Set a waiting period in the Settings tab and every new release is held for that many days before WordPress offers it. Each release gets its own window. This only delays updates. It never starts one, and it never turns on auto-updates for a site that had them off.

Will this stop the update notification badge in my admin menu?

Locked items are removed from the counts WordPress uses for the update badge, so the number reflects only the updates you can actually apply. Version Locker still shows you the held update on its own screen, including the new version number, so nothing is hidden from you.

Does locking a plugin make my site insecure?

It can, if you lock something and forget about it. That is why every lock records the version it was pinned at, shows how far behind you have fallen with a major, minor, or patch badge, and can be given a date to unlock itself. Locking is meant to delay an update you have not tested yet, not to avoid updating forever.

Does this modify plugin or theme files?

Locking does not. It only uses WordPress filters to control update behavior, so your files are left exactly as they are. Roll Back is the exception, and it only runs when you ask for it. Choosing a version and confirming the warning replaces the installed files with that release, the same way an update does.

Will locked items still show update available?

Yes. The Plugins and Themes tabs show an "update available" indicator with the new version number for locked items, but the update is held and the update button will not appear until you unlock.

Can I still update a locked item?

Yes, just unlock it first. Updates work normally once unlocked.

What is the difference between locking one item and turning off all updates?

Locking targets specific items. The site-wide switches turn off ALL plugin updates, ALL theme updates, or core updates at once.

Does "Disable all plugin updates" stop someone uploading a plugin ZIP by hand?

No. The site-wide switches only stop WordPress update checks: update notices, one-click updates, and auto-updates. A plugin uploaded by hand from Plugins > Add New > Upload Plugin is treated by WordPress as an install, so an update or downgrade ZIP will still install. To stop that, lock the specific plugin or turn on "Block plugin installs". Files changed directly on the server over FTP, SSH, or cPanel cannot be blocked by any plugin, because WordPress does not run during a direct file copy.

Can I copy my settings to another site?

Yes. Export your locks and settings to a file from the Settings tab, then import that file on another site. Nothing is applied on upload: you first see which locks would be added or removed and which settings would change. An imported file can only change Version Locker's own settings, and locks for items not installed on the receiving site are skipped.

Does this work on Multisite?

Yes. Each site keeps its own list of locks, so what one site shows as locked is its own business. Protection works across the whole network, though, because it has to. Plugin and theme files exist once and are shared by every site, so a lock set on any single site stops those files being updated from anywhere, including Network Admin. Without that, one site could overwrite the version another site deliberately kept.

Does it slow my site down?

No. Version Locker does no work at all on front-end page views. Its data is only read when WordPress is deciding about updates, which happens in the admin and on cron, never when a visitor loads a page.

What happens if I delete the plugin?

By default, all locks and settings are preserved on uninstall. To delete all data on removal, turn on "Delete everything on uninstall" in the Settings tab before uninstalling.

更新日志:

1.3.0 Added Performance Fixed 1.2.3 - 2026-06-10 Compatibility Fixed Removed Added Changed Security Other 1.2.2 - 2026-01-24 New Improvements Security 1.2.1