wp-staging
Last commit date
Backend
5 days ago
Backup
5 days ago
Basic
1 week ago
Component
1 month ago
Core
5 days ago
Framework
5 days ago
Frontend
7 months ago
Notifications
10 months ago
Staging
5 days ago
assets
5 days ago
languages
5 days ago
resources
1 year ago
vendor_wpstg
5 days ago
views
5 days ago
CONTRIBUTING.md
2 years ago
Deactivate.php
10 months ago
README.md
5 months ago
SECURITY.md
2 weeks ago
autoloader.php
3 months ago
bootstrap.php
2 weeks ago
commonBootstrap.php
2 weeks ago
constantsFree.php
5 days ago
freeBootstrap.php
1 month ago
install.php
5 days ago
opcacheBootstrap.php
5 days ago
readme.txt
5 days ago
runtimeRequirements.php
4 months ago
uninstall.php
5 days ago
wp-staging-error-handler.php
8 months ago
wp-staging.php
5 days ago
readme.txt
331 lines
| 1 | === WP STAGING - WordPress Backups, Restore, Migration & Clone === |
| 2 | |
| 3 | Contributors: WP-Staging, WPStagingBackup, ReneHermi, lucatume, lucasbustamante, alaasalama, fayyazfayzi |
| 4 | Donate link: https://wp-staging.com/backup-wordpress |
| 5 | License: GPLv2 or later |
| 6 | License URI: https://www.gnu.org/licenses/gpl-2.0.html |
| 7 | Tags: backup, wordpress backup, restore, move, transfer |
| 8 | Requires at least: 3.6 |
| 9 | Tested up to: 7.0 |
| 10 | Stable tag: 4.10.0 |
| 11 | Requires PHP: 7.0 |
| 12 | |
| 13 | WordPress backup plugin: backups, restore & migration in minutes. Clone or duplicate your site, test updates on a staging copy. 100% unit-tested. |
| 14 | |
| 15 | == Description == |
| 16 | |
| 17 | <h3>WordPress Backup, Restore, Staging, Cloning & Migration — All in One</h3> |
| 18 | |
| 19 | WP STAGING is the all-in-one WordPress backup, restore, staging, cloning, and migration plugin, built for professional workflows with 100% unit-tested code, thousands of automated tests, and extensive end-to-end testing across supported PHP versions. |
| 20 | |
| 21 | Create a full backup or an exact clone or copy of your website in minutes. Use it to duplicate your site, test plugin and theme updates safely, restore your site when needed, move or migrate WordPress to another server, transfer your site to a new host, or build a staging copy before making changes. WP STAGING also works as a WordPress duplicator, so you do not need a separate duplicator plugin to copy your website. |
| 22 | |
| 23 | WP STAGING reliably backs up, clones, and migrates WooCommerce stores too, including orders, products, and customer data. |
| 24 | |
| 25 | WP STAGING is developed in Germany and designed for agencies, developers, and businesses that need reliable WordPress backup, recovery, staging, restore, and migration workflows. |
| 26 | |
| 27 | [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also includes advanced workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another"), which lets you pull a WordPress site securely from one server to another using an API key, and [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a WP STAGING backup into a local Docker-based development site. |
| 28 | |
| 29 | All data stays on your server unless you choose a transfer or remote storage workflow. WP STAGING is designed for speed, reliability, and low-resource environments, including shared hosting. |
| 30 | |
| 31 | WP STAGING automatically performs search and replace for links and paths during cloning, backup, restore, and migration workflows. |
| 32 | |
| 33 | **This staging and backup plugin can clone your website quickly and efficiently, even if it is running on a weak shared hosting server.** |
| 34 | |
| 35 | [vimeo https://vimeo.com/999447985] |
| 36 | |
| 37 | == Frequently Asked Questions == |
| 38 | |
| 39 | = Why should I use a staging site and backup workflow? = |
| 40 | |
| 41 | Plugin updates, theme changes, and custom code should be tested before they reach your live site. A staging workflow lets you clone your production website, test changes safely, and keep a working backup ready in case something goes wrong. Safe updates and update testing on a staging copy protect your live site from broken releases. |
| 42 | |
| 43 | Usually, it is best to run the staging site on an environment as close as possible to the production server. That is the best way to catch compatibility issues before they affect your live site. |
| 44 | |
| 45 | WP STAGING combines backup, restore, staging, and migration in one workflow, so you can protect your live website, reduce downtime risk, and ship changes with more confidence. |
| 46 | |
| 47 | = Is WP STAGING a backup plugin? = |
| 48 | |
| 49 | Yes. WP STAGING started as a staging plugin and grew into a complete WordPress backup plugin, with restore, staging, cloning, and migration in one tool. |
| 50 | |
| 51 | Even the free version lets you create backups and restore them when needed. [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") adds more advanced backup workflows, cloud storage destinations, migration tools, and developer-focused features. |
| 52 | |
| 53 | = How is WP STAGING different from other backup plugins? = |
| 54 | |
| 55 | WP STAGING combines backup, restore, staging, cloning, and migration in one workflow. While many backup plugins focus mainly on archive-based backups or simple migration, WP STAGING also helps you create a working staging copy, test updates safely, and restore your site when needed. |
| 56 | |
| 57 | Some backup plugins focus mainly on creating backup archives, while WP STAGING also creates working staging copies for safer testing and rollback workflows. This is especially useful when you want production-like validation before pushing changes live. |
| 58 | |
| 59 | Some backup plugins may not fully support custom tables in all scenarios. WP STAGING is designed to work reliably with staging workflows and custom table prefixes used by its own cloned environments. |
| 60 | |
| 61 | [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also includes advanced workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another") and [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a backup into a local Docker-based development site. That makes WP STAGING especially attractive for developers, agencies, and site owners who want more than a basic backup plugin. |
| 62 | |
| 63 | = How do I back up and restore a WordPress site? = |
| 64 | |
| 65 | After installing WP STAGING, go to the backup section in the plugin and create a full-site backup. You can then restore that backup if a plugin update, theme change, deployment, or unexpected issue breaks your site. |
| 66 | |
| 67 | WP STAGING is designed to make backup and restore simple, even on shared hosting and large WordPress installations. |
| 68 | |
| 69 | = What is Remote Sync in WP STAGING Pro? = |
| 70 | |
| 71 | Remote Sync is a Pro feature that lets you pull a WordPress site securely from one server to another using an API key. Instead of manually exporting databases and copying files, you connect the two sites and start the sync from inside WP STAGING. |
| 72 | |
| 73 | This is especially useful for agencies, developers, and site owners who want a faster and more reliable workflow for moving content between WordPress installs. |
| 74 | |
| 75 | Learn more: |
| 76 | [Remote Sync: Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another") |
| 77 | |
| 78 | = How can I turn a backup into a local Docker development site? = |
| 79 | |
| 80 | [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") includes access to [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a WP STAGING backup into a local Docker-based WordPress site with one command. |
| 81 | |
| 82 | This is ideal for debugging, QA, development, and reproducing client issues locally. It helps you create repeatable local environments without building custom Docker setups for every project. |
| 83 | |
| 84 | Learn more: |
| 85 | [WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Upgrade Now") |
| 86 | |
| 87 | = How do I move, migrate, or transfer a WordPress site to a new host? = |
| 88 | |
| 89 | [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") includes migration and transfer workflows that help you move a WordPress website to another host, transfer your WordPress site to a new host, change the domain, or move to another server. You can move your website between hosts without manual database exports. |
| 90 | |
| 91 | If you want a guided step-by-step walkthrough, see: |
| 92 | [How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/ "How to Migrate Your WordPress Site to a New Host") |
| 93 | |
| 94 | = How do I duplicate or clone a WordPress site? = |
| 95 | |
| 96 | WP STAGING works as a WordPress duplicator: it can duplicate or clone a WordPress site in a few clicks and create an exact copy of your site for testing, development, or as a safety net. Duplication runs in the background, so you can duplicate even large WordPress sites on shared hosting. If you have used a plugin like Duplicator before, WP STAGING covers the same clone and copy workflows and adds backup, restore, and staging. |
| 97 | |
| 98 | = Is WP STAGING a good Duplicator alternative? = |
| 99 | |
| 100 | Yes. If you are looking for a Duplicator alternative, WP STAGING covers the same use cases: duplicate a WordPress site, create a full-site copy, and move or transfer it to another host. In addition to the duplicator workflow, you get one-click staging sites, scheduled backups, and restore in the same plugin. |
| 101 | |
| 102 | = Why do I need a backup plugin at all? = |
| 103 | |
| 104 | Consistent website backups are the foundation of a robust disaster recovery strategy. They protect your website against failed updates, user mistakes, malware cleanup, hosting issues, hardware failures, software malfunctions, and data loss. |
| 105 | |
| 106 | Backups should include website files, databases, user data, and configuration data. A combination of full backups and incremental backups can improve storage efficiency while keeping restore points current. |
| 107 | |
| 108 | If your website generates leads, sales, traffic, or customer trust, regular backups are not optional. A reliable backup, restore, and recovery workflow lets you roll back your WordPress site and can save hours of downtime and expensive recovery work. |
| 109 | |
| 110 | = Can I activate permalinks on the staging site? = |
| 111 | |
| 112 | Permalinks are disabled on the staging site after the first cloning process. |
| 113 | |
| 114 | Read this guide to activate permalinks on your staging site: |
| 115 | [Activate Permalinks on the Staging Site](https://wp-staging.com/docs/activate-permalinks-staging-site/ "Activate Permalinks on the Staging Site") |
| 116 | |
| 117 | = I cannot log in to the staging or backup site = |
| 118 | |
| 119 | If you use a security plugin such as Wordfence, iThemes Security, All In One WP Security & Firewall, or a plugin that hides the default WordPress login URL, make sure you are running the latest version of WP STAGING. |
| 120 | |
| 121 | If you still cannot log in, go to WP STAGING > Settings and disable WP STAGING extra authentication. Your admin dashboard will still remain protected. |
| 122 | |
| 123 | = Can I just use my local WordPress development system for testing and backup? = |
| 124 | |
| 125 | You can always test your website locally, but if your local hardware and software environment is not an exact clone of your production server, there is no guarantee that every aspect of your local copy will behave the same way. |
| 126 | |
| 127 | Differences in PHP version, server stack, memory, CPU performance, and filesystem behavior can all lead to unexpected results on production. That is why staging on infrastructure close to production remains valuable. |
| 128 | |
| 129 | [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also gives you a more advanced local workflow through [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a backup into a local Docker-based development site. |
| 130 | |
| 131 | = Is WP STAGING available in multiple languages? = |
| 132 | |
| 133 | Yes. WP STAGING is available in multiple languages, and several translations are already complete or nearly complete. |
| 134 | |
| 135 | You can view translated plugin pages here: |
| 136 | |
| 137 | [English](https://wordpress.org/plugins/wp-staging/ "WP STAGING on WordPress.org") |
| 138 | [French](https://fr.wordpress.org/plugins/wp-staging/ "WP STAGING en Français") |
| 139 | [German](https://de.wordpress.org/plugins/wp-staging/ "WP STAGING auf Deutsch") |
| 140 | [Spanish](https://es.wordpress.org/plugins/wp-staging/ "WP STAGING en Español") |
| 141 | [Croatian](https://hr.wordpress.org/plugins/wp-staging/ "WP STAGING na hrvatskom") |
| 142 | [Dutch](https://nl.wordpress.org/plugins/wp-staging/ "WP STAGING in het Nederlands") |
| 143 | [Finnish](https://fi.wordpress.org/plugins/wp-staging/ "WP STAGING suomeksi") |
| 144 | [Greek](https://el.wordpress.org/plugins/wp-staging/ "WP STAGING στα Ελληνικά") |
| 145 | [Hungarian](https://hu.wordpress.org/plugins/wp-staging/ "WP STAGING magyarul") |
| 146 | [Indonesian](https://id.wordpress.org/plugins/wp-staging/ "WP STAGING dalam Bahasa Indonesia") |
| 147 | [Italian](https://it.wordpress.org/plugins/wp-staging/ "WP STAGING in Italiano") |
| 148 | [Persian](https://fa.wordpress.org/plugins/wp-staging/ "WP STAGING به فارسی") |
| 149 | [Polish](https://pl.wordpress.org/plugins/wp-staging/ "WP STAGING po polsku") |
| 150 | [Portuguese (Brazil)](https://br.wordpress.org/plugins/wp-staging/ "WP STAGING em Português do Brasil") |
| 151 | [Russian](https://ru.wordpress.org/plugins/wp-staging/ "WP STAGING по-русски") |
| 152 | [Turkish](https://tr.wordpress.org/plugins/wp-staging/ "WP STAGING Türkçe") |
| 153 | [Vietnamese](https://vi.wordpress.org/plugins/wp-staging/ "WP STAGING bằng Tiếng Việt") |
| 154 | |
| 155 | If you want to help improve translations, please get in touch with us through the support forum. |
| 156 | |
| 157 | = Can I give feedback for WP STAGING? = |
| 158 | |
| 159 | Yes. If something does not work as expected, please open a support request and describe the issue in as much detail as possible. |
| 160 | |
| 161 | We continuously improve WP STAGING based on user feedback, real-world hosting environments, and developer use cases. |
| 162 | |
| 163 | Open support: |
| 164 | [WP STAGING Support Forum](https://wordpress.org/support/plugin/wp-staging/ "WP STAGING Support Forum") |
| 165 | |
| 166 | == WP STAGING FREE - BACKUP & STAGING FEATURES == |
| 167 | |
| 168 | * Clone the entire production site into a subdirectory like example.com/staging-site. |
| 169 | * High-performance backup and cloning, even for websites with very large databases. |
| 170 | * Create full or partial backups — full-site backup, database-only, or files-only backups. |
| 171 | * Scheduled backups with automatic daily backups. |
| 172 | * Easy to use: create a clone or backup in one click. |
| 173 | * Efficient background processing without slowing down your website. |
| 174 | * No Software as a Service and no external account required. |
| 175 | * All your data stays on your server. Your data belongs to you only. |
| 176 | * No server timeouts on huge websites or weak servers. |
| 177 | * Fast backup, clone, and restore workflows depending on site size and server resources. |
| 178 | * Use the clone as part of your backup and update strategy. |
| 179 | * Only administrators can access the cloned or backup website. |
| 180 | * SEO-friendly staging sites with login protection and no-index handling. |
| 181 | * The admin bar on the staging / backup website is orange colored and shows when you work on the staging site. |
| 182 | * Extensive logging features. |
| 183 | * Supports Apache, Nginx, Microsoft IIS, and LiteSpeed Server. |
| 184 | * Every release passes extensive automated tests to keep the plugin robust, reliable, and fast. |
| 185 | * Fast and professional support team. |
| 186 | |
| 187 | == WP STAGING | PRO - BACKUP & STAGING FEATURES == |
| 188 | |
| 189 | The features below are available in [WP STAGING | PRO](https://wp-staging.com/backup-pro-features "WP STAGING | PRO Features"). |
| 190 | |
| 191 | * Remote Sync - Pull a WordPress site securely from one server to another. |
| 192 | * WP STAGING CLI - Turn a backup into a local Docker-based development site. |
| 193 | * Migrate and transfer WordPress to another host or domain. |
| 194 | * Push staging changes to production (staging to live), including plugins, themes, and media files, with one click. |
| 195 | * Clone a backup or staging site to a separate database. |
| 196 | * Choose a custom directory for a backup or cloned site. |
| 197 | * Select a custom subdomain destination like dev.example.com. |
| 198 | * Define user roles for accessing the clone or backup site. This can be clients or external developers. |
| 199 | * Multisite support for migration, backup, and cloning. |
| 200 | * Schedule recurring backups by time and interval. |
| 201 | * Download and upload backups to another server for migration and transfer. |
| 202 | * Backup retention settings. |
| 203 | * Custom backup names. |
| 204 | * Email notifications if a backup cannot be created. |
| 205 | * WordPress multisite backup and restore. |
| 206 | * Cloud backup, offsite backup, and remote backups to external storage providers. |
| 207 | * Backup to Google Drive. |
| 208 | * Backup to Amazon S3. |
| 209 | * Backup to (S)FTP. |
| 210 | * Backup to Dropbox. |
| 211 | * Custom backup folder destinations for cloud storage providers. |
| 212 | * Priority support. |
| 213 | |
| 214 | == DOCUMENTATION == |
| 215 | |
| 216 | <strong>How to Backup and Restore WordPress</strong> |
| 217 | [Backup and Restore WordPress](https://wp-staging.com/docs/how-to-backup-and-restore-your-wordpress-website/ "Backup and Restore WordPress") |
| 218 | |
| 219 | <strong>Backup & Transfer WordPress Site to Another Host</strong> |
| 220 | [How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/ "How to Migrate Your WordPress Site to a New Host") |
| 221 | |
| 222 | <strong>Remote Sync</strong> |
| 223 | [Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another") |
| 224 | |
| 225 | <strong>Local Docker Development with WP STAGING CLI</strong> |
| 226 | [WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress") |
| 227 | |
| 228 | <strong>All Backup Guides</strong> |
| 229 | [All Backup Guides](https://wp-staging.com/docs/category/backup-restore/ "All Backup Guides") |
| 230 | |
| 231 | <strong>Working with Staging Sites</strong> |
| 232 | [Working with Staging Sites](https://wp-staging.com/docs/category/working-with-wp-staging/ "Working with Staging Sites") |
| 233 | |
| 234 | <strong>FAQ for Backup & Cloning</strong> |
| 235 | [FAQ for Backup & Cloning](https://wp-staging.com/docs/category/frequently-asked-questions/ "Backup & Cloning FAQ") |
| 236 | |
| 237 | <strong>Troubleshooting Backup & Cloning</strong> |
| 238 | [Troubleshooting Backup & Cloning](https://wp-staging.com/docs/category/troubleshooting/ "Troubleshooting Backup & Cloning") |
| 239 | |
| 240 | == WP STAGING BACKUP & CLONING TECHNICAL REQUIREMENTS & INFORMATION == |
| 241 | |
| 242 | * Works on latest version of WordPress |
| 243 | * Minimum Supported WordPress Version 3.8 |
| 244 | * Cloning and Backup work on all webhosts |
| 245 | * No extra libraries required |
| 246 | * Backup & cloning supports huge websites |
| 247 | * Custom backup format is much faster and smaller than any tar or zip compression |
| 248 | * Backup & cloning works in low memory & shared hosting environments |
| 249 | |
| 250 | == SUPPORT == |
| 251 | |
| 252 | [WP STAGING Backup & Cloning](https://wp-staging.com/backup-wordpress "WP STAGING Backup & Cloning") |
| 253 | |
| 254 | == Installation == |
| 255 | |
| 256 | = Installation via admin plugin search = |
| 257 | |
| 258 | 1. Go to Plugins > Add new. Select "Author" from the dropdown near search input. |
| 259 | 2. Search for "WP STAGING". Searching for "WPStaging" in one word works as well. |
| 260 | 3. Find "WP STAGING - WordPress Backup, Restore & Migration" and click the "Install Now" button. |
| 261 | 4. Activate the plugin. |
| 262 | 5. The plugin should be shown below settings menu. |
| 263 | |
| 264 | = Admin Installer via zip = |
| 265 | |
| 266 | 1. Visit the Add New plugin screen and click the "Upload Plugin" button. |
| 267 | 2. Click the "Browse..." button and select the zip file of our plugin. |
| 268 | 3. Click "Install Now" button. |
| 269 | 4. Once uploading is done, activate WP STAGING - WordPress Backup, Restore & Migration. |
| 270 | 5. The plugin should be shown below the settings menu. |
| 271 | |
| 272 | == Screenshots == |
| 273 | |
| 274 | 1. Create new WordPress staging / backup site (Dark Mode) |
| 275 | 2. Create new WordPress staging / backup site (Lite Mode) |
| 276 | 3. Select name for staging / backup site (Lite Mode) |
| 277 | 4. Create Full Site Backup (Dark Mode) |
| 278 | 5. Create Full Site Backup (Lite Mode) |
| 279 | 6. Cloning / backup processing (Dark Mode) |
| 280 | 7. Backup Complete (Dark Mode) |
| 281 | 8. Login to staging site |
| 282 | 9. Staging demo site |
| 283 | |
| 284 | == Changelog == |
| 285 | |
| 286 | = 4.10.0 = |
| 287 | * New: Add an A/B experiment framework and run the first experiment on the WP STAGING Free first-run experience. #5522 |
| 288 | * Enh: Add a Remote Sync sidebar menu item for quicker access to syncing from a remote site. #5323 |
| 289 | * Enh: Add a target domain field to the restore tool so a backup can be restored for another domain than the one the tool is opened from. #5453 |
| 290 | * Enh: New installations can start a staging site, a backup or WP STAGING Desktop straight from a first-action selector. #5522 |
| 291 | * Enh: Offer a full backup during staging creation that starts automatically once the staging site is ready. #5522 |
| 292 | * Enh: Offer the same deferred backup during any staging creation, for sites without an established backup workflow. #5522 |
| 293 | * Enh: Rewrite the analytics consent question to name every category WP STAGING actually sends. It no longer asks for permission to collect a name and email address, which it never collected. #5522 |
| 294 | * Enh: Show lifetime licences correctly on the licence page: the plan they bought, "Never" as the expiration date, the premium support period, and no upgrade offer. #5418 |
| 295 | * Fix: Don't show the "Scheduled backups may not run" warning when scheduled backups demonstrably work, e.g. when WP-Cron is executed by an external server cron job. #5403 |
| 296 | * Fix: Keep preserved options and cron jobs intact when a value fails safe unserialization. #5463 |
| 297 | * Fix: Only run the WordPress.com restore task when the site is actually hosted on WordPress.com. #5463 |
| 298 | * Fix: Prevent a successful Remote Sync from ending with a "No response" error when the job log file name is not set. #5483 |
| 299 | * Fix: Prevent duplicate primary keys in database backups when a request is retried, which made the restore fail with MySQL error 1062. #5450 |
| 300 | * Fix: Prevent interrupted database restores from failing when resuming. #5470 |
| 301 | * Fix: Prevent staging, backup, and remote sync from running two workers on the same job at once (which could corrupt the operation) by acquiring the background process lock atomically. #5327 |
| 302 | * Fix: Report the HTTP status and server response when a backup request fails, instead of only guessing at a PHP fatal error. #5503 |
| 303 | * Fix: Require an authenticated request before a cancelled job resets the first-run state. #5522 |
| 304 | * Fix: Resolve Remote Sync Pull failing with a 404 error when downloading data from a source site hosted on IIS. #5488 |
| 305 | * Fix: Resolve the Remote Sync connection key "Copy" button not working in Microsoft Edge. #5488 |
| 306 | * Fix: Restore a backup again after an interrupted restore left the site stuck, where every new attempt stopped at the same table. #5460 |
| 307 | * Fix: Restore the data on servers that do not report their maximum query size, where every row was skipped as too large and the restore finished with empty tables. #5470 |
| 308 | * Fix: Resume a database restore at a byte offset so large restores no longer stall and fail with "Cannot increase execution time". #5486 |
| 309 | * Fix: Show an accurate error when magic login is unavailable on the staging site instead of always suggesting a plugin update. (Pro) #5438 |
| 310 | * Fix: State the deferred backup offer as a choice, so it is no longer mistaken for a job already running. #5522 |
| 311 | * Fix: Stop deleting the oldest backup on the remote storage when its backup listing fails during an upload. (Pro) #5434 |
| 312 | * Fix: Stop logging a false cron update failure when the backup schedule rows are unchanged. #5463 |
| 313 | * Fix: Stop the dark theme from overriding the text colour of every WP STAGING design-system button. #5522 |
| 314 | * Fix: The Delete buttons for the WP Staging logs and PHP debug log on the System Info page now reliably remove the log file and show a clear success or error message. #5375 |
| 315 | * Fix: Warn instead of failing silently when the background session check gets a malformed server response. #4479 |
| 316 | * Dev: Allow gh api POST so review replies need no approval, keep PATCH denied. #5534 |
| 317 | * Dev: Fire wpstg_background_job_failure as a WordPress action as well as an internal hook, so more than one listener can observe a failed background job. #5522 |
| 318 | * Dev: Ignore qemu crash dumps so they stop accumulating in the working tree. #5533 |
| 319 | * Dev: Prevent intermittent failures when building distributable plugins in parallel. #5270 |
| 320 | * Dev: Reduce duplication in BackgroundLogger token verification tests. #5130 |
| 321 | * Dev: Report translation catalogue lines of code in the pull request breakdown. #5531 |
| 322 | * Dev: Speed up "make reset" by preparing WordPress once and setting up all test sites at the same time. #5482 |
| 323 | |
| 324 | WP STAGING Backup & Cloning | Full changelog: |
| 325 | [https://wp-staging.com/wp-staging-changelog](https://wp-staging.com/wp-staging-changelog) |
| 326 | |
| 327 | == Upgrade Notice == |
| 328 | |
| 329 | Compatible up to WordPress 7.0. |
| 330 | Many improvements for reliability and bug fixes. Please update to the latest version! |
| 331 |