|
Troy
|
March 2, 2017 at 10:33 am
Hello, I will be upgrading a customer’s site and their EE3 plugin to EE4. I have researched the standard process for installing activating and then importing EE3 data. HOWEVER, as I have to work on EE4 with existing data (making sure everything looks good and works correctly) prior to launch I am worried about the registrations on the existing site being missed for a week or two while I do that.
SO, I just wondered if anyone else has gone through this type of thing before and can confirm that:
Once the EE3 data is imported and EE4 looks and works correctly, I can “reset” EE4 which will allow me to re-import all of the up to date events and registrations so I can then launch the site and nothing will be missed…?
Is that correct? Anyone done that before and willing to share or confirm?
Your help is appreciated!!
|
|
Josh
|
March 2, 2017 at 1:12 pm
If I understand your question and assume you’re not working with the live data on the staging with EE4, then it sounds like you’re on the right track.
So to be clear, are you working on theme files and getting those things ready to transfer to the live site? If so when you’re ready to upgrade the site you’ll make a backup of the live site, then copy the theme files over to the live site, deactivate EE3, activate EE4 for the first time on the live site, then run the migration there.
|
|
Troy
|
March 3, 2017 at 7:37 am
I think, yes I am meaning importing the live data.
Theoretically if I activate EE4 and import the current data (today for example) on the development site, then make all my [css] changes and preparations, and then I want to reimport all newer data (in 3 weeks for example) from the old live site the day of launch. Will resetting EE4 reset all my changes or just allow a second import?
If that won’t work, what do you suggest I do to make custom changes or test EE4 on the development site?
Thanks again!
That a little clearer?
|
|
Josh
|
March 3, 2017 at 8:11 am
May I ask which method are you using to import the current data? For example, are you using a plugin like WP Migrate DB and migrating the live website’s entire database over to the development site?
|
|
Troy
|
March 3, 2017 at 9:00 am
Based on the documentation ive read on EE4, I would use the built in tool following activation.
|
|
Josh
|
March 3, 2017 at 2:09 pm
Hi Troy,
The built in tool doesn’t import data, it migrates existing data for that site from EE3 and converts it to work with EE4.
|
|
Troy
|
March 6, 2017 at 7:21 am
Let me restate,
1. I would import the most recent data from the existing site to EE3 in the dev site,
2. then install and migrate to ee4 on the dev site
3. make all my changes and customizations to ee4.
4. Then the day before the dev site launch *I’d like to* export all current ee3 data from the existing site again, reimport to ee3 on the dev site and then migrate that data *while keeping my ee4 customizations/changes* to ee4
5. then launch the dev site
That a little clearer? Thanks again!
|
|
Josh
|
March 6, 2017 at 1:05 pm
It doesn’t answer the question about how or which method are you using to import the current data. So based on your last reply, if you’re using a tool like WP Migrate DB, your steps would be:
1. Import the most recent data from the existing site to EE3 in the dev site
using WP Migrate DB correct?,
2. then install and migrate to ee4 on the dev site
3. make all my changes and customizations to ee4.
I hope you mean changes and customizations to your WordPress theme and into a customization plugin. If you make changes and customizations directly to EE4 that may cause some problems.
4. Then the day before the dev site launch *I’d like to* export all current ee3 data from the existing site again, reimport to ee3 on the dev site and then migrate that data *while keeping my ee4 customizations/changes* to ee4
So you’d first need to remove and replace the EE3 data with the current data, and delete all EE4 data. If your customizations and changes are in the theme’s files and within a customization plugin you’ll be fine. If your customizations and changes are in the database or within the plugin, you’ll run into some problems with that.
5. then launch the dev site
I’m not clear on this process. Does that involve moving the data and files over from dev to production? If so, how?
|
|
Troy
|
March 14, 2017 at 9:53 am
Ok so basically I am going to just “go for it” and try to minimize overlap and downtime on the dev site. we will manually enter any registrations that sign up over the next few days.
That said, apparently I have to update ee3 before being able to migrate to ee4??? I just bought the full ee4 suite so its not letting me download or upgrade ee3?!
Please advise what you recommend here. Time is of the essence. Thank you!
|
|
Troy
|
March 14, 2017 at 10:27 am
Sorry, I realized I could be a little more thorough.
1. Thanks for your last response. Based on that, I am going to move forward. And to answer your question, I just exported/imported using phpmyadmin vs the db plugin.
2. I am running ee3 that is just .1 version too old to migrate to ee4 (of course…) and without there being a way to immediately contact your company, I appreciate you letting me know what I need to do to upgrade ee3 first without having to buy a whole new ee3 license.
Thanks for all your help.
|
|
Josh
|
March 14, 2017 at 8:51 pm
You can download the latest version of EE3 from Github:
https://github.com/eventespresso/event-espresso-legacy
|
