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
Important information Re: the recent Jetpack update and Event Espresso | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Important information Re: the recent Jetpack update and Event Espresso

Important information Re: the recent Jetpack update and Event Espresso

Posted: December 29, 2012 at 2:36 pm

Viewing 1 reply thread


Josh

December 29, 2012 at 2:36 pm

There is a conflict between Event Espresso and Jetpack 2.0.4 that will manifest itself if either of the Publicize and Sharing modules are active. When either of these modules are active, opengraph meta tags get added to the head of the document, which are causing problems on the registration pages.

The problems may include a blank confirmation page, an error message on the payment page: “An error occured. The primary attendee could not be found.”, and duplicated attendee entries.

The Publicize and Sharing modules can be deactivated on the main Jetpack settings page by clicking the Learn more button, then clicking the Deactivate button that appears to the right of the Learn more button.

screenshot of disabling the publicize module

If you’d prefer to use either of these modules and you’re comfortable with working with PHP, you can remove the opengraph meta tags from the registration page by adding a function like this to a custom functionality plugin -or- if you have the Custom Files Add-on installed, you can add it to the custom_functions.php file:

function disable_jetpack_ogtags_on_regpage() {
    remove_action( 'wp_head', 'jetpack_og_tags' );
}
global $this_is_a_reg_page;
if ( $this_is_a_reg_page ) {
    add_action( 'template_redirect', 'disable_jetpack_ogtags_on_regpage' );    
}

There is an open ticket in our issue tracker to add a solution to the next version to avoid the conflict with Jetpack. In the meantime, the conflict can be worked around by disabling the Sharing and Publicize modules site wide or on the main registration page only.


Josh

January 30, 2013 at 5:19 pm

Update:

Event Espresso 3.1.30.P fixes the compatibility issues between Jetpack and Event Espresso.

Viewing 1 reply thread

The support post ‘Important information Re: the recent Jetpack update and Event Espresso’ 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