Managing plugins

The Plugins page of a site shows everything installed there and lets you act on it: install, update, activate, deactivate, roll back or delete, one plugin at a time or many at once.

The plugin list

Each row shows the plugin, its version, whether an update is available, and its status (Active or Inactive). Filter by status, search by name, and use Scan installed to re-read the list from the site if you changed something directly in wp-admin. The “last scanned” stamp shows how fresh the list is.

Installing a plugin

Click Add plugin. You can install from two sources:

• From WordPress.org: search the public directory, pick a plugin and install it, optionally activating it right away. You can even choose a specific version instead of the latest.
• From my repository: your private library of uploaded zips, for premium and custom plugins that are not on WordPress.org. See the repository guide for how to fill it.

Everyday actions

Each plugin’s row menu offers the usual operations: Update, Activate, Deactivate, Delete, and Enable/Disable auto-updates (WordPress’s own auto-update flag). Nothing needs wp-admin; the connector performs the action on the site and the list refreshes itself to show the true state afterwards.

Rolling back to an older version

An update broke something? Rollback version lists the older releases available for that plugin on WordPress.org so you can install a specific one. Combined with backups this makes experimenting with updates low-risk.

Bulk actions

Select several plugins and run one action across all of them, for example update everything that has an update pending. The dashboard reports progress step by step (“3/7”) in the notification toast, and the plugins that succeeded stay changed even if one in the middle fails; the result message tells you exactly which ones need attention.

How actions run

Every action is a background job. You can navigate away or even close the tab; the job keeps running and the bell in the top bar shows its progress and result. Jobs on the same site queue up one after another so they never trample each other, while different sites run in parallel. This is also why a bulk update across 20 sites finishes quickly: each site works independently.