Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Ee3 or ee4 | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Ee3 or ee4

Ee3 or ee4

Posted: April 8, 2014 at 8:38 pm

Viewing 1 reply thread


dafydd evans

April 8, 2014 at 8:38 pm

Starting company in Asia doing lots of small coffee shop type events , should we buy ee3 or ee4 ?

Can you ‘upgrade’ ee3 to 4 later ?

What’s the downside to buying ee3 ?

Downside to buying ee4 ?


Dean

  • Support Staff

    •

April 9, 2014 at 1:17 am

Hi,

This article is a good grounding on the differences between the two – http://staging.eventespresso.com/2014/02/event-espresso-4-beta-officially-released/

In short, right now if you need addons such as Multiple Event Registration, Ticketing etc, you should stick with EE3.

If your needs are simpler, EE4 would be the way to go.

We have an EE4 demo site available – http://demoee.org – which is free to sign up to.

Can you ‘upgrade’ ee3 to 4 later ?

Yes, there is a migration system in place. So long as you don’t modify the database structure in EE3 it can be migrated over.

What’s the downside to buying ee3 ?

None really, EE3 is fully functional. However, over time EE4 will replace EE3.

Downside to buying ee4 ?

Currently there are no addons and some features missing. We are constantly adding more as time goes on.
Viewing 1 reply thread

The support post ‘Ee3 or ee4’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Status: closed

Updated by Dean 10 years, 9 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server