Updating a plugin or theme on a production website can sometimes cause unexpected problems, including broken layouts, PHP errors, or a White Screen of Death (WSOD). Siteligent's Safe Update workflow adds checks and recovery steps around the update so the original version can be restored if the updated version causes the site to fail.
How Siteligent Safe Updates Work
A Safe Update goes through several stages before and after the actual update.
Step 1: Pre-Update Health Check
Before changing any files, Siteligent checks the site's homepage over HTTP.
If the site is already down or returning errors, Siteligent stops the update instead of making changes to a site that is already unhealthy.
This helps distinguish an existing problem from a problem caused by the update.
Step 2: Create a Local Snapshot
For plugin and theme updates, Siteligent first attempts to create a Local Snapshot of the component being updated.
The snapshot is stored directly on the WordPress server and provides a local restore point. Because the files are already on the server, restoring from this snapshot can be considerably faster than downloading a backup from cloud storage.
Step 3: Cloud Backup Fallback
If Siteligent cannot create the local snapshot—for example, because the server has insufficient disk space or the required directory permissions are unavailable, it falls back to a cloud-based backup of the relevant plugins or themes directory.
This gives the update process another recovery path when a local snapshot isn't possible.
Note: WordPress core updates use WordPress's native rollback mechanism rather than this component-level cloud backup process.
Step 4: Capture Before Screenshots
If Visual Regression Testing is enabled for your Siteligent team, Siteligent captures screenshots of the URLs you've designated for testing before the update.
For example, you might monitor your homepage, checkout page, or another important page where a visual change would be significant.
These screenshots provide the baseline for the comparison after the update.
Step 5: Perform the Update
Once the recovery point has been secured, the Siteligent Connector downloads the new plugin or theme package, extracts it, and replaces the existing component files on the WordPress server.
Step 6: Clear Caches
After the update completes, Siteligent automatically clears active caches through its unified cache manager.
This includes supported caching layers and WordPress caching plugins such as WP Rocket, LiteSpeed Cache, and WP Super Cache.
Clearing the cache ensures that visitors aren't continuing to receive pages generated from the previous version.
Step 7: Post-Update Validation and Rollback
After the update, Siteligent checks the website again to make sure it is responding correctly.
The health check expects a successful HTTP 200 response. If Visual Regression Testing is enabled, Siteligent also captures new screenshots and compares them with the pre-update screenshots.
If the site fails the health check, for example, it returns a 500 error or becomes completely blank or the visual regression test detects layout degradation, Siteligent initiates an Auto-Rollback.
How Auto-Rollback Restores the Site
The Siteligent Connector uses its restore handler to copy the original files from the available local snapshot or cloud backup back into the active plugin or theme directory.
This restores the files that were present before the update and allows the site to return to its previous working state.
Updating Premium and Commercial Plugins
Premium plugins work somewhat differently from plugins installed directly from the WordPress.org repository.
Plugins such as Advanced Custom Fields Pro, Elementor Pro, and WP Rocket may require an active license or API credential before their developers' servers will provide the update package.
If the license is expired, invalid, or has reached its allowed number of site activations, the developer's server can reject the update request.
If this happens:
Log in to the WordPress site's dashboard.
Open the affected plugin's settings.
Check the plugin's license status.
Renew or re-authenticate the license if necessary.
Return to Siteligent and run the update again.
Siteligent cannot bypass a plugin developer's licensing requirements.
When Should You Use Safe Updates?
Safe Updates are particularly useful for production sites where an incompatible plugin or theme update could affect visitors, layouts, or important functionality. The workflow is designed to check the site before the update, establish a recovery point, perform the update, clear caches, and validate the site afterward.
If the validation detects a serious failure, the update can be rolled back using the saved files.