Skip to content

Updates in wp-admin

The Updates in wp-admin setting takes updates away from people signed in to WordPress. They no longer see or apply updates in wp-admin, except the accounts you exempt, while ConstellaWP keeps detecting them and applying them with its backups, ordering and homepage checks. Use it on client sites where an administrator clicking Update now would bypass all that.

The setting is per site and available on every plan. It needs the latest ConstellaWP Agent and does not work on multisite networks (see Limits).

  1. Open the site and go to Settings.
  2. In Updates in wp-admin, pick a level.
  3. Under Exempt accounts, enter the WordPress usernames that keep access, one per line. Usually your own.
  4. Click Save.

ConstellaWP sends the setting to the site right away. If the site does not answer, the lock applies at its next check-in, within five minutes. Owners and admins can change the setting, and each change is logged in the site’s Events as Update lock changed.

Once the site confirms, the card shows Active, and the site Dashboard shows Updates locked or Code locked under Updates in wp-admin. That badge stays orange while the lock does not hold, until the site confirms for instance. The card lists anything that needs a look, and so does the badge when you hover it.

In wp-admin Updates only through ConstellaWP Code locked
Update WordPress, plugins, themes and translations Blocked Blocked
Replace an installed plugin or theme by uploading a ZIP Blocked Blocked
Add plugins and themes (install or upload) Allowed Blocked
Delete plugins and themes Allowed Blocked
Edit plugin and theme files Allowed Blocked
Activate and deactivate plugins, switch themes Allowed Allowed
Install a new language, use Site Health Allowed Allowed

Code locked also hides the screens that plugins reserve to people who can install plugins, such as the Gravity Forms Add-Ons page.

  • No update counts, update links or bulk update actions. The banner WordPress shows when a new version is out, which would otherwise ask them to notify the site administrator, is gone too.
  • On the Plugins screen, a notice that reads Updates on this site are managed by your maintenance provider. It does not name ConstellaWP: your client is the one reading it.
  • No Enable auto-updates links, so they cannot hand a plugin or theme to WordPress’s automatic updates.
  • While the lock holds, Site Health no longer counts pending WordPress, plugin and theme updates. Its results are shared, so this applies to every account, exempt ones included.

The lock refuses these permissions at the moment WordPress checks them, the way WordPress itself applies DISALLOW_FILE_MODS. Roles and user accounts are left untouched. A role editor such as User Role Editor, or a reset of the default capabilities, neither sees the lock nor lifts it, and no role can grant the blocked actions back. When the lock lifts, everyone has exactly the access their role gives them.

Exempt accounts are left out of the lock: they keep the access their role gives them. Use them for yourself and your team.

  • Enter WordPress usernames, the login the account signs in with, not an email address or a display name. One per line, commas work too. Case does not matter.
  • Up to 20 accounts.
  • A username with no account on the site is flagged on the card: No account named … on this site: whoever creates one would be exempt. Fix the spelling or remove it. Otherwise anyone who can create users on the site could create that account to get around the lock.

The lock is about people in wp-admin. It leaves alone:

  • ConstellaWP. The agent keeps detecting pending updates, including premium plugins’, and applies the ones you queue from the dashboard.
  • WordPress security releases. WordPress keeps installing its minor releases on its own, which carry its security fixes, as well as the fixes wordpress.org forces on sites when a vulnerability is critical.
  • Automatic updates already turned on. Plugins and themes whose auto-updates were on before the lock keep updating through WordPress, outside ConstellaWP. The card gives their number, for example 3 plugins or themes still update automatically through WordPress, outside ConstellaWP. To bring them under ConstellaWP, turn their auto-updates off from an exempt account, on the Plugins and Themes screens.
  • Recovery mode. After a fatal error, the administrator who opens WordPress’s recovery link is not locked out, since an update is often the fix.

WordPress only reports a failed automatic core update to people who can update core. When one fails on a locked site, the card says so instead: queue a WordPress core update from the site’s Updates page.

A site must never stay locked once ConstellaWP no longer maintains it. The lock lifts by itself, with nothing to undo in WordPress, when:

  • The site is disconnected: Disconnect or a new token under Settings → ConstellaWP in WordPress, or the site revoked or deleted in ConstellaWP (the lock lifts at the site’s next check-in).
  • The agent is deactivated.
  • Three days pass without contact. The lock is a 72-hour lease that every check-in renews. A site that can no longer reach ConstellaWP unlocks itself 72 hours after its last contact.
  • The site is beyond your plan’s site limit. A read-only site is no longer maintained from ConstellaWP and its settings cannot be changed, so it is unlocked at its next check-in.

Unless the site was deleted, the setting stays in ConstellaWP. Once the site checks in again, connected and within your plan, the lock comes back.

Restoring a backup keeps the lock as it is set in ConstellaWP today, whatever it was when the backup was taken.

To lift the lock from the site itself, whatever the dashboard says, add this line to wp-config.php, above /* That's all, stop editing! */:

define( 'CONSTELLAWP_DISABLE_UPDATE_LOCK', true );

The lock stops at the next page load. After the site’s next check-in, the card shows Lifted on the site itself by CONSTELLAWP_DISABLE_UPDATE_LOCK in wp-config.php. Remove the line to let the lock apply again.

It is also the way out when the agent cannot be deactivated normally: the agent stays loaded when it is removed from the active plugins without going through WordPress, directly in the database for example.

  • A guardrail, not a security boundary. The lock keeps updates out of reach in wp-admin. Anyone with file access (SFTP, the host’s file manager) or WP-CLI can still change code. An administrator can also deactivate the ConstellaWP Agent, which lifts the lock and shows in ConstellaWP.
  • Delete and reinstall. At the Updates only through ConstellaWP level, deleting a plugin and installing it again gets its latest version. Code locked closes that.
  • No multisite yet. Updates on a multisite network apply to the whole network at once, so the levels are unavailable there.
  • The latest agent is required. With an older ConstellaWP Agent, the levels are unavailable and the card asks you to update it. Update it from the Agent Updates card in the same Settings page, or turn on Update the agent automatically.