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

Support

Home › Forums › Translations › Upgrade compatibility questions

Upgrade compatibility questions

Posted: January 7, 2014 at 7:16 pm

Viewing 1 reply thread


Alan Blair

January 7, 2014 at 7:16 pm

I have just started working with a client who has a WordPress site with Event Espresso Version 3.1.34.1.P . Their current WordPress version on 3.6.

They are saying that some of the functionality in Event Espresso is no longer working correctly and attribute this to the updates.

Before troubleshooting their site I want to update the WordPress Core and all plugins to current versions. If I purchase a license for 3.1.36.1.P are there any upgrade issues from the current version?


Josh

January 7, 2014 at 7:52 pm

Hi Alan,

There are no known upgrade issues with updating from 3.1.34.1 to 3.1.36.1.P.
Viewing 1 reply thread

The support post ‘Upgrade compatibility questions’ 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.

Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.

Status: closed

Updated by Josh 11 years ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server