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
Upgrading to newest Event Espresso and WP 3.5 | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Upgrading to newest Event Espresso and WP 3.5

Upgrading to newest Event Espresso and WP 3.5

Posted: December 27, 2012 at 2:23 pm

Viewing 3 reply threads


oohtruck

December 27, 2012 at 2:23 pm

what’s the preferred method of upgrading? Should I upgrade to 3.5 first, and then initiate the EE upgrade or vice versa?


Josh

December 27, 2012 at 2:26 pm

Hi there,

Event Espresso 3.1.29.1 will run fine on WP 3.4.2, so I would recommend updating Event Espresso first.


oohtruck

December 27, 2012 at 2:36 pm

I’m running 3.3.2…


Josh

December 27, 2012 at 3:07 pm

Event Espresso 3.1.29 requires WP 3.3 or higher.

If I was going to update a live site that hadn’t been updated in a while, I’d clone the site (database and files) onto another installation and run the updates there first. You will also want to pay attention to the known issues with updating to WP 3.5:
http://wordpress.org/support/topic/troubleshooting-wordpress-35-master-list
Viewing 3 reply threads

The support post ‘Upgrading to newest Event Espresso and WP 3.5’ 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 Josh 12 years, 2 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server