Support

January 13, 2021 at 6:51 am

Good morning, Daniela (and a happy new year to you).

In short, you can not switch from EE4 to EE3 without starting fresh. They both use completely different database tables and data structures.

We have a migration path from EE3 to EE4 in that EE4 will pull all of the data it can from the EE3 database tables into EE4 on initial activation but we do not have a migration script from EE4 to EE3 as EE3 is now considered legacy and will eventually be phased out.

I searched for the status of development of the recurring events in EE4 and found that the development is still in progress. The feature was promised for the end of the year 2019 and we are still waiting for this.

Correct, we are currently developing this feature and will be releasing a pre-release version to beta testers soon (not to be used on a live site just yet).

May I ask where you have seen a release date for EE4 Recurring events stating 2019? I can’t find where that has been posted.

To build out recurring events we rebuilt the datetime/ticket editor from the ground for various reasons so although it sounds like a fairly straightforward request the changes required to accommodate those events were significant.

I saw some customers gave up and changed to an other product.

We’ve always been open and honest that EE4 doesn’t officially support recurring events yet and whilst possible to do for basic recurring events it does take a lot more effort to manage.

We can’t release the add-on until it’s ready to do so and as much as we would love to have all the features we have planned available right now, it simply isn’t possible. However, the time and effort put into the changes for recurring events should help speed up various additional features being introduced in the future.

I/We understand the frustration here and we are all working as hard as we can in the background to get this add-on released asap.