Quote From : Brijesh March 31, 2021, 12:51 pm Hi,
Below are the answers to your questions :
1. Set this installation as live will detach your staging and live site connection and then that staged site will be an independent site and you will not be able to push the staging site to live. Push to Live will copy the files and database from your staging site to the live site.
Hi, what happens if one have chosen this option by mistake? How can one fix this problem?
I was told that when I was ready to push to live I shouldn't mark the "Push database" since I didn't want to overwrite the current customer database, so I didn't. However, there were a bunch of fields below that referred to the database that I chose not to select being afraid of overwriting something. However, by doing this, the push to live didn't work. So I tried a second time and chose "Set this installation as live" instead, thinking it was the better choice. That's when I noticed it had separated both sites: production and staging.
Now when I try to either backup or create a clone from the staging, I get an error saying that the installation already exists and I should uninstall it first.
How can I solve this situation? I need the staging site to replace production without overwriting the database with members information!
Can you help?
Thank you! 
|
Powered By AEF 1.0.8 © 2007-2008 Electron Inc.
August 21, 2021, 1:39 am | Post: 2
