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
WP Engine & WP 3.6 jQuery issues | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium WP Engine & WP 3.6 jQuery issues

WP Engine & WP 3.6 jQuery issues

Posted: August 7, 2013 at 2:59 pm

Viewing 1 reply thread


Davin Green

August 7, 2013 at 2:59 pm

We’re running this on WP Engine, and having massive issues with any jQuery on Event Espresso. Since 3.6 uses jQuery 1.10…, Espresso is having issues with any live() function usage. We also have to set concatenation off in WordPress, which causes issues with our other plugins.

We’ve already spent too much time trying to troubleshoot it… do you have a quick solution?


Josh

August 7, 2013 at 3:37 pm

Hi Davin,

It sounds like you’re on an older version of Event Espresso. The live() method has been removed and replaced with the on() method from Event Espresso a few versions back in order to be compatible with the newer version of jQuery that ships with WP.

Updating to the latest version of Event Espresso should help.

BTW, WP 3.6 includes the jQuery migrate plugin, so as long as it’s enqueued there shouldn’t be any problems with using live().

I’ve had similar issues with admin script concatenation on one server that I test on in the WP admin. I think what happens is some servers can only handle x number of scripts being concatenated, and with every major version of WP that gets released a few more get scripts added so that’s when you notice it breaking.

Viewing 1 reply thread

The support post ‘WP Engine & WP 3.6 jQuery issues’ 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.

Event Espresso - Staging Server