Cropping and editing a production WordPress online site is like detailing your own personal car while it’s generating down the freeway. An individual might arrive at your own destination on time and even looking good. Then yet again, it could all start horribly wrong—and if a person do it often an adequate amount of, your luck can run out eventually.
If a business depends on its WordPress web page or WooCommerce store, croping and editing the live production assembly is simply not value the risk. WordPress hosting sites, also called emergence sites or testing web sites, are the safe renewable.
In this write-up, we explain what a person need to know with regards to WordPress staging sites, exactly why you should use these people, and how cPanel’s WP Toolkit (WPT) makes that easy to deploy a good staging site and coordinate changes back to the production site.
What Is a Wp Staging Webpage ?
A staging site is a cloned copy of a construction site. It has the same data and documents, but it isn’t available to the public, as well as it’s usually hosted on a different subdomain. Every changes you make to a staging site are usually not transferred to the particular production site unless anyone want them to end up being. Because it’s a clone hosted in the very same environment, it behaves basically like the production web site, making it the ideal testing ground.
In typically the past, creating a staging or development site is complicated and time-consuming. Anyone had to export info from the production data source, create a new data source, import the data, content the files, reconfigure the site, and set up a staging subdomain. Then simply you’d have to change the order of the process to release the changes to formation.
That complexity will be why many WordPress customers don’t use staging websites, instead opting for typically the risky high-wire act connected with editing a busy live site. However, if you host WordPress sites on a server managed by just cPanel & WHM, the exact whole process takes only a few clicks.
Why Do A person Need a Staging Site?
There are lots of situations where it’s your good idea to release a WordPress staging site to test changes before committing to them. Ideally, any change more complicated than publishing a post gets thoroughly tested before it goes live.
Use cases for staging internet sites include:
- Testing new landing pages to ensure every component works as expected before potential clients visit.
- Testing updates for compatibility issues, although WP Toolkit can automate that for you with Smart Update.
- Creating a new theme or editing your current theme.
- Editing the site’s code to add new functionality.
Staging sites are also useful when you want to let developers and designers work on your site but don’t want to give them access to the production installation.
How to Setup a WordPress Staging Site
We’re going to walk you through the process of creating a staging site and deploying changes back to production. We’ll be using the clone and staging features in WordPress Toolkit Deluxe.
Select WordPress Toolkit from cPanel’s main page menu and expand the step-by-step view of the site you want to work with.
Click the Clone tool in the dashboard view. In the Clone interface, you can choose the staging site’s subdomain and path. The subdomain can be a pre-existing domain, or the Toolkit can create a new one. If necessary, you can also change the database name.
That’s it! The Toolkit will now create the staging site and subdomain. You can access the new site in the main WPT interface alongside your other sites.
To make staging sites easier to tell apart from live sites, use WPT’s labels. Click Add Label and choose an appropriate option from the dropdown menu.
After web sites are labeled, you can sort and filter them using the Sort and Filter dropdowns at the top right of the interface.
Commit Staging Site Changes to Production
Once you have developed and tested a new feature or design, it’s time to push the changes to the production site. To do that, we have to copy the staging site’s database and files. This would once have been a complicated and error-prone process, but it can be done safely in less than a minute with WP Toolkit.
Click the Copy Data tool in the staging site’s WPT dashboard.
In the Copy Data interface, select the production site from the Target dropdown menu. You have fine-grained get a grip on over which aspects of the site are transferred. You can copy the files, database, and specific database tables. You can also choose whether to overwrite and delete production files if they were edited or removed on the staging site.
In our example image, we’re copying everything except the database’s post and user tables and their associated metadata tables. That allows us to synchronize the WordPress instances without overwriting or deleting posts and users created after we made the staging site.
Because copying can be a destructive operation, WPT automatically creates a restore point so you can quickly roll back if something goes wrong.
Together, WordPress Toolkit’s clone and copy features provide quick and simple-to-use staging site deployment. You can create a staging site in seconds and push changes to production just as easily. For agencies and other businesses that offer WordPress hosting and management services, the WPT means faster, safer, and more reliable WordPress workflows.
As always, if you have any feedback or comments, please let us know. We are here to help in the best ways we can. You’ll find us on Discord, the cPanel forums, and Reddit. Be sure to also follow us on Facebook, Instagram, and Twitter.
