Smart Updates In wp-toolkit¶

Use this page when Smart Updates are available in wp-toolkit. Smart Updates test WordPress, plugin, theme, or language updates on a temporary copy before applying them to the live site.

How Smart Updates Work¶

Smart Updates are designed to reduce update risk:

1. wp-toolkit creates a temporary clone of the site.
2. Updates are applied to the clone.
3. wp-toolkit checks the updated clone for visible differences or errors.
4. The result is shown for review.
5. The update is applied to the live site only after approval or the configured automatic rule.

cPanel notes that Smart Updates clone data can be stored inside the installation path in a hidden directory named like .wp-toolkit_X.

When To Use Smart Updates¶

Use Smart Updates for:

• Plugin or theme updates on important sites.
• WooCommerce, membership, booking, or form-heavy sites.
• Sites with page builders.
• Core updates where compatibility is uncertain.
• Sites where a quick visual comparison is useful.

Smart Updates are not a replacement for backups. They are a preflight test.

Before Enabling Smart Updates¶

Confirm:

• The account has enough disk space for a temporary clone.
• The live site has a recent backup.
• The site is not already broken.
• The site does not rely on a fragile production-only integration that could misbehave on a clone.

Review Smart Update Results¶

When wp-toolkit shows the Smart Update result, look for:

• Broken layouts.
• Missing images.
• Changed checkout, form, or login behavior.
• JavaScript or CSS errors.
• Admin dashboard errors.
• Unexpected content changes.

For small cosmetic differences, the update may still be safe. For functional differences, stop and test on a staging copy before applying the update live.

WP-CLI Equivalent: Manual Smart Update Workflow¶

Smart Updates are a wp-toolkit feature, so there is not a single WP-CLI command that performs the same visual clone-and-compare workflow. The terminal version is to test the same update set on a staging copy, then repeat the approved updates on live.

On the staging copy:

wp core check-update
wp plugin list --update=available
wp theme list --update=available
wp core update
wp plugin update plugin-slug
wp theme update theme-slug

After testing the staging copy, repeat only the approved commands on production. This is slower than Smart Updates, but it keeps each changed component clear.

When Not To Trust The Result Blindly¶

Manual testing is still needed when the site has:

• Payments.
• Membership access.
• Bookings or scheduling.
• Custom API integrations.
• Heavy caching.
• Server-specific code.

After applying updates, test the live site just as you would after a normal update.

Review WordPress updates