|
Jean Watson
|
March 24, 2018 at 1:57 pm
I remember doing this migration for another client a couple years about and when I upgraded to EE4 I lost access to all of my old events. Is there any way to prevent that? Appreciate your help, thank you!
|
|
Tony
|
March 26, 2018 at 2:29 am
Hi Jean,
We can’t answer with 100% certainty as it depends if any customizations have been made on the EE3 site but on an EE3 install that has not been heavily customized or had any of the system questions re-purposed for something other than what they are intended to be used for you should not lose access to past events as EE4 will migrate them over.
When you migrate to EE4, all of the EE3 tables remain as they are, so even if EE4 does not show the data, you can switch to EE3 to view old events if needed (worst case scenario).
What I would recommend doing here is creating a local development copy of the current site, specifically for migrating over and see if you run into any problems. You don’t need to add your license key to development copies as it does not effect EE’s functionality other than one click updates.
|
|
Jean Watson
|
March 27, 2018 at 7:01 am
Thanks Tony, will give that a shot.
|
|
Tony
|
March 27, 2018 at 7:17 am
You’re most welcome.
Please do let us know how you get on 🙂
|
|
Jean Watson
|
March 27, 2018 at 2:17 pm
Hi Tony
Ran the install on my staging site and received some errors:
Is there anything I can do in the current install (EE3) to avoid these errors when I migrate to EE4?
Warnings occurred during your last Database Update (Data Migration from Event Espresso 3 to Event Espresso 4.1.0):
**redacted**
-
This reply was modified 6 years ago by
 Josh. Reason: forums replies must not contain personal information
|
|
Jean Watson
|
March 27, 2018 at 2:31 pm
Not sure if I should be posting these here, but here are more errors from v. 4.6
Warnings occurred during your last Database Update (Data Update to Event Espresso 4.6.0):
Could not find payment method with PMD_type = ‘cc’ when migrating payment row *redacted*
-
This reply was modified 6 years ago by Josh.
-
This reply was modified 6 years ago by Josh. Reason: redacted benign error information
|
|
Josh
|
March 27, 2018 at 2:35 pm
Hi there,
Those errors are benign. In a few cases the reason for the error is because an associated item (like a question) was deleted (so an associated answer in the database no longer has a related question).
In the future please do not post the full contents of error messages like these because they include personal information. I’m going to redact the error messages in order to remove all of the personal identifiable information now.
|
|
Jean Watson
|
March 27, 2018 at 2:41 pm
Thank you!! I appreciate that. I posted another one as well…
|
|
Jean Watson
|
March 27, 2018 at 2:50 pm
It looks like the previous links do not work.
For example /event-registration/?ee=138 doesn’t link to the event anymore
Will I have to set up redirects for all of those links?
|
|
Josh
|
March 27, 2018 at 3:35 pm
You could set up redirects or update the link element’s href attribute.
Event Espresso 4 uses a more friendly URL scheme, e.g. if an event name is “Annual Fishing Derby” the url will be /events/annual-fishing-derby.
|
|
Jean Watson
|
March 27, 2018 at 3:56 pm
Oh, ok! How do I update the link element’s href attribute? Do I do that pre-migration?
|
|
Tony
|
March 28, 2018 at 2:27 am
No, because you don’t know the specific event id’s slug at that time (it may be a duplicate of another and have -2 at the end of the slug for example).
I’m assuming these links are hardcoded links someone has added to the pages on the site?
|
|
Jean Watson
|
March 28, 2018 at 3:46 am
Ok, makes senses. And yes these links have been included in external documents so I will simply set the current events up as a redirect. Thanks for your help!
|
