What You’ll Learn
- Installing the Database Updater extension
- Detecting database updates for WooCommerce, Elementor, and Elementor Pro
- Updating databases on all sites or individually
- Avoiding the need to access child site wp-admin
Install the Database Updater Extension
Go to your MainWP Dashboard
Go to Add-ons > Manage Add-ons
Click the Install Add-ons button
Locate the Database Updater extension and select it
Click the Install Selected Add-ons button
Activate the add-on after installation
How to Update the Databases
After you’ve installed the extension, a Database Updates tab becomes available. Open it from Sites > Updates > Database. You can also select Add-ons > Database Updater, which routes to the same view.Update databases on all child sites
Go to Sites > Updates > Database
Click Update All for the plugin you want to update
Update databases on individual child sites
Go to Sites > Updates > Database
Expand the plugin row and locate the desired site in the table
Click the Update Now button next to the desired site
Check the update result
After you click Update Now or Update All, check the status shown for each site:Clear a stuck update request
The extension records each database update request it sends to a child site. This record stops the Dashboard from sending the same update twice. If a request times out or hits a connection error, the Dashboard can’t confirm whether the child site ran the update. The request then stays pending, and Update Now returns the message “This update was sent but never confirmed. Reload the page, then use Clear Stuck Request to try again.” A request that timed out on the Dashboard side can still be running on the child site. To avoid sending the same update twice, the extension waits before it lets you clear a request. Clear Stuck Request becomes available only after the request’s timeout has passed, plus a one-minute safety margin. With the default timeout, this wait is about 20 hours from when the request was sent. Until then, the tooltip on Update Now shows the approximate remaining wait. For a request that was sent before you updated to a version with this protection, the wait starts the first time the extension checks that request after the update, for example when you load the Database tab. It lasts at least 20 hours. Before you clear a stuck request, check the plugin on the child site. Confirm that its database update did not already run.Go to Sites > Updates > Database
Expand the plugin row and locate the site
Click the Clear Stuck Request button next to Update Now
Confirm the prompt
update_plugins capability, and access to the site.MainWP Abilities
Database Updater 5.2.0 adds three abilities to read stored database updates for one site, preview a selection, and dispatch a confirmed update. Observations use the last stored sync data and do not apply the Dashboard’s ignored-update settings. Verify a fresh backup before dispatching. Acceptance means MainWP Child started or queued the update; sync later and check the plugin to confirm completion. The abilities share the Dashboard’s request records and stuck-request protection. Every call checks Dashboard Abilities API access, Database Updater access, theupdate_plugins right, and access to the selected site. See Database Updater Abilities for authentication, previews, request examples, and results.
Related Resources
- Updates Add-ons - Browse all update tools
- Manage Updates - Core update management guide
- WooCommerce Status Extension - WooCommerce integration
