With the latest release of WP Staging Pro, we’ve finally got rid of the need to resave permalinks after pushing a staging site to live.
So whenever you migrate the staging site the permalinks are recreated automatically on your production site.
So, when you successfully push it looks like this now:
Several Improvements
We’ve finished a long list of small issues for a better user experience.
Also, a major rewrite of a large portion of background code has been made for the next release of our site migration feature which will hopefully see the light in 2 weeks.
See Changelog
As a license owner, get the latest update from your WordPress admin dashboard or purchase it from wp-staging.com
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.
View all posts by Rene Hermenau
