Skip to content

4.9.2

Choose a tag to compare

View all tags
@rene-hermenau rene-hermenau released this 07 Jul 22:47
4.9.2
68d11c5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

WP Staging Free 4.9.2 / Pro 6.9.2

WordPress compatibility: 7.0

Changes

  • Enh: Add accessible labels to Pro upgrade badges and buttons. #5337
  • Enh: Improve the first-time staging experience by removing the redundant "Create Staging Site" button, sharing a single CTA between the listing and empty state. #5266
  • Enh: Route every in-plugin upgrade link to the wp-staging.com pricing table, localized to the current admin language (de, it, es, fr, pt, pl, ja), with unique UTM tags so each click is identifiable in analytics. #5337
  • Enh: Standardize Pro badge wording across the plugin — small locked controls now read "Pro", section badges "Available in Pro", and the upsell button "Upgrade to Pro". #5337
  • Enh: Suppress the dismissed CLI notice server-side instead of via localStorage, so it no longer briefly flashes before being hidden. #5266
  • Enh: Turn the Pro feature badges in the Create Staging Site modal and other upgrade prompts into links to the pricing table. #5337
  • Fix: 404 error when accessing a staging site created with a name containing spaces or special characters. #5321
  • Fix: A backup no longer fails when it hits a file outside the standard WordPress folders. The file is skipped and noted in the log instead of aborting the whole backup. #5325
  • Fix: Allow staging site names up to 100 characters while keeping the generated directory name capped at 16 characters. #5321
  • Fix: Broken auto login to the staging site when the staging site name contains spaces or special characters. #5321
  • Fix: Fatal error on the staging site caused by an invalid destination path when the site name contains spaces or special characters. #5321
  • Fix: Improve remote backup downloads when the remote file size cannot be detected. (Pro) #5222
  • Fix: Prevent backup restore from writing files outside the restore folder. #5299
  • Fix: Prevent site fatal error when plugin files are partially updated or missing during an upgrade. #5309
  • Fix: Prevent the loading bar from staying visible after a successful backup extraction, and improve the “Show logs” button styling. #5306
  • Fix: Prevent unsafe push when staging and production WordPress versions are incompatible. (Pro) #5286
  • Fix: Remove the security alerts popup from the welcome page. #5336
  • Fix: Sanitize the staging site directory name and URL so spaces and special characters no longer produce a broken path. #5321
  • Fix: Stop remote cloud upload immediately when user cancels instead of continuing in background. (Pro) #3891
  • Fix: Temporarily disable the Next-Gen staging engine to prevent staging-site data corruption (postmeta keys). Users are automatically reverted to the Classic engine and warned when they may have staging sites created with the Next-Gen engine. #5346
  • Fix: Temporary folders left by the restore tool are no longer included in backups when "Backup Other WP Root Folders" is enabled. (Pro) #5158
  • Tweak: Refresh backup content icons and improve their light and dark mode styling. #5315
  • Dev: Avoid lowering PHP memory limit when loading the restore tool as a library. (Pro) #5345
  • Dev: Streamline the release pipeline's test phase to avoid a long-running idle CI job that wasted runner time on every release. #5142

WP STAGING Backup & Cloning | Full changelog:
https://wp-staging.com/wp-staging-changelog

== Upgrade Notice ==

Compatible up to WordPress 7.0.

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

Assets 2
Loading