Home› Blog›

Updating Event Espresso to Maintain Compatibility with WordPress

Posted by Garth on Thursday, April 16th, 2015

As part of our commitment to our active support license holders, we look into the future and try to foresee any problems you may have with updating Event Espresso and WordPress. Our foresight has been clear and fruitful, and with recent updates to Event Espresso, we’re ready for WordPress 4.2 (coming soon).

To avoid interruption, update Event Espresso BEFORE you update WordPress to version 4.2 (coming soon). Compatibility updates are available from your account (and have been for a while).

Changes to WordPress core

I wonder if Heraclitus was talking about open-source software when he said:

The Only Thing That Is Constant Is Change – Heraclitus

WordPress is constantly changing; new features are added, new methods are introduced, and programmers make mistakes. But, we are constantly monitoring the WordPress codebase to ensure that Event Espresso is as compatible as possible.

Here are a few examples:

Five months ago we noticed that our automated tests were failing because of changes to WordPress 4.1 (which was not yet released). We reported these findings and helped to delay (revert) these changes until they could be improved upon for a future release (now coming in WordPress 4.2).

Two-and-a-half months ago, changes to WordPress 4.2 (not yet released) cause the WYSIWYG to be removed from the: event editor, venue editor, and the attendee (contact) editor. Fortunately the fix is fairly easy. We released this fix in 4.6.16.p (almost a month ago).

About a week ago, we noticed css changes in WordPress caused the Event Espresso admin sidebar to disappear. Since then we have made the necessary changes, tested and released an update in 4.6.20.p (today).

Problems solved.

We are always looking ahead, anticipating and adapting to change. We hope our proactive approach helps you be able to focus more on your events than on your website.

It is important to keep your support license active so you can receive critical updates and maintain compatibility with the ever-changing WordPress.
To avoid interruption, update Event Espresso BEFORE you update WordPress to version 4.2 (coming soon). Compatibility updates are available from your account (and have been for a while).

Questions?

If you have any questions about this announcement, or buying a support license to access the updated files, please contact us.

Related Articles

Filed under Product & News

7 thoughts on “Updating Event Espresso to Maintain Compatibility with WordPress”

    • We have a test site running Event Espresso 3.1.37.p that had the WordPress 4.2 betas and is now on the 4.2 release candidate and everything we’ve tested has passed. Older versions prior to 3.1.37.p haven’t been tested.

  3. We have discovered more issues caused by WordPress’ database changes. If you are experiencing any of these problems, please try updating Event Espresso first:

    • No event in your queue
    • Price not sticking when saving ticket in the editor
    • Other weird things where a ticket appears to have the same price or price modifier as another ticket.

    • There are no known issues for messaging.

      Sometimes, when using an off-site gateway like paypal standard the IPN notification is delayed because their system is slow. But we have put extensive work into triggering the notifications and trying to account for slow services like PayPal.

      There was an issue reported of a fringe case where some registration information was not included in the email, but that issue was resolved in 4.6.25.

      If you experience issues with the messages system and WordPress 4.2, please create a forum thread so we can address it directly.

Share a Reply or Comment

Your email address will not be published. Required fields are marked *

Need help with Event Espresso? Create a support post in our support forums

Do NOT follow this link or you will be banned from the site!
[gravityform id=116 title=false description=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_116' ><form method='post' enctype='multipart/form-data' id='gform_116' action='/2015/04/updating-event-espresso-compatibility-wordpress/'> <div class='gform_body'><ul id='gform_fields_116' class='gform_fields top_label form_sublabel_below description_below'><li id='field_116_5' class='gfield gfield_contains_required field_sublabel_hidden_label field_description_below gfield_visibility_visible' ><label class='gfield_label gfield_label_before_complex' >What is your first name?<span class='gfield_required'>*</span></label><div class='ginput_complex ginput_container no_prefix has_first_name no_middle_name no_last_name no_suffix gf_name_has_1 ginput_container_name' id='input_116_5'> <span id='input_116_5_3_container' class='name_first' > <input type='text' name='input_5.3' id='input_116_5_3' value='' aria-label='First name' aria-required="true" aria-invalid="false" placeholder='First name'/> <label for='input_116_5_3' class='hidden_sub_label screen-reader-text'>First name</label> </span> </div></li><li id='field_116_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_1' >What is your email address so we can follow up with you?<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_116_1' type='text' value='' class='medium' placeholder='hello@example.com' aria-required="true" aria-invalid="false" /></div></li><li id='field_116_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_2' >Tell us about your concerns below<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_textarea'><textarea name='input_2' id='input_116_2' class='textarea medium' placeholder='What kind of events are you planning?' aria-required="true" aria-invalid="false" rows='10' cols='50'></textarea></div></li><li id='field_116_6' class='gfield field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement</label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_116_6'><li class='gchoice_116_6_1'> <input name='input_6.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_116_6_1' /> <label for='choice_116_6_1' id='label_116_6_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_116_3' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_3' id='input_116_3' type='hidden' class='gform_hidden' aria-invalid="false" value='' /></li><li id='field_116_4' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_4' id='input_116_4' type='hidden' class='gform_hidden' aria-invalid="false" value='https://eventespresso.com/2015/04/updating-event-espresso-compatibility-wordpress/' /></li><li id='field_116_7' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_7' >Name</label><div class='ginput_container'><input name='input_7' id='input_116_7' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description__7'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_116' class='gform_button button' value='Send my message' onclick='if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} jQuery("#gform_116").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_116' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='116' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_116' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_116' id='gform_target_page_number_116' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_116' id='gform_source_page_number_116' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 116) {if(typeof Placeholders != 'undefined'){ Placeholders.enable(); }} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [116, 1]) } ); </script>