|
J
|
September 21, 2017 at 10:49 pm
Hello
We are seeking to transition from EE3 (Event Espresso – 3.1.32.2.P) to EE4. For various reasons we were going to simply replicate our site, remove EE3 and replace it with EE4 and do any necessary updates. A local developer replicated the site and put it on a subdomain, but now the cart is not working – when you click add to cart, you get this error message: “Your cart is empty or you have refreshed after completing your registration.” This would likely be resolved in moving to EE4, but this will take time – can you help get the cart running in the meantime?
Regards, Joe
|
|
J
|
September 22, 2017 at 1:20 am
Hi – just an update on this. We managed to get the cart working for the relevant events by re-doing the links to the relevant registration pages (these links were working but for some reason the cart would not work until we removed and redid the links). So the problem is resolved, but I would be grateful for any thoughts you may have in moving to EE4 as we have proposed – ie replicating the site, deleting EE3 and replacing it with EE4. Thx Joe
|
|
Tony
|
September 22, 2017 at 2:14 am
Hi Joe,
When migrating to EE4 we highly recommend creating a dev copy of the site and migrating there so that if you run into any issues they can be fixed on the dev site whilst your ‘live’ site continues to function on EE3.
A step missed above is updating EE3 to the latest version before switching to EE4. EE4 expects the latest database schema to be set up within EE3 to allow you to migrate your data, so you’ll need update EE3 to 3.1.37.12.P first, then delete EE3 and active EE4 and run through migrations.
|
|
J
|
September 22, 2017 at 2:45 am
Thanks Tony. BTW, you will probably see I put in a priority support token, which I will not be needing at this stage (may use this during / after the update process if that’s ok).
Regards
Joe
|
|
Tony
|
September 22, 2017 at 2:50 am
Yeah, that’s no problem.
I’ve cancelled the request and for security, we do not keep login details for longer than needed so I’ve also removed those, if/when you need to redeem your support token you’ll need to provide those details again.
|
