"A vulnerability in Elementor was just disclosed. Several of the sites I maintain run Elementor. I need to update only Elementor across those sites today."
If you maintain WordPress sites for multiple clients, this scenario happens several times a month. Core updates and other plugin updates can wait for the regular maintenance run, but a specific plugin needs to land urgently.
The trouble is that mainstream maintenance tools don't really offer a UI for "a targeted update across multiple sites, with safety mechanisms intact." Here's how that design problem can be solved.
The limits of an industry-standard "Update All"
Most WordPress maintenance tools have an "Update All" button on each site's dashboard.
- Press it, and every plugin update fires at once
- If any one of them breaks the site, the industry-standard "Safe Updates" / "Atomic Updates" feature rolls everything back
- There's no granularity for "update just Elementor" or "across only this subset of sites"
The structural reasons the industry converged on this design are covered in three gaps the WordPress maintenance industry still hasn't solved — the Worker-plugin-over-HTTP-API architecture constrains how fine-grained the operations can be.
The practical result: an agency task like "update only Elementor across these sites" tends to fall back to logging into each site one by one and updating manually.
What was needed was two-axis granularity (site × plugin)
WP Maintenance Manager v1.6.2 solves this with two axes of granularity:
- Site axis: see, across every managed site, which plugins are due for update
- Plugin axis: pick the (site × plugin) cells with checkboxes — only those combinations are updated
Instead of an "Update All" button, you get a "update only the combinations you picked" button.
Cross-site dashboard design
Opening "Plugin Updates" from the toolbar triggers an SSH-parallel scan across every managed site, surfacing all plugins that are due for update.
Results are grouped by plugin name:
Elementor — needs update on several sites (4.0.0 → 4.0.8)
☐ siteA.com
☐ siteB.com
☐ siteC.com
Yoast SEO — needs update on several sites (22.0 → 22.1)
☐ ...
At a glance, you can see which plugins are out of date on which sites. Looking at the full list of sites, you can make decisions like "update Elementor everywhere, defer Yoast for another window."
Results are cached in the browser and surface immediately even after restarting the app. The parallel SSH scan completes quickly even with a large fleet, so it's lightweight enough to check casually.
A selective update runs with the same safety mechanisms as regular maintenance
This is the key point. When you press "Update selected plugins," the underlying execution uses exactly the same safety mechanisms as a regular maintenance run:
- Database backup (taken before any update)
- One-plugin-at-a-time updates with HTTP checks + automatic pinpoint rollback if something breaks (implementation deep dive)
- Visual check and summary email
The only difference from a regular maintenance run is that Core / theme / translation updates are skipped. Only the plugin combinations you picked actually run.
The log history and report carry a "selective update" tag, and the names of the targeted plugins are recorded. You can trace back later: "when did we push Elementor across multiple sites last month, and to which sites?" The audit trail is preserved.
Takeaway — granularity changes how operations feel
The simplicity of "Update All" is convenient, but it doesn't fit the realistic need to move only a specific plugin across multiple sites simultaneously.
The combination of cross-site dashboard + selective update + safety mechanisms preserved is what makes "a targeted, safe, multi-site update" actually work. When a single plugin's vulnerability gets disclosed, you can update just the affected sites in one action — safely.
What used to be a binary choice between "update everything" and "do nothing" becomes surgical movement with all the safety nets still on. That shifts where the line falls between emergency response and routine maintenance.
