Updates
On a site’s dashboard and its Updates page, ConstellaWP shows pending updates reported by the agent (refreshed on heartbeat, with wordpress.org checks at most once per hour). Owners and admins can queue updates; members can view them.
What you can update
Section titled “What you can update”| Category | How it is selected |
|---|---|
| WordPress core | One toggle when a newer version is available |
| Plugins | Per plugin. Premium plugins without a package URL are marked License required and cannot be updated from ConstellaWP |
| Themes | Per theme, same license rule as plugins |
| Translations | Language packs pending on the site |
You can mix categories in one Review updates pass. That queues an update_all job with your selection.
Optional backup first
Section titled “Optional backup first”If the organization has a storage destination, the review panel offers Take a full backup first. When enabled, ConstellaWP queues a backup job and keeps the update queued until that backup finishes. If the backup fails, the update does not run.
Without a destination, the toggle is unavailable. Configure storage before relying on rollback.
The agent also snapshots plugins/themes it is about to update and rolls a component back when its update breaks a homepage that was working (you will see a note on the job that the previous version was restored). That is not a full-site restore — use Restore for that. WordPress core has no snapshot: if a core update breaks the homepage, the plugin updates that follow still run, since they are often the fix, and the job says whether the homepage works when it ends.
How a job runs
Section titled “How a job runs”- ConstellaWP creates the job and the worker delivers it to the agent.
- The agent prefers WP-CLI when the capability is present, otherwise PHP (
shell_exec/WP_Filesystem). - Before changing anything, the agent loads the site’s homepage. If the site cannot reach its own homepage, nothing is updated and the job says why: an update that cannot be checked is not applied.
- Items run in this order: WordPress core, plugins, themes, translations. Core goes first because WordPress refuses a plugin or theme version that requires a newer WordPress. A plugin is updated after the plugins it depends on (WooCommerce before its extensions, Elementor before Elementor Pro, WPML and Gravity Forms before their add-ons), and a parent theme before its child theme.
- After each plugin, theme, or core update, the agent loads the homepage again, bypassing page caches, and rolls back an update that broke it.
- Each updated component emits events (
plugin.updated,core.updated, and similar).
If the request running the job stops on a PHP fatal error (memory or time limit, for instance), the agent puts back the plugin or theme it was replacing and reports the job right away, with what it had already updated. A process killed outright by the host cannot report anything: the job is then marked failed once the timeout passes.
Typical timeout: 10 minutes per category, 30 minutes for update_all.
Notes on updated items
Section titled “Notes on updated items”An item can be updated and still carry a note in the job details:
- WooCommerce database update. After some WooCommerce updates, WooCommerce waits for an administrator to start its database update from the notice it shows in wp-admin. The job tells you when that is the case.
- Error after the install. Some plugins run code at the end of their own update. When that code fails in the request that installed the update, the new version is kept and the error is shown on the item.
WP Engine and core updates
Section titled “WP Engine and core updates”If the site is linked to a WP Engine hosting account, WordPress core is managed by the host. ConstellaWP does not offer update_core for those linked sites. Plugins, themes, and translations still go through the agent.
Keep updates out of wp-admin
Section titled “Keep updates out of wp-admin”To stop administrators from applying updates themselves in wp-admin, turn on Updates in wp-admin in the site’s Settings. ConstellaWP keeps detecting and applying updates, and the accounts you exempt are left out of the lock.
Good practice
Section titled “Good practice”- Take a BYOS backup before core or many plugin updates.
- Update premium plugins in wp-admin when ConstellaWP shows License required.
- Watch the Jobs page until the job is
successorfailed. Owners and admins can retry a failed job.