The main consideration when using Staging boils down to one simple question: is the live site being edited or updated while the Staging site is in development, or will it be waiting unchanged until you’re ready to push your Staging changes to the live site?
The answer to that question will determine the best use of staging for you, because when you push Staging changes to the live site, you’ll have the option of whether to overwrite the live database with the Staging database, or to leave the live database as-is and instead only push file changes from Staging.
Because those are the two options, here’s a guide to our recommendations for Staging:✓
Ideal uses for Staging:
- Duplicating the live site to make changes and updates
- Making changes and updates to theme files
- Installing and removing plugins
- Adding and removing themes
- Testing updates to themes or plugins
- Activating a new theme
- Adding new media files, images, etc.
- Adding or editing posts, pages, settings, products and other content stored in the site’s database as long as the live site’s content and database are NOT being updated or edited in the meantime
NOT recommended for Staging:
- Importing an external site or database—anything that is not a duplicate of the live site
- Adding or editing posts, pages, settings, products and other content stored in the database in situations where the live site IS changing while Staging is in development (such as an eCommerce store, a frequently updated blog, or a forum)
- Making changes to eCommerce data like products, orders, users, etc. while the live site’s store is still active
- Making database content changes to any site where site users can create content
- Keeping a backup of the live site. (Our automated backups do not include Staging)
- Leaving the Staging site active but not pushing it live for extremely long periods of time (as this increases the likelihood of database conflicts)
- Any situation where a secure HTTPS connection is required. (The staging temp domain cannotbe secured with an SSL certificate at this time)
- Speed tests and other uses which require a connection to the site (since Staging sites are blocked by Privacy Mode)
- Situations where the Staging database would need to be merged with the live site’s database, keeping changes to both, or in which only a partial database merge is desired
If that all seems like a lot, just remember: Staging is designed to create a duplicate of the live site, then allow changes to be pushed back to the live site later. Staging can overwrite the live database or leave it alone and only push files, but it can’t merge changes to both the Staging and the live site’s database. So if you’re changing both at the same time, you risk losing some data.