WP STAGING – Backup Duplicator & Migration

Descripción

WP STAGING for WordPress Cloning & Migration

Este plugin duplicador puede crear una copia exacta de toda tu web para pruebas, copia de seguridad o desarrollo en cuestión de segundos.*
(El tiempo exacto de la copia de seguridad depende del tamaño de tu web)

Crea un clon de tu web en una subcarpeta o subdominio (Pro) de tu instalación principal de WordPress, incluyendo una copia completa de tu base de datos.

Nota: Para enviar y migrar archivos de plugins y temas al sitio de producción, echa un vistazo a la edición Pro en https://wp-staging.com/

Todas las operaciones de copia de archivos y bases de datos que impliquen mucho tiempo se realizan en segundo plano. El plugin incluso realiza automáticamente una búsqueda y reemplazo completo de todos los enlaces y rutas serializados.

Este plugin de pruebas y copia de seguridad puede clonar tu web incluso en los servidores de alojamiento compartido más pequeños.

¡WP STAGING puede ayudarte a proteger tu web de estar rota o no disponible debido a la instalación de actualizaciones de plugins no probados!

Características principales

  • WP STAGING clones the whole production site into a subfolder like example.com/staging-site.
  • Easy to use! Create a clone of your site by clicking one button
  • No Software as a Service – No account needed! All data belong to you only and stay on your server.
  • Sin timeouts en sitios web grandes y/o en hospedajes pequeños
  • Muy rápido: el proceso de migración y clonado tarda solo unos segundos o minutos, dependiendo del tamaño de la web y de la potencia I/O del servidor.
  • Use the clone as part of your backup strategy
  • Only administrators can access the clone website.
  • SEO friendly: The clone website is unavailable to search engines due to a custom login prompt and the meta tag no-index.
  • La barra de administración de la web de pruebas es de color naranja y se muestra claramente cuando se trabaja en el sitio de pruebas.
  • Extensas funcionalidades de registro
  • Supports all popular web servers: Apache, Nginx, and Microsoft IIS
  • [Premium]: Elige una base de datos independiente y selecciona un directorio personalizado en el que clonar
  • [Premium]: Haz que la web clonada esté disponible en un subdominio, como dev.example.com
  • [Premium]: Envía y migra todo el sitio clonado, incluyendo todos los plugins, temas y archivos de medios, a la web de producción.
  • [Premium]: Define los perfiles de usuario que solo tendrán acceso al sitio clonado. Por ejemplo, clientes o desarrolladores externos.
  • [Premium]: Migración y clonación de multisitios de WordPress

Nota: Algunas características son Premium. Esto significa que necesitas WP STAGING | PRO para usar esas características. ¡Obtén WP STAGING | PRO!

Funcionalidades adicionales de WP STAGING PRO Edition

  • Backup entire website, even with millions of database rows extremely fast
  • Migrate and transfer WordPress to another host or domain
  • Clonación y migración de multisitios WordPress
  • Definir una base de datos independiente y un directorio personalizado a clonar
  • Clonar tu web en un subdominio
  • Especifica qué roles de usuario pueden acceder al sitio de prueba
  • Copiar todas las modificaciones del sitio de pruebas en el sitio web de producción

Cambia tu flujo de trabajo de actualización de temas y datos de plugins:

  1. Usa WP STAGING para clonar una web de producción para hacer desarrollo, pruebas o copia de seguridad
  2. Crea una copia de seguridad de tu sitio web
  3. Personaliza el tema, configura, actualiza o instala nuevos plugins
  4. Pruébalo todo en tu sitio de prueba y mantén una copia de seguridad del sitio original
  5. Si todo funciona en el sitio de pruebas, ¡inicia la migración y copia todas las modificaciones a tu sitio de producción!

¿No puedo usar mi sistema de desarrollo de WordPress local como xampp / lampp para pruebas y propósitos de copia de seguridad?

Puedes probar tu web localmente, pero si tu entorno de hardware y software local no es un clon 100 % exacto de tu servidor de producción, NO hay garantía de que cada elemento de tu copia local funcione en tu web de producción exactamente como se espera.
Hay algunas cosas obvias, como las diferencias en la configuración de PHP y el servidor que estás ejecutando, pero incluso configuraciones no tan obvias, como la cantidad de RAM o el rendimiento de la CPU, pueden producir resultados inesperados en tu web de producción.
Hay docenas de posibles causas de error adicionales que no se pueden controlar bien cuando se prueban los cambios en una plataforma local sin crear un sitio de pruebas.

This is where WP STAGING comes into play… Site cloning, backup, and staging site creation simplified and with enterprise code quality on a new level.!

Sitio oficial

https://wp-staging.com

Capturas

  • Paso 1. Creación un nuevo sitio de WordPress de pruebas / copia de seguridad
  • Paso 2. Explorar tu web en busca de archivos y tablas de bases de datos
  • Paso 3. Creación de sitios de prueba de WordPress en curso
  • Finalizar - Accede a su sitio de copia de seguridad / prueba

Instalación

  1. Súbelo e instálalo en el escritorio de WordPress wp-admin > Plugins > Añadir nuevo > Subir plugin
  2. Activa el plugin desde el menú ‘Plugins’ de WordPress.

FAQ

¿Por qué debería tener un sitio de prueba?

Las actualizaciones de plugins y las personalizaciones de temas primero deben probarse en una plataforma de prueba antes de que se hagan en tu web de producción.
Se recomienda tener la plataforma de pruebas en el mismo servidor donde se encuentra la web de producción para usar el mismo entorno de hardware y software para tu web de pruebas y detectar todos los posibles errores durante las pruebas.

Antes de actualizar un plugin o ir a instalar uno nuevo, es muy recomendable echar un vistazo a las modificaciones en un clon de tu sitio web de producción.
Esto garantiza que las modificaciones funcionen en el sitio web de producción sin producir errores inesperados ni que la página deje de cargarse (“error de página en blanco de WordPress”).

La mayoría de los usuarios no prueban la actualización de un plugin antes de instalarla en un entorno de producción porque las soluciones de prueba existentes son demasiado complejas y necesitan mucho tiempo para crear una
copia actualizada de tu web.

Algunos pueden tener miedo de instalar actualizaciones de plugins por seguir la regla «nunca toques un sistema en ejecución» pensando que las actualizaciones no probadas aumentan el riesgo de romper el sitio.
Esta es una de las principales razones por las que las instalaciones de WordPress están obsoletas, sin actualizar e inseguras debido a esta costumbre de no tener al día las mismas.

Es hora de cambiar esto, así que usa «WP STAGING» para clonar, hacer copias de seguridad y migrar webs WordPress

¿Cómo instalar y configurar?

Install WP STAGING backup via the admin dashboard. Go to ‘Plugins’, click ‘Add New’ and search the plugins for ‘WP STAGING’. Install the plugin with ‘Install Now’.
After installation, go to WP STAGING > Staging Sites and create your first staging / backup site

Is this a backup plugin?

Even though you can use WP STAGING for backup purposes, the free version is not a usual backup plugin per the general definition. WP STAGING creates a clone of your entire website which you can immediately use for developing and testing.
You can even use it as some kind of backup in case something happens to your production site but only the WP STAGING | PRO pro version allows you to download the backup to your local computer. There are many other popular backup plugins out there but our goal is to bring the reliability and performance of a backup plugin to a new level. So instead of offering our backup feature free of charge, we think it’s time to provide a full-fledged premium backup solution with enterprise code quality affordable for everyone.

Video: How we run automated tests for WP STAGING

What is the difference between WP STAGING and a regular backup plugin?

Note: WP STAGING | PRO provides more advanced backup functionality which can be compared with the below-mentioned backup plugins. The speed and performance of WP STAGING’s backup feature often exceed even the biggest and well-established backup plugins.

We are now adding more and more advanced backup features to deliver what other existing backup plugins are still missing.

You may have heard about other popular backup plugins like All in one Migration, BackWPUp, BackupWordPress, Simple Backup, WordPress Backup to Dropbox, or similar WordPress backup plugins and now wonder about the difference between WP STAGING and those backup tools.
Other backup plugins usually create a backup of your WordPress filesystem and a database backup which you can use to restore your website in case it became corrupted or you want to go back in time to a previous state.
The backup files are compressed and can not be executed directly. WP STAGING on the other hand creates a full backup of the whole file system and the database in a working state that you can open like your original production website.

Even though WP STAGING comes with some backup capabilities its main purpose is to create a clone of your website which you can work on. It harmonies very well with all the mentioned backup plugins above and we recommend that you use it in conjunction with these backup plugins.

Note, that some free backup plugins are not able to support custom tables. (For instance the free version of Updraft plus backup plugin). In that case, your backup plugin is not able to create a backup of your staging site when it is executed on the production site.
The reason is that the tables created by WP STAGING are custom tables beginning with another table prefix.
To bypass this limitation and to be able to create a backup of your staging site, you can set up your backup plugin on the staging site and create the backup from that location. This works well with every available WordPress backup plugin.

I want to migrate my local website to another host

If you want to migrate your local website to an already existing production site you can use our pro version WP STAGING | PRO or a tool like WP Migrate DB which copies only the database.
WP STAGING is intended for creating a staging site with the latest data from your production site or creating a backup of it.

¿Cuáles son las ventajas en comparación con un plugin como Duplicator?

Nos gusta el plugin Duplicator. Incluso si no es tan rápido como WP STAGING para crear una copia de seguridad, es una gran herramienta para migrar de un sitio de desarrollo a uno de producción o de un sitio de producción a uno de desarrollo y una buena herramienta para crear una copia de seguridad de tu web WordPress.
La desventaja es que, antes de que incluso crees un archivo de exportación o de copia de seguridad con Duplicator, se necesitan muchos ajustes, intervenciones manuales y requisitos antes de que puedas iniciar el proceso de copia de seguridad.
El plugin de copias de seguridad Duplicator también necesita algunas habilidades para poder crear una copia de seguridad y un sitio de desarrollo/pruebas, mientras que WP STAGING no necesita de tu parte nada más que un clic para crear una copia de seguridad o un sitio de pruebas.
Duplicator está mejor colocado para ser una herramienta para la creación por primera vez de tu sitio de producción. Ahí es donde es muy práctico y potente.

Si has creado un sitio de desarrollo en local o en un servicio de alojamiento web y necesitas migrar este sitio la primera vez a tu dominio de producción, ¡no hay nada malo en utilizar
el plugin Duplicator! Si necesitas utilizar tanto los últimos datos de producción como las publicaciones, los plugins actualizados, los datos de tema y los estilos en un entorno de prueba o deseas crear una copia de seguridad rápida antes de probar algo, lo que te recomiendo es ¡utilizar WP STAGING en su lugar!

If speed, performance, and code quality are a matter for you as well, give WP STAGING | PRO a try.

I can not log in to the staging / backup site

If you are using a security plugin like Wordfence, iThemes Security, All In One WP Security & Firewall, or a plugin that hides the WordPress default login URL make sure that you have installed the latest version of WP STAGING to access your cloned backup site.
If you can still not log in to your staging / backup site, you can go to WP STAGING > settings and disable there the WP STAGING extra authentication. Your admin dashboard will still be protected and not accessible to public users.

Can I activate permalinks on the staging site?

Los enlaces permanentes se desactivan en el sitio de prueba / copia de seguridad después de la primera clonación / creación de copia de seguridad
Lee aquí cómo activar enlaces permanentes en el sitio de pruebas.

¿Puedo daros mi opinión?

Este plugin ha sido creado tras miles de horas de trabajo y funciona incluso con el paquete de alojamiento web compartido más pequeño.
También usamos estructuras de código de pruebas de nivel empresarial para asegurarnos de que el plugin se ejecuta con solidez en tu sistema.
Si eres desarrollador, probablemente te gustará escuchar que usamos Codeception y PHPUnit para nuestro software.

Como hay un número infinito de posibles combinaciones de servidores, todavía podría suceder que algo no te funcione bien al 100 %. En ese caso,
por favor, abre una solicitud de soporte y describe tu problema.

Reseñas

30 de julio de 2021
This fab plugin has saved me loads of time - much quicker than backing up before updating plugins. Very useful and works perfectly on most of my sites.
30 de julio de 2021
It was super easy to use. First time I do a staging site and really help me a lot. 🙂
28 de julio de 2021
The plugin does what it's supposed to do, and does so quickly and cleanly. However, I sometimes find that links on the staging site take me to pages on the public-facing site that it was cloned from, which can be confusing and disorienting. It's not a major problem, and I really can't complain since the plugin is free.
Leer todas las 1.821 reseñas

Colaboradores y desarrolladores

«WP STAGING – Backup Duplicator & Migration» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«WP STAGING – Backup Duplicator & Migration» ha sido traducido a 4 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «WP STAGING – Backup Duplicator & Migration» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

2.8.5

  • Enh: Preview of the new backup & migration feature in WP STAGING | PRO
  • Enh: Replace CSS based hover with pure js hoverintent for tooltips #1106
  • Enh: Cleanup logs older than 7 days automatically #1116
  • Enh: Update the version to check in Outdated WP Staging Hooks notice #1118
  • Enh: Schedule the uploads backup to be deleted after one week if that option was selected during push #980
  • Enh: Allow copying of only that symlink whose source is a directory #979
  • Enh: Show notice only to user who can manage_options if wp_options table is missing primary key #1009
  • Enh: Delete Optimizer Plugin on WP Staging plugins deactivate instead of uninstall #1096
  • Fix: Fixed conflict with Rank Math Seo PRO when Rank Math Seo PRO is activated network wide in multisites #1111
  • Fix: Make Scan::hasFreeDiskSpace() return other info even if disk_free_space is unavailable #1093
  • Fix: Replace the deprecated of calling a non-static method in daily version check hooks #1092
  • Fix: Try catch all instance of directory iterators #1101
  • Fix: Handle error properly for Filesystem::delete() method #974
  • Fix: Remove loading wpstg scripts as ESM to allow loading them as asynchronous #1007
  • Fix: Properly handle exception while cleaning themes and plugins bak and tmp directories #1017
  • Fix: Delete the clone even if in any case a corrupted delete job cache file existed for delete job #1033
  • Fix: No cloning/pushing logs were written to file. Now fixed. #1040
  • Fix: Wrap wp_doing_ajax in a adapter and use that adapter to call it to make it usable in WP < 4.7 #1047
  • Fix: Fix typo and wrap up text in i18n for src/Backend/views/clone/ajax/start.php #1051
  • Fix: Fix missing clone options warning during scanning process for old clones for UPDATE and RESET #1058
  • Fix: Make isExcludedDirectories condition works for relative directories path too #1054
  • Fix: Set donation link to redirect to WP Staging pricing page #1080
  • Dev: Add a shortcut to allow to use the DI container as a Service Locator easier under some circumstances #1039
  • Dev: Add trait to allow for easier use of the uopz extension in tests #1053
  • Dev: Replace const related tests logic with UOPZ for better readability and control #1079

2.8.4

  • Feat: Compatible up to WordPress 5.7.2
  • Enh: Preserve directories/tables selection and excludes rules for RESET and UPDATE process #809
  • Enh: If any wpstg process is running allow to stop that process within RESET modal #942
  • Fix: Fix multisite subsite capabilities on the staging site #852
  • Fix: Properly resets the properties between Cloning tasks #896
  • Fix: Avoid PHP warning when building version of missing asset file #929
  • Fix: Make RESET modal show error message within modal on failed response instead of browser logs #942
  • Fix: Replace wpstgGetCloneSettings() in mail-settings.php with CloneOption::get() #956
  • Fix: Little typo changed effect to affect #963
  • Fix: Made node_modules dir to be only excluded from WP Staging’s Plugins #963
  • Fix: Fix UPDATE and RESET for old wpstg clones which are without appended underscore db prefix #958

2.8.3

  • Enh: Add Shutdownable interface to replace usages of __destruct in the code #729
  • Enh: Refactor on how the plugin keeps track of a request running time #766
  • Fix: Replace deprecated jQuery click method #730
  • Fix: Fix overlapping of sweetalert confirmation on push with sidebar #742
  • Fix: Exclude wp staging content folder during staging #741
  • Fix: Add sanitizing for path to fix comparing for Windows paths #751
  • Fix: _cerber_files tables are excluded and could not be copied Fix #770
  • Fix: Replaced jQuery assignment with an IIFE wrapper #761
  • Dev: Update php-scoper and other development dependencies #744
  • Dev: Build javascript when building the distributable version of the plugin #750
  • Dev: Internal helper CLI command to order the changelog notes according to type #749
  • Dev: Refactor Job(s) implementation to use the Resources Trait #765
  • Dev: Add internal documentation to versioning and hotfixes #780

2.8.2

  • Feat: Compatible up to WP 5.7
  • Feat: Check database connection in clone data edit #650
  • Feat: Exclude .wp-staging-cloneable file from cloning and update #718
  • Feat: Show notice if a user is using an outdated version of WP Staging Hooks plugin #716
  • Feat: Add single disabled items notice with better message #717
  • Feat: Add options to enable/disable staging sites cloning from UI #722
  • Enh: Use included directories instead of excluded directories to increase cloning speed #671
  • Enh: Stringify directories array var in $_POST to reduce $_POST size during cloning #671
  • Enh: Replace relative paths exclude to absolute and wildcard paths exclude during cloning #671
  • Enh: Detect snapshot tables using regex #694
  • Enh: Enable disable save button in clone data edit during database connection #700
  • Enh: Improve exclude filters for Push process #720
  • Enh: Move Backend/public/img to assets/img #719
  • Enh: Unify Single and Multisite Classes #713
  • Enh: Keep other staging behavior when the staging site is cloneable #722
  • Enh: Refactor search and replace jobs to use memory and time-consumption aware trait #702
  • Fix: Lost password link generation in staging sites #697
  • Fix: Fix cloning on multisite for PHP 5 #725
  • Fix: Skip symlink scanning during directory scan #736
  • Fix: Replace deprecated jQuery click method #730
  • Fix: Fix overlapping of sweetalert confirmation on push with sidebar #742
  • Fix: Exclude wp staging content folder during staging #741
  • Fix: Add sanitizing for path to fix comparing for Windows paths #751
  • Fix: Uninstall not possible if «delete all settings is activated» #756
  • Dev: Internal refactoring of database backup to avoid long-lived branch #624
  • Dev: Enforced changelog entries in CI #695
  • Dev: Refactored webdriver tests to make them faster #656
  • Dev: Refactor how the automated test workflows are generated. Add new webdriver test before release with default settings #712
  • Dev: Increased default file batch limits for faster development environment and CI #706
  • Dev: Renamed all code and UI references of Snapshot to Backup #715
  • Dev: Add helper to manage clone settings #717
  • Dev: Internal code refactoring, renaming classes for better readability #721
  • Dev: Add infrastructure support for wp-cli and background processing #728
  • Dev: Update php-scoper and other development dependencies #744
  • Dev: Build javascript when building the distributable version of the plugin #750

2.8.1

  • Feat: Show creator user name of staging site
  • Enh: Show notice if sending mails are disabled
  • Enh: Show message and stop execution if php version is lower than 5.5
  • Enh: Abort cloning process if table already exists in external database
  • Fix: Can not update database credentials in staging sites wp-config.php under rare circumstances
  • Fix: During the update process if options table was not selected it didn’t get skipped
  • Fix: Error if WP is lower than 4.6
  • Fix: Can not delete entire staging site on error
  • Fix: Activating pro version does not properly disable free version

2.8.0

  • Fix: Latest supported WP version is not reflected on wordpress.org plugin repo
  • Enh: Show confirmation popup if user tries to send another support request within an hour

2.7.9

  • New: Compatible up to WordPress 5.6
  • Fix: Uninstall function can throw fatal error
  • Fix: Do not write sensitive information into debug.log if debug mode is active
  • Fix: Update notification shown even if there is no more recent version
  • Dev: Memory exhausted during tests
  • Dev: Prefix composer vendor libraries with PHP-Scoper
  • Dev: Add more unit and webdriver tests to improve QA
  • Enh: Change authentication to a combination of nonces and access tokens
  • Enh: Improve tests performance
  • Enh: Add tests for database export and restore

2.7.8

  • New: Add special admin notice if plugin is not tested with latest WordPress version
  • New: Compatible up to WordPress 5.5.2
  • New: Allow deleting of orphaned staging site entries if staging site was deleted manually before

  • Fix: Activation hook is not fired after first time installation and wpstg optimizer and cron tasks are not set up

  • Fix: Staging site does not work if database password contains dollar sign in password
  • Fix: Prevent fatal error when the plugin is activated, but there is no permission to create folder wp-content/uploads/wp-staging or wp-content/uploads/wp-staging/logs.

  • Dev: Add new DI container implementation

  • Dev: Add composer 2

2.7.7

  • Fix: Fatal error on activation in pro version (Syntax error)

2.7.6

  • New: Compatible up to WordPress 5.5.1
  • New: Add WP_ENVIRONMENT_TYPE constant for staging site
  • New: Better and wider test coverage
  • New: Implementing of automated CI tests
  • New: Huge code base refactor for cleaner code
  • New: Updated authentication mechanism for ajax requests
  • New: Show welcome video message
  • New: Show message asking for admin credentials on login form
  • New: Move WP STAGING menu down below the menu Plugins
  • New: Selected tables are highlighted with a blue background color
  • Fix: Show access denied message if a non but existing user tries to access the staging site
  • Fix: Remove wp_logout() in staging site login form to prevent multiple login log entries with plugin WP Activity Log
  • Fix: Wrong german translations
  • Fix: Cloning fails if there is no underscore in table prefix

2.7.5

  • New: Compatible up to WordPress 5.4.2
  • Fix: Remove beta notice
  • Fix: Error if views are cloned
  • Fix: Fatal error if WordPress is older than 4.5
  • Fix: Merge pro/free version
  • Fix: Step switching logic does not work properly
  • Fix: Fix progress bar when certains steps are skipped
  • Fix: Change german translation for REPORT ISSUE

2.7.4

SKIP VERSION

2.7.3

  • New: Compatible up to WordPress 5.4.1
  • New: Allow filtering of staging site title
  • Fix: Since WordPress WP 5.4 cloning fails if WordPress is installed in subfolder
  • Fix: Loading icon not shown when disk space is checked
  • Fix: Can not copy tables if prefix is capitalized & has no underscore

2.7.2

  • Nuevo: Compatible hasta WordPress 5.4
  • Fix: Fatal error on WordPress 4.6 and older

2.7.1

  • HotFix: Prefix hotfix failed

2.7.0

  • HotFix: Fix fatal error in step 6 after updating to WordPress 5.4

2.6.9

  • Fix: Can not login to staging site under certain circumstances
  • Fix: Use user selected language setting instead global site based one
  • Fix: Fatal Error: curl_version() not defined in SystemInfo.php
  • New: Refactored structure for easier maintenance
  • New: Core support for WP Staging snapshots
  • New: Implementing of UnitTests

2.6.8

  • Fix: If server is windows it will result in missing files after cloning and can lead to fatal errors of the staging site

2.6.7

  • Fix: Update function adds duplicate string to internal urls like https://example.com/staging/staging/wp-content/*
  • New: Support for WP 5.3.2

2.6.6

  • Fix: Fatal error: Cannot redeclare wpstgpro_overwrite_nonce() and wpstg_overwrite_nonce() after activating pro version on top of this free one
  • Fix: wpdb->prepare() warning after initial cloning

2.6.5

  • New: Support for WordPress 5.3.1
  • New: Refactoring code base and remove app folder
  • New: Add french language files
  • New: Add WP Staging logo to login form
  • New: Set 24 hours expiration date to process lock
  • New: Add link URL to staging site title
  • Fix: Fatal error: Invalid serialization data for DateTime object #91
  • Fix: Add missing string language location
  • Fix: Function fnmatch() not available in all systems
  • Fix: Warning in staging site after initial cloning in db row rewrite_rules
  • Fix: Wrong staging site is selected when delete function is executed and there are more then 10 staging sites

2.6.4

  • Fix: Broken image folder with duplicate leading slash after cloning

2.6.3

  • New Support for WordPress 5.2.4
  • New: Allow wildcards for excluding files
  • New: Add hook «wpstg_clone_action_staging» to execute code on staging site after cloning
  • Tweak: Improved support for custom uploads folder if user customized UPLOADS constant or upload_path in DB
  • Fix: Better compatibility with Windows IIS server
  • Fix: External links are broken after cloning if ABSPATH is equal to /www/
  • Fix: use an alternative method for file_put_contents as it is not supported on all systems due to file permission issues
  • Fix: Redundant and duplicated update comments in wp-config.php in staging site

2.6.2

  • Fix: Do not show warning «Preparing Data Step3: Failed to update rewrite_rules in wpstg0_options»
  • Fix: Change error «Table wpstgtmp_options does not exist» to warning
  • New: Add arguments for hook wpstg_cloning_complete
  • New: Setup server environment variables per process and not globally (e.g. set_time_limit)
  • New: Add support for custom uploads folder if user customized UPLOADS constant or upload_path in DB

2.6.1

  • New: Improve styling of login form. Thanks to Andy Kennan (Screaming Frog)
  • New: Add ‘password lost’ button to login form
  • New: Change welcome page CTA
  • New: Add feedback option when plugin is disabled
  • Fix: PDO instances can not be serialized or unserialized
  • Fix: Can not update staging site db table if there are constraints in it

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