|
kdaily
|
January 23, 2018 at 7:08 am
So a few weeks ago I messaged WPE about their process to push from staging to live. My feeling was that it would remove any registrations that occured after the push from live to staging. I was correct. WPE advised I find out from you which tables I need to exclude and told me where to do that. Sounds easy enough? Nope. You all told me that wasn’t possible and suggested I use mergebot. So, I went and got approval to spend another $250 on mergebot at your suggestion. I’ve got mergebot purchased and configured, only to find out that it only pushes database changes, not updated files. Mergebot seems suprised that I can only use my license for updating on one server and that the staging server counted against the license.
I need a way that I can test changes in the staging environment and not lose the registrations that occur during the testing process. Putting EE into maintenance mode is not an acceptable answer because I need various approvals before I can make some changes go live and that is not instantaneous.
|
|
Josh
|
January 23, 2018 at 7:21 am
Mergebot seems suprised that I can only use my license for updating on one server and that the staging server counted against the license.
That’s actually not correct, you can keep Event Espresso up to date on both sites with one key. You can put the key on one site (doesn’t matter which site) then you push the files to the other sites. Event Espresso 4 function the same with or without the key.
So when you need to push database changes from staging to production, you use Mergebot. When you need to push file changes from staging to live, you can use sFTP.
|
|
kdaily
|
January 23, 2018 at 7:34 am
But how do I know which files to move over via sftp? I’m assuming I have to manually move them.
|
|
Josh
|
January 23, 2018 at 7:46 am
You don’t need to know which files to move over. You upload the new version after testing.
|
|
kdaily
|
January 23, 2018 at 7:49 am
Upload how?
|
|
Josh
|
January 23, 2018 at 8:09 am
Option one: sFTP into the site and upload the new version folder.
Option two: go to the WP Plugins page and upload the zip file of the new version.
With either option, your account page will have the current version.
|
|
kdaily
|
January 23, 2018 at 8:40 am
will that overwrite any custom plugins or configurations I’ve made?
|
|
Josh
|
January 23, 2018 at 8:58 am
With regards to custom plugins, Aare you making changes to Event Espresso 4 core? When you update the plugin, you should only upload a replacement of the plugin folder. If you’re making edits directly to Event Espresso’s plugin files, then yes, you’ll lose your code changes no matter which way you update.
If your custom plugins are within their own plugin folders outside of the Event Espresso folder, then no, updating the Event Espresso plugin will not overwrite your custom plugins.
Updating will not overwrite configurations/settings stored in the database.
|
|
kdaily
|
January 23, 2018 at 9:04 am
Ok. I just want to verify I understand what to do. Install the updates on staging and test, configure, whatever. Push the db changes with Mergebot to the live environment and manually upload the plugin files from the EE website via SFTP. All of our changes are to php files within the themes dir so they will remain unchanged. Sorry for being a pain… I’m not a web developer and this kind of got thrown into my responsibility.
|
|
Josh
|
January 31, 2018 at 12:14 pm
If all you’re doing is testing updates on staging before running the updates on live, you don’t need to merge data. You can do the tests on staging first (and if need be pull example data from live to staging). Then after everything looks good on staging, do the updates on the live site.
|
