WP Staging 2.1.9 – What has been changed and improved?

WP Staging 2.1.9 has been released and it brings you several improvements to ensure better compatibility for websites on hosted accounts like bluehost or godaddy.

If you are on one of these web hosts and you experience a cloning process error like “Can not find ajax url” than this update is for you. WP Staging 2.1.9 also improves the cloning performance and fixes issues where a staging site can not be deleted.

This update also contains several new functions for our new database migration tool which is coming very soon.

See what else we did under the hood:

* New: Allow selection of db tables with wpstg_ prefix in the table selection dialog
* Fix: Deleting process throws timout issues and php notices
* Fix: Link to staging site is undefined when staging name contains space characters
* Fix: If file copy limit is lower than 500, not all files are copied in all cases
* Fix: Increase file copy performance
* Fix: Cloning update function created new staging tables everytime it is run

I hope you like the new release. As usual you find the update in your WordPress admin dashboard under the plugins section:

Author: Rene Hermenau

I'm René Hermenau, founder of WP STAGING. I've been building WordPress infrastructure software since 2013 and writing code on GitHub since 2011. My repos live at github.com/rene-hermenau. WP STAGING started as a small developer project solving the same problem I kept hitting on client work: there was no fast, safe way to clone a WordPress site for staging or migration without breaking serialized data, file paths, or media references. Today we are a team of more than 10 people. The free plugin runs on hundreds of thousands of WordPress installations, and the Pro version powers backup, migration, and staging workflows for agencies, hosting platforms, and ecommerce stores. I'm still hands-on with the codebase and technical architecture. Our releases are built as a team, but many of the core architectural decisions are ones I helped design, test, and evolve over the years: how we handle large database exports, how we keep memory usage flat on multi-GB sites, and how we make migrations atomic against partially written tables. "When you touch code, leave it 10% better than before and write a test." If you're stuck on a WP STAGING question, the docs are at wp-staging.com/docs. If you hit a bug, file it on GitHub at github.com/wp-staging. Our team reads everything that lands there.