How does WP Toolkit staging work? The Cpanel version doesn't have a how-to like the Plesk version

[binarybcc]

The creation of a staging site using clone is easy enough, but there is no obvious way to make the staging work the new main site in WP Toolkit. Literally, I can make a staging site and make all the changes I want, etc, but there is no way of moving that back to the main site in the Cpanel version of WPTk. The Plesk version has a button to merge the staging back into the old site. A button. And a simple how-to page. I'm paying for WPToolkit specifically FOR the ease of Staging/merging.

Now, I may have missed the button in the WHM interface, but I don't think so. I'd love to be made to look like an idiot at this point. Thanks for you help.

 

[cPRex]

Hey there! You should find the "copy data" function in the WPT interface. Once you click that, you'll be presented with various options for where you are copying the data to. Can you check that and see if that is what you're looking for?

 

[binarybcc]

Thanks but.... but this isn't 'staging.' A real staging site that one pays for is one where the user clicks a button and the staging site becomes the production site. This is not staging. I'm paying for staging. If I have to manually merge the staging work into the production site by hopefully picking the right files, data, and content -- I don't need the WP Toolkit. WHM's WPToolkit version for plesk panel literally has a button that merges the the new site into the production site, according to the online manual for it. If I redesign a site, the content of the databases is appended with settings for the new design -- Plus, what happens to the material I have added to the old site in the interim (daily updates, etc). Staging merges that.

Whiney Whine whine, I know. But I'm PAYING for this.

Again, maybe I'm missing something obvious, and I apologize if so, but I'd hope someone could show me....

Here's the WPToolkit on Plesk lead in:

"
Video 2: Applying changes to the production website
Video: 1:15 minutes

Usually, you would put the production website into “maintenance mode” so that the synchronization procedure is not interrupted by a site visitor. Then, copy new and changed files from the staging to the production website. And finally, copy new tables from the staging database to the production database.
This might seem even more complex than creating the staging environment, right? But not with the WordPress Toolkit, because you can do the entire procedure with just a single click.
"

It's the same Toolkit.... but it's not?

 

[cPRex]

The Copy Data feature should do all the things you mention - it just gives you more control over what you want to change, so I suppose it's not totally "one-click"

Can you try that feature in the interface and see if it performs how you expect?