Major Update: Event Espresso 4.3

This release brings many improvements to existing core features and a few new features, such as duplicate events, iCal integration, batch email/newsletter system, registration form and payment system optimizations.

An Important Calendar Update is Available!
If you use the 1-click update feature, please be sure to update the EE4 Calendar to 3.1 BEFORE updating the EE4 core plugin.

New Features

  • Duplicate Event
  • Ticket Required Option
  • Added iCal Integration
  • Drag-n-drop Answer Values
  • Order Questions by Question Group
  • Question Editor Style Changes (thanks to Matt Van Andel)
  • Re-order Datetimes in Ticket Editor and Single Page Checkout
  • New Hooks and Filters for Developers Added to the Registration Process


  • Gateways
  • Messages System
  • Migration Issues
  • Miscellaneous Spelling Errors

ImageSupport for “Ticket Bundles” & “Graduated Pricing”
Starting with Event Espresso 4.3 you can offer discount pricing and/or graduated pricing based on ticket quantities.

  • Ticket Bundles
    Can be used to set a per ticket price, based on a pre-defined quantity of tickets. This article shows how to create a ticket bundle where you can set a lower price per ticket when purchased in a bundle.
  • Graduated Ticket Pricing
    Can be used to set a per ticket price, based on a quantity range of tickets, similar to a tiered pricing structure. This article shows how to set graduated ticket pricing where you can set a lower price per ticket for larger quantity ticket purchases.

Messages System Changes/Fixes
We’ve improved the Custom Template System, added a “Newsletter” Message Type for sending batch emails, and made a couple of minor updates.

  • Message Type – Newsletter message type
  • Messages Admin – Updated to implement a new Custom Template creation/edit process
  • Event Editor – Modify Messages metabox in event editor to use new custom template system
  • Messages System – Default ‘From’ Email shortcode changed to [CO_FORMATTED_EMAIL]

acf-home-panel-fieldsAdvanced Custom Fields Integration
Fully customize WordPress edit screens with powerful custom fields, using the Advanced Custom Fields plugin for WordPress. We’ve added several new hooks and filters throughout the Single Page Checkout system to give developers the ability to integrate with this awesome plugin.

Payment Gateway Fixes
This time around we’ve spent some time making sure the payment processing features work better, faster, and are easier to understand for your customers. We’ve also added better support for tracking partial payments.

  • Send address fields to Mijireh
  • Show failed payments in payment response
  • Thank You page now uses the WordPress Heartbeat API to automatically display payment status updates
  • Fix for Single Page Checkout so it displays the correct amount owed based on when a payment has already been entered into the system

6 thoughts on “Major Update: Event Espresso 4.3

  1. Great news!

    However the links above “developers corner” etc. does not work (404) 🙂
    Also, It would be soooooooooooooooo great and much easier for us developer if you had a fairly complete list of these wonderful hooks and filters you keep adding in! A section in the documentation would be absolutely friggin swhunging fraggletasticly wonderful!
    You don’t need to provide example of each one but a list with the hooks name and parameters (and type of those parameters) would be so friggin helpful I’m all but weeping of joy at the mere idea!


    • Hi Jonathan, Sorry about that, and thanks for pointing it out. It was scheduled for 12pm today (MST I believe), but I have brought it forward so it should be accessible now. We do have which is a script generated list of functions etc. It’s not perfect, but may assist in the interim. While a search in the code would reveal the filters and hooks, I’ll add a request for more formal documentation in the future.

  2. Hey Jonathan,

    Keep your eyes on We are using that as the space to created developer centric documentation and are slowly adding to it over time.

    In the meantime, we follow a consistent naming schema for all our filters and actions. All our filters are prefixed with “FHEE” and all our actions are prefixed with “AHEE”. Most IDE’s or text editors have fairly good search tools, so you can use that to generate a list of all actions and filters available in the code.

    Hope that helps!

Share a Reply or Comment

Your email address will not be published.

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

Event Espresso