> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mainwp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Database Updater

> MainWP Database Updater Extension is designed for updating the databases for WooCommerce, Elementor, and Elementor Pro. With this extension, you can update the databases of these plugins directly from inside the MainWP Dashboard.

## 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

***

> [!NOTE]
>
> **Extension Add-on** - This add-on runs in MainWP Dashboard and supports database updates for WooCommerce, Elementor, and Elementor Pro installed on child sites.

[Database Updater - Video Tutorial](https://www.youtube.com/embed/R93OoLsYJzY)

The Database Updater Extension detects available database updates for WooCommerce, Elementor, and Elementor Pro. This means that you no longer need to access the WordPress admin area of a child site to start these database updates.

## Install the Database Updater Extension

**1. Go to your MainWP Dashboard**

**2. Go to Add-ons > Manage Add-ons**

**3. Click the Install Add-ons button**

**4. Locate the Database Updater extension and select it**

**5. Click the Install Selected Add-ons button**

**6. Activate the add-on after installation**

Once the installation process is complete, click the **Activate Add-ons** button.

## 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

**1. Go to Sites > Updates > Database**

**2. Click Update All for the plugin you want to update**

### Update databases on individual child sites

**1. Go to Sites > Updates > Database**

**2. Expand the plugin row and locate the desired site in the table**

**3. 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:

| Icon | Meaning |
| - | - |
| Yellow clock | The child site started or queued the update. Hover over it to see "Update started; sync the site to verify completion." |
| Red X | The update failed or the extension refused it |

A database update stays listed as pending until the next site sync refreshes its status. A successful request means the update was accepted, not that it finished. After a yellow clock, sync the site to confirm the update finished. If any site shows a yellow clock or a red X during **Update All**, the progress modal stays open so you can review the results.

If the extension refuses the update, a red X replaces the row's buttons. Hover over the red X to see the reason.

When the last request for that update was sent to the child site but never confirmed, the tooltip reads: "This update was sent but never confirmed. Reload the page, then use Clear Stuck Request to try again." If the request might still be running, the tooltip instead tells you how long to wait: "This update was sent but never confirmed. Clear Stuck Request will be available in about \[time]. Reload the page then to try again." Before you clear the request, check the plugin on the child site to confirm its database update did not already run.

### 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.

**1. Go to Sites > Updates > Database**

If you just ran **Update Now**, reload the page. The **Clear Stuck Request** button appears only when the page loads and the wait has passed.

**2. Expand the plugin row and locate the site**

**3. Click the Clear Stuck Request button next to Update Now**

**4. Confirm the prompt**

The extension removes the stuck request, and the button disappears. Click **Update Now** to send the update again.

If the request is still within its wait, the extension keeps it and shows: "This update request may still be running. Try again in about \[time], then reload the page."

> [!NOTE]
>
> **Clear Stuck Request** appears only for requests that are still waiting for confirmation and whose wait has passed. You can't clear a request that the child site accepted or declined. To clear a request, you need the same permissions as **Update Now**: access to the Database Updater extension, the `update_plugins` capability, and access to the site.

The extension never clears stuck requests on its own. It removes records of confirmed requests 30 days after they finish, using a daily scheduled task. When you uninstall the extension, it deletes all of its request records.

***

## 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, the `update_plugins` right, and access to the selected site. See [Database Updater Abilities](https://docs.mainwp.com/api-reference/abilities-api/database-updater.md) for authentication, previews, request examples, and results.

***

## Related Resources

* [Updates Add-ons](https://docs.mainwp.com/add-ons/updates.md) - Browse all update tools
* [Manage Updates](https://docs.mainwp.com/sites/updates/manage-updates.md) - Core update management guide
* [WooCommerce Status Extension](https://docs.mainwp.com/add-ons/administrative/woocommerce-status-extension.md) - WooCommerce integration


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.