wp-staging
Last commit date
Backend
1 month ago
Backup
1 month ago
Basic
3 months ago
Component
1 month ago
Core
1 month ago
Framework
1 month ago
Frontend
5 months ago
Notifications
8 months ago
Staging
1 month ago
assets
1 month ago
languages
1 month ago
resources
1 year ago
vendor_wpstg
1 month ago
views
1 month ago
CONTRIBUTING.md
1 year ago
Deactivate.php
8 months ago
README.md
3 months ago
SECURITY.md
2 years ago
autoloader.php
1 month ago
bootstrap.php
1 month ago
constantsFree.php
1 month ago
freeBootstrap.php
1 month ago
install.php
1 year ago
opcacheBootstrap.php
1 month ago
readme.txt
1 month ago
runtimeRequirements.php
3 months ago
uninstall.php
2 months ago
wp-staging-error-handler.php
6 months ago
wp-staging.php
1 month ago
readme.txt
320 lines
| 1 | === WP STAGING - WordPress Backup, Restore & Migration === |
| 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, restore, migration, staging, wordpress backup |
| 8 | Requires at least: 3.6 |
| 9 | Tested up to: 7.0 |
| 10 | Stable tag: 4.8.0 |
| 11 | Requires PHP: 7.0 |
| 12 | |
| 13 | Backup, restore, staging, and migration for WordPress. Create full-site backups and test updates safely. 100% Unit Tested. |
| 14 | |
| 15 | == Description == |
| 16 | |
| 17 | <h3>Backup, Restore, Staging, Cloning & Migration for WordPress</h3> |
| 18 | |
| 19 | WP STAGING is an all-in-one backup & restore, duplicator, staging, and migration plugin for WordPress, built for professional workflows with 100% unit-tested code coverage, thousands of automated tests, and extensive end-to-end testing across supported PHP versions. |
| 20 | |
| 21 | Create a full backup or an exact clone of your website in minutes. Use it to test plugin and theme updates safely, restore your site when needed, migrate WordPress to another server, or build a staging copy before making changes. |
| 22 | |
| 23 | WP STAGING is developed in Germany and designed for agencies, developers, and businesses that need reliable WordPress backup, staging, restore, and migration workflows. |
| 24 | |
| 25 | [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. |
| 26 | |
| 27 | 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. |
| 28 | |
| 29 | WP STAGING automatically performs search and replace for links and paths during cloning, backup, restore, and migration workflows. |
| 30 | |
| 31 | **This staging and backup plugin can clone your website quickly and efficiently, even if it is running on a weak shared hosting server.** |
| 32 | |
| 33 | [vimeo https://vimeo.com/999447985] |
| 34 | |
| 35 | == Frequently Asked Questions == |
| 36 | |
| 37 | = Why should I use a staging site and backup workflow? = |
| 38 | |
| 39 | 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. |
| 40 | |
| 41 | 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. |
| 42 | |
| 43 | 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. |
| 44 | |
| 45 | = Is WP STAGING a backup plugin? = |
| 46 | |
| 47 | Yes. WP STAGING started as a staging plugin and evolved into a full backup, restore, staging, and migration solution for WordPress. |
| 48 | |
| 49 | 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. |
| 50 | |
| 51 | = How is WP STAGING different from other backup plugins? = |
| 52 | |
| 53 | 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. |
| 54 | |
| 55 | 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. |
| 56 | |
| 57 | 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. |
| 58 | |
| 59 | [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. |
| 60 | |
| 61 | = How do I back up and restore a WordPress site? = |
| 62 | |
| 63 | 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. |
| 64 | |
| 65 | WP STAGING is designed to make backup and restore simple, even on shared hosting and large WordPress installations. |
| 66 | |
| 67 | = What is Remote Sync in WP STAGING Pro? = |
| 68 | |
| 69 | 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. |
| 70 | |
| 71 | This is especially useful for agencies, developers, and site owners who want a faster and more reliable workflow for moving content between WordPress installs. |
| 72 | |
| 73 | Learn more: |
| 74 | [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") |
| 75 | |
| 76 | = How can I turn a backup into a local Docker development site? = |
| 77 | |
| 78 | [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. |
| 79 | |
| 80 | 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. |
| 81 | |
| 82 | Learn more: |
| 83 | [WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Upgrade Now") |
| 84 | |
| 85 | = How do I migrate WordPress to another host or server? = |
| 86 | |
| 87 | [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") includes migration workflows that help you move a WordPress website to another host, domain, or server. |
| 88 | |
| 89 | If you want a guided step-by-step walkthrough, see: |
| 90 | [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") |
| 91 | |
| 92 | = Why do I need a backup plugin at all? = |
| 93 | |
| 94 | 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. |
| 95 | |
| 96 | 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. |
| 97 | |
| 98 | If your website generates leads, sales, traffic, or customer trust, regular backups are not optional. A reliable backup and restore workflow can save hours of downtime and expensive recovery work. |
| 99 | |
| 100 | = Can I activate permalinks on the staging site? = |
| 101 | |
| 102 | Permalinks are disabled on the staging site after the first cloning process. |
| 103 | |
| 104 | Read this guide to activate permalinks on your staging site: |
| 105 | [Activate Permalinks on the Staging Site](https://wp-staging.com/docs/activate-permalinks-staging-site/ "Activate Permalinks on the Staging Site") |
| 106 | |
| 107 | = I cannot log in to the staging or backup site = |
| 108 | |
| 109 | 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. |
| 110 | |
| 111 | If you still cannot log in, go to WP STAGING > Settings and disable WP STAGING extra authentication. Your admin dashboard will still remain protected. |
| 112 | |
| 113 | = Can I just use my local WordPress development system for testing and backup? = |
| 114 | |
| 115 | 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. |
| 116 | |
| 117 | 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. |
| 118 | |
| 119 | [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. |
| 120 | |
| 121 | = Is WP STAGING available in multiple languages? = |
| 122 | |
| 123 | Yes. WP STAGING is available in multiple languages, and several translations are already complete or nearly complete. |
| 124 | |
| 125 | You can view translated plugin pages here: |
| 126 | |
| 127 | [English](https://wordpress.org/plugins/wp-staging/ "WP STAGING on WordPress.org") |
| 128 | [French](https://fr.wordpress.org/plugins/wp-staging/ "WP STAGING en Français") |
| 129 | [German](https://de.wordpress.org/plugins/wp-staging/ "WP STAGING auf Deutsch") |
| 130 | [Spanish](https://es.wordpress.org/plugins/wp-staging/ "WP STAGING en Español") |
| 131 | [Croatian](https://hr.wordpress.org/plugins/wp-staging/ "WP STAGING na hrvatskom") |
| 132 | [Dutch](https://nl.wordpress.org/plugins/wp-staging/ "WP STAGING in het Nederlands") |
| 133 | [Finnish](https://fi.wordpress.org/plugins/wp-staging/ "WP STAGING suomeksi") |
| 134 | [Greek](https://el.wordpress.org/plugins/wp-staging/ "WP STAGING στα Ελληνικά") |
| 135 | [Hungarian](https://hu.wordpress.org/plugins/wp-staging/ "WP STAGING magyarul") |
| 136 | [Indonesian](https://id.wordpress.org/plugins/wp-staging/ "WP STAGING dalam Bahasa Indonesia") |
| 137 | [Italian](https://it.wordpress.org/plugins/wp-staging/ "WP STAGING in Italiano") |
| 138 | [Persian](https://fa.wordpress.org/plugins/wp-staging/ "WP STAGING به فارسی") |
| 139 | [Polish](https://pl.wordpress.org/plugins/wp-staging/ "WP STAGING po polsku") |
| 140 | [Portuguese (Brazil)](https://br.wordpress.org/plugins/wp-staging/ "WP STAGING em Português do Brasil") |
| 141 | [Russian](https://ru.wordpress.org/plugins/wp-staging/ "WP STAGING по-русски") |
| 142 | [Turkish](https://tr.wordpress.org/plugins/wp-staging/ "WP STAGING Türkçe") |
| 143 | [Vietnamese](https://vi.wordpress.org/plugins/wp-staging/ "WP STAGING bằng Tiếng Việt") |
| 144 | |
| 145 | If you want to help improve translations, please get in touch with us through the support forum. |
| 146 | |
| 147 | = Can I give feedback for WP STAGING? = |
| 148 | |
| 149 | Yes. If something does not work as expected, please open a support request and describe the issue in as much detail as possible. |
| 150 | |
| 151 | We continuously improve WP STAGING based on user feedback, real-world hosting environments, and developer use cases. |
| 152 | |
| 153 | Open support: |
| 154 | [WP STAGING Support Forum](https://wordpress.org/support/plugin/wp-staging/ "WP STAGING Support Forum") |
| 155 | |
| 156 | == WP STAGING FREE - BACKUP & STAGING FEATURES == |
| 157 | |
| 158 | * Clone the entire production site into a subdirectory like example.com/staging-site. |
| 159 | * High-performance backup and cloning, even for websites with very large databases. |
| 160 | * Backup scheduling with automatic daily backups. |
| 161 | * Easy to use: create a clone or backup in one click. |
| 162 | * Efficient background processing without slowing down your website. |
| 163 | * No Software as a Service and no external account required. |
| 164 | * All your data stays on your server. Your data belongs to you only. |
| 165 | * No server timeouts on huge websites or weak servers. |
| 166 | * Fast backup, clone, and restore workflows depending on site size and server resources. |
| 167 | * Use the clone as part of your backup and update strategy. |
| 168 | * Only administrators can access the cloned or backup website. |
| 169 | * SEO-friendly staging sites with login protection and no-index handling. |
| 170 | * The admin bar on the staging / backup website is orange colored and shows when you work on the staging site. |
| 171 | * Extensive logging features. |
| 172 | * Supports Apache, Nginx, Microsoft IIS, and LiteSpeed Server. |
| 173 | * Every release passes extensive automated tests to keep the plugin robust, reliable, and fast. |
| 174 | * Fast and professional support team. |
| 175 | |
| 176 | == WP STAGING | PRO - BACKUP & STAGING FEATURES == |
| 177 | |
| 178 | The features below are available in [WP STAGING | PRO](https://wp-staging.com/backup-pro-features "WP STAGING | PRO Features"). |
| 179 | |
| 180 | * Remote Sync - Pull a WordPress site securely from one server to another. |
| 181 | * WP STAGING CLI - Turn a backup into a local Docker-based development site. |
| 182 | * Migrate and transfer WordPress to another host or domain. |
| 183 | * Push a staging website including plugins, themes, and media files to production with one click. |
| 184 | * Clone a backup or staging site to a separate database. |
| 185 | * Choose a custom directory for a backup or cloned site. |
| 186 | * Select a custom subdomain destination like dev.example.com. |
| 187 | * Define user roles for accessing the clone or backup site. This can be clients or external developers. |
| 188 | * Multisite support for migration, backup, and cloning. |
| 189 | * Schedule recurring backups by time and interval. |
| 190 | * Download and upload backups to another server for migration and transfer. |
| 191 | * Backup retention settings. |
| 192 | * Custom backup names. |
| 193 | * Email notifications if a backup cannot be created. |
| 194 | * Backup for WordPress multisites. |
| 195 | * Backup to Google Drive. |
| 196 | * Backup to Amazon S3. |
| 197 | * Backup to (S)FTP. |
| 198 | * Backup to Dropbox. |
| 199 | * Custom backup folder destinations for cloud storage providers. |
| 200 | * Priority support. |
| 201 | |
| 202 | == DOCUMENTATION == |
| 203 | |
| 204 | <strong>How to Backup and Restore WordPress</strong> |
| 205 | [Backup and Restore WordPress](https://wp-staging.com/docs/how-to-backup-and-restore-your-wordpress-website/ "Backup and Restore WordPress") |
| 206 | |
| 207 | <strong>Backup & Transfer WordPress Site to Another Host</strong> |
| 208 | [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") |
| 209 | |
| 210 | <strong>Remote Sync</strong> |
| 211 | [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") |
| 212 | |
| 213 | <strong>Local Docker Development with WP STAGING CLI</strong> |
| 214 | [WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress") |
| 215 | |
| 216 | <strong>All Backup Guides</strong> |
| 217 | [All Backup Guides](https://wp-staging.com/docs/category/backup-restore/ "All Backup Guides") |
| 218 | |
| 219 | <strong>Working with Staging Sites</strong> |
| 220 | [Working with Staging Sites](https://wp-staging.com/docs/category/working-with-wp-staging/ "Working with Staging Sites") |
| 221 | |
| 222 | <strong>FAQ for Backup & Cloning</strong> |
| 223 | [FAQ for Backup & Cloning](https://wp-staging.com/docs/category/frequently-asked-questions/ "Backup & Cloning FAQ") |
| 224 | |
| 225 | <strong>Troubleshooting Backup & Cloning</strong> |
| 226 | [Troubleshooting Backup & Cloning](https://wp-staging.com/docs/category/troubleshooting/ "Troubleshooting Backup & Cloning") |
| 227 | |
| 228 | == WP STAGING BACKUP & CLONING TECHNICAL REQUIREMENTS & INFORMATION == |
| 229 | |
| 230 | * Works on latest version of WordPress |
| 231 | * Minimum Supported WordPress Version 3.8 |
| 232 | * Cloning and Backup work on all webhosts |
| 233 | * No extra libraries required |
| 234 | * Backup & cloning supports huge websites |
| 235 | * Custom backup format is much faster and smaller than any tar or zip compression |
| 236 | * Backup & cloning works in low memory & shared hosting environments |
| 237 | |
| 238 | == SUPPORT == |
| 239 | |
| 240 | [WP STAGING Backup & Cloning](https://wp-staging.com/backup-wordpress "WP STAGING Backup & Cloning") |
| 241 | |
| 242 | == Installation == |
| 243 | |
| 244 | = Installation via admin plugin search = |
| 245 | |
| 246 | 1. Go to Plugins > Add new. Select "Author" from the dropdown near search input. |
| 247 | 2. Search for "WP STAGING". |
| 248 | 3. Find "WP STAGING - WordPress Backup, Restore & Migration" and click the "Install Now" button. |
| 249 | 4. Activate the plugin. |
| 250 | 5. The plugin should be shown below settings menu. |
| 251 | |
| 252 | = Admin Installer via zip = |
| 253 | |
| 254 | 1. Visit the Add New plugin screen and click the "Upload Plugin" button. |
| 255 | 2. Click the "Browse..." button and select the zip file of our plugin. |
| 256 | 3. Click "Install Now" button. |
| 257 | 4. Once uploading is done, activate WP STAGING - WordPress Backup, Restore & Migration. |
| 258 | 5. The plugin should be shown below the settings menu. |
| 259 | |
| 260 | == Screenshots == |
| 261 | |
| 262 | 1. Create new WordPress staging / backup site (Dark Mode) |
| 263 | 2. Create new WordPress staging / backup site (Lite Mode) |
| 264 | 3. Select name for staging / backup site (Lite Mode) |
| 265 | 4. Create Full Site Backup (Dark Mode) |
| 266 | 5. Create Full Site Backup (Lite Mode) |
| 267 | 6. Cloning / backup processing (Dark Mode) |
| 268 | 7. Backup Complete (Dark Mode) |
| 269 | 8. Login to staging site |
| 270 | 9. Staging demo site |
| 271 | |
| 272 | == Changelog == |
| 273 | |
| 274 | = 4.8.0 = |
| 275 | * New: Add analytic events logging for Backup Explorer. #4954 |
| 276 | * New: Add filter configuration support for the standalone restore tool via JSON config file. #5051 |
| 277 | * New: Add option to create remote sync profiles which allow one click remote sync process. #4668 |
| 278 | * New: Add option to receive remote sync success notifications via emails and slack. #4668 |
| 279 | * Enh: Add Remote Sync promo video composition (EN + DE) under promo-video/. #5088 |
| 280 | * Enh: Add filter for custom search/replace in encoded database values (e.g. base64 JSON). #4931 |
| 281 | * Enh: Added a notification on backup download to verify the downloaded file size. #1786 |
| 282 | * Enh: Redesign remote sync flow to be smoother. #4668 |
| 283 | * Enh: Remove deprecated wpstg.backup.restore.exclude_plugins filter. Use wpstg.backup.restore.exclude_paths instead. #4892 |
| 284 | * Enh: Show "Not enough disk space" error when backup file archiving fails due to a disk-full condition, instead of a generic write-failure message. #3034 |
| 285 | * Fix: Add per-request cron integrity check that self-heals missing, orphaned, or wrong-recurrence WP Staging cron events (backup schedules, daily/weekly maintenance, queue processing) so scheduled backups keep running even when WP-Cron itself is broken. #5090 |
| 286 | * Fix: Cron warning shows only when scheduled backups are actually failing. #5058 |
| 287 | * Fix: Fixed edge cases that could cause some settings or backup information to load incorrectly, and improved validation and error handling in backup and staging workflows. #5070 |
| 288 | * Fix: Improved backup reliability on some hosts by ensuring backup progress continues correctly between requests. #5112 |
| 289 | * Fix: Preserve WP Staging Free plugin during backup restore when using Pro version. #4892 |
| 290 | * Fix: Prevent background backups from processing the database twice. #5009 |
| 291 | * Fix: Prevent fatal error and full-site crash when plugin files are missing or corrupted. #5074 |
| 292 | * Fix: Reject empty token on /wpstg/v1/sse-logs REST route to prevent unauthenticated log-stream connections when no job is active. #5097 |
| 293 | * Fix: SFTP connection test fails when run more than once. (Pro) #5029 |
| 294 | * Fix: Show actual Remote Sync error in UI instead of generic failure message and identify which server caused it. #5011 |
| 295 | * Fix: Skip optimizer copy when the destination (mu-plugins directory) is not writable. #4545 |
| 296 | * Fix: Staging delete modal overflows viewport when staging site has many database tables. #5071 |
| 297 | * Fix: Stored SFTP credentials, including SSH private keys, are now saved securely by default. #5048 |
| 298 | * Fix: Undefined variable notice of jobId from AnalyticsServiceProvider. #1503 |
| 299 | * Dev: Add logic to log generic analytic events. #4954 |
| 300 | * Dev: Add translation-audit helper script to find orphaned msgids and missing translations across .po files. #5106 |
| 301 | * Dev: Bump phpunit/phpunit, symfony/process, phpseclib/phpseclib, eslint, @typescript-eslint, and flatted dependencies. #5017 |
| 302 | * Dev: CI release prepare seeds dist/newsfeed-{en,de}.json from dev/releases-history/<version>/ when present, and skips newsfeed:generate-json regeneration in that case so manual edits to the EN newsfeed and translated DE newsfeed survive across re-runs and reach the deploy artifact. #5138 |
| 303 | * Dev: Decouple general/ Playwright tests from staging GitHub workflows into dedicated basic_general, pro_general, and pro_thirdparty_general workflows. #5125 |
| 304 | * Dev: Fix failing "Pro Integration" test on CI for PHP 8.3+. #5082 |
| 305 | * Dev: Fix syntax error in CI release prepare workflow that caused the post-commit "mark required checks" step to crash. #5137 |
| 306 | * Dev: Keep `fast-tests-passed` / `fast-tests-failed` labels across commits; let next test run swap them. #5087 |
| 307 | * Dev: Refactor Staging Site e2e tests to be more robust and stable. #5077 |
| 308 | * Dev: Remove binary .mo translation files from git to prevent merge conflicts. #5072 |
| 309 | * Dev: Revert PHP 8.6 SplFileObject runtime detection until PHP 8.6 is officially released. #5115 |
| 310 | * Dev: Skip AuthTempCertFileTest file permission check on Windows as it does not support Unix permissions. #5069 |
| 311 | * Dev: Update dependencies related to building assets to reduce time taken to build assets. #4880 |
| 312 | |
| 313 | WP STAGING Backup & Cloning | Full changelog: |
| 314 | [https://wp-staging.com/wp-staging-changelog](https://wp-staging.com/wp-staging-changelog) |
| 315 | |
| 316 | == Upgrade Notice == |
| 317 | |
| 318 | Compatible up to WordPress 7.0. |
| 319 | Many improvements for reliability and bug fixes. Please update to the latest version! |
| 320 |