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 Personal + WP 3.6 = what? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Event Espresso Personal + WP 3.6 = what?

Event Espresso Personal + WP 3.6 = what?

Posted: September 9, 2013 at 12:05 pm

Viewing 3 reply threads


Debra McElroy

September 9, 2013 at 12:05 pm

Hi,

I found various threads on the forum, exploring things that have gone wrong when EE is combined with WP 3.6. I have a website on a test server, and the client is wanting to upgrade to WP 3.6 to enable some video posting capabilities.

Here’s my question: Can I expect EE to work flawlessly if we do that?

Here are my current specs:
– EE Personal license, version 3.1.34.1.P
– WP 3.5.2
– test site: http://wp.northridgefriends.org/
– hosting: VPS at Liquid Web
– Risen theme from StevenGliebe

Thanks!

  • This topic was modified 11 years, 4 months ago by Debra McElroy.


Josh

September 9, 2013 at 12:52 pm

I haven’t seen any issues with updating to WP 3.6 when using the current version of Event Espresso. Can you share a link to one of threads where it was discovered that updating to WP 3.6 caused an issue? We ran the alphas, betas, and release candidates on Event Espresso right up until the official release and the only changes that affected Event Espresso were a few deprecated function notices.

That said, we always recommend backing everything up before doing a software update.


Debra McElroy

September 9, 2013 at 1:06 pm

Hmm.. :/ I searched for “WP 3.6” and came up with a lot of threads, glanced over them, read a couple, got nervous, and posted my question. After deeper perusal, this seems to be the only one that is actually about my topic:

http://staging.eventespresso.com/topic/wp-engine-wp-3-6-jquery-issues/

…and I overlooked the fact that it’s about an older version of EE.

So, sorry for “crying wolf!” Thanks for your assurances that this should work, and for the speedy reply.


Josh

September 9, 2013 at 1:22 pm

No worries. In the other thread that had to be an older version of Event Espresso because the .live() method was removed back in Event Espresso 3.1.31 in anticipation of WordPress upgrading to jQuery 1.9. (Which did indeed happen in WP 3.6).
Viewing 3 reply threads

The support post ‘Event Espresso Personal + WP 3.6 = what?’ 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 11 years, 4 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server