Support

September 30, 2022 at 5:15 am

Hi there,

No, the announcement does not apply to EE3.

However, it is important to note that many hosts are now dropping support for PHP7 and only supporting PHP8+ so you may need to check with your host in case they are about to drop PHP7 support.

EE3 is considered our legacy product and has been for a while now so it will only receive security updates reported for our code. Rewriting EE3 for properly support PHP8 is not something we have plans for currently.

Have you tested EE3 with PHP8 at all? For me it works as normal, it does throw plenty of warnings/deprecated notices but I’ve not run into a fatal error when using it.

October 3, 2022 at 3:51 am

🙂 I wish!

Just so you know, I started out as a customer using EE3 because the company I was working for wanted to sell tickets as part of a street theatre act… that was over 10 years ago. I customized a lot of it, posted solutions here on the forums for other customers and applied some patches for bug/improvements into core which ultimately got me the job here, the rest is history.

Why am I telling you this? Because even though I didn’t create EE3, I’ve worked on the code a lot (and do actually enjoy working on it) so I know that a rewrite of EE3 would be massive 🙂 Getting rid of the warnings/deprecated notices wouldn’t be all that ‘hard’ (time-consuming though) but getting EE3 up to PHP8 spec would be much more difficult. That and the fact that people still use older version of PHP (5.6 for example) with EE3 means you start battling with legacy PHP when rewriting a codebase.

That’s also one of the reasons we created EE4 frame scratch rather than re-writing EE3, EE4 started out as just a rewrite and we identified limitations with the current database schema, codebase, design patterns etc which eventually would have blocked us (or just taken a lot longer) from moving in the direction we wanted to go with Event Espresso.

Anyway, enough of me rambling 🙂

—

Side note – Be careful relying on BlueHost to maintain PHP7, they are moving to PHP8:

https://www.bluehost.com/help/article/php-version-selection

October 17, 2022 at 8:23 am

What your looking to do above is actually pretty complex. The steps involved aren’t all that hard, but the migration path isn’t as clear cut.

There isn’t a function within Event Espresso that allows you to export from Site A into Site B, regardless of whether or not the sites are running EE3 or EE4. The export function in that video isn’t intended as a way to export all your data into a new site 🙂

However, you can move EE3 data over from one site to another (your can’t with EE4) but it’s done by copying the database tables over rather than any kind of build in export function.

Your developer will need to be comfortable managing the database using something like PHPMyAdmin to do this.

When you go from EE3 to EE4 there is a migration script that allows you to migrate your data over when you first activate EE4 but to do that you need copy the EE3 database tables in the ‘new’ site.

So using PHPMyAdmin they need to export the database tables that have the _events_ prefix (thats EE3), like this:

https://monosnap.com/file/UdGsBobOJesqn78tGzPcw2gzEfruNP

Then import those tables into the new sites database and run a migration script to update any references to the ‘old’ URL in a similar way they would need to do during any site migration.

Then install and activate EE3 on that site, you may need to setup the General Settings page (Event Espresso -> General Settings) again but eventing else should then be copied over.

Where you go here depends on what you are looking to do moving forward, I assume you are switching to EE4 on the dev site?

October 28, 2022 at 8:22 am

Transfer the EE3 tables from Site A to Site B?

Sure, I can help with doing that.