Release Notes for WP Staging 4.11.2

WP Staging 4.11.2 is out. Focused on stability and user experience.

Highlights

• Staging sites are created with the Next-Gen engine again, now that the table prefix corruption that had it switched off is fixed.
• A badge appears in the admin sidebar when a scheduled backup fails or is missed.

Fixes

• Always store the WP STAGING settings as an array, so a stored object can no longer break saving, restoring or pushing.
• Cancel only the Remote Sync pull the request verified, never a job that replaced it.
• Clean up the temporary files and tables of a cancelled onboarding backup.
• End a background cancellation that cannot be prepared cleanly instead of with a PHP error.
• End a remote storage upload the provider refuses instead of retrying it on every request.
• Generate temporary-login link IDs server-side with a secure random generator and throttle the login-link path, so links can no longer be guessed from a predictable timestamp or brute-forced.
• Preserve WordPress metadata keys when cloning with the Next-Gen engine.
• Reject cloud storage OAuth callbacks that were not started from the plugin.
• Reject nested legacy object payloads during search-replace and stop a rest_route parameter from bypassing the staging site login form.
• Report MySQL as the database engine in usage analytics instead of leaving it undefined.
• Report a pCloud upload that the remote refused as failed instead of finished.
• Require administrator rights to complete Google Drive API authentication, so a low-privileged user can no longer trigger the OAuth token exchange.
• Retry a backup upload the storage provider refused for rate limiting instead of failing it, and stop reporting a throttled Google Drive as a full one.
• Safely handle custom excluded option names during Next-Gen cloning.
• Show the backup creation offer in the staging modals.
• Stop BackgroundLogger showing a false Something went wrong error for background jobs that already finished successfully.
• Stop a superseded push setup response from replacing the open push modal.
• Stop the backup finalize step from writing an unsigned, corrupted backup after an interrupted request.
• Stop the corner update-protection modal from swallowing clicks on the rest of the page.

Full changelog: https://wp-staging.com/wp-staging-changelog/