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
Event Espresso Upgrade 4.0 | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Event Espresso Upgrade 4.0

Event Espresso Upgrade 4.0

Posted: September 15, 2013 at 7:57 pm

Viewing 1 reply thread


James Lam

September 15, 2013 at 7:57 pm

Hi guys.

At the moment we’re running EE 3.1.35. We’re considering giving EE 4.0 (or 4.1?) a try. Can you shed some light on what to expect for the following?

1) We have a number of registrations and events on site already. Are these going to port over or will we need to export a database to import it when 4.0 is up?

2) I note that we are running MER. I also understand the price modifier will not work with MER. However, can we use price modifier on standalone items or not?

3) Are the plugins working for 4.1 at the moment or is it still 4.0?

Thanks so much.


Dean

  • Support Staff

    •

September 16, 2013 at 1:41 am

Hi James,

We are hoping to have Beta out in the next month or so.

1) There will not initially be a way to port over 3.1.X data to 4.X

2) I assume you mean using Price Modifier with 4.x? There will be no add on plugin functionality initially.

3) There will be no add on plugin functionality initially.
Viewing 1 reply thread

The support post ‘Event Espresso Upgrade 4.0’ 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.

The original Forum description...

Status: closed

Updated by Dean 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server