Skip to main content
The Update Manager provides a single page for updating plugins, themes, and WordPress core — with pre-update backups, a full history log, and the ability to schedule or roll back updates.
Update Manager was added in v2.6.0.

Overview

The Update Manager has three tabs:
TabDescription
AvailableLists all pending updates for plugins, themes, and WordPress core
HistoryLog of every update run through this interface, with rollback support
ScheduledSchedule updates to run automatically at a specified date and time

Available updates tab

The Available tab shows every item with a pending update. Each row displays:
  • Name — plugin, theme, or core name
  • Type badge — Plugin (blue), Theme (purple), or Core (orange)
  • Current version — the installed version
  • New version — the version available from WordPress.org
  • Changelog link — opens the WordPress.org changelog page

Refreshing the update list

Click Check for Updates (top-right) to force WordPress to re-query WordPress.org for fresh update data immediately, without waiting for the scheduled cron check.

Running an update

1

Find the item to update

Locate the plugin, theme, or core update in the list.
2

Click Update

Click the Update button on the row. The button shows a spinner while the update runs.
3

Monitor status

The row status icon changes to reflect the result:
  • Green checkmark — update succeeded.
  • Red X — update failed (hover for error detail).
Pre-update backups are stored in wp-content/wmp-backups/updates/ and are used for rollback. The directory is protected with .htaccess to block HTTP access.

Bulk updating

Select multiple items using the checkboxes and click Update Selected to run all chosen updates sequentially.

History tab

The History tab shows every update that was run through Update Manager, including the version it came from and went to, the date, and its final status. Each history entry shows:
ColumnDescription
NamePlugin, theme, or core name
TypePlugin, Theme, or Core
From → ToVersion transition (e.g. 1.2.0 → 1.3.0)
DateTimestamp of the update
StatusDone, Failed, or Rolled back
Has backupWhether a backup ZIP was captured before the update

Rolling back an update

If an update caused a problem, you can revert to the previous version:
1

Find the history entry

Locate the update you want to undo in the History tab. It must show Has backup to be rollback-eligible.
2

Click Rollback

Click the Rollback (undo) icon on the row. A confirmation dialog appears showing the from/to versions.
3

Confirm

Confirm the rollback. The backup ZIP is used to restore the previous version. The history entry status changes to Rolled back.
Rollback reinstalls the backed-up version of the plugin or theme. If the plugin has run database migrations since the update, rolling back may leave the database schema out of sync with the older code. Test rollbacks on staging before using them in production.

Clearing history

Click Clear History to remove all history entries. This does not delete backup files.

Scheduled updates tab

The Scheduled tab lets you queue an update to run automatically at a specific date and time via WP Cron.

Creating a scheduled update

1

Select item type

Choose Plugin, Theme, or Core from the type dropdown.
2

Select the item

The item selector populates based on the type. For plugins, choose from the list of plugins that have available updates. For themes, choose from themes with updates. For core, the WordPress core entry appears.
3

Set the date and time

Pick the date and time you want the update to run using the datetime input.
4

Schedule

Click Schedule Update. The job is registered as a WP Cron event with the wmp_run_scheduled_update action.

Viewing and cancelling scheduled jobs

Scheduled jobs appear in a table showing:
ColumnDescription
NameItem name
TypePlugin, Theme, or Core
Scheduled forHuman-readable date/time of the planned update
Statuspending or running
Next runNext WP Cron fire time
Click the Cancel (X) button on any row to unschedule the job.
Schedule core WordPress updates for off-peak hours (e.g. 3 AM) to minimise disruption. Make sure WP Cron is firing reliably — check the Cron Manager → Health tab to verify.

Build docs developers (and LLMs) love