Events Manager 6.5 & Pro 3.3

We’re very happy to announce Events Manager 6.5 and 3.3, which include a MAJOR rewrite of our booking admin tables, including full-support for the front-end bookings admin area.

Under the hood, this was a massive undertaking, which started as an attempt to replicate the somewhat-recently revamped booking admin tables available in the WP Dashboard area and make it available in the front-end admin areas. This snowballed into something far bigger (and longer!) than we had planned, and what we are happy to finally push out in 6.5.

There’s so many changes that have taken place both visually and under the hood, it’s hard to summarize it into a release post! We’re working on a more comprehensive follow-up post to demo the new features.

For now, we invite you to just update and check it out! Here are some of the major new power-ups:

  • Switch views to Tickets or Attendees and split records to ungroup bookings into individual sets of ticket bookings and/or Attendees!
  • Sortable columns, including user meta (name, email etc.), ticket data (prices, spaces, etc.), booking meta (custom fields), attendee meta (custom fields).
  • More powerful search capabilities, search attendee, user and booking meta.
  • Quickly preview grouped data with tooltips in bookings tables:
    • For example, a booking with 2 ticket types can display both tickets (see screenshot).
  • Switch views to Multiple Bookings mode (Pro feature), view all your Multiple Bookings.
  • Responsive booking tables.
  • Front-end support, including charts!
  • Fine-grained export options, allowing splitting exports by view (ticket, attendee etc) and selecting any field for export.
  • All booking tables including “events with bookings” and transaction tables revamped to use new table layout and features.
  • Check In/Out shortcut actions (Pro feature) and a quick-reference check-in status column.
  • Improved bulk action support.

Here’s a screenshot of how your admin area might look after the upgrade, hope you enjoy it

Pro Backwards Compatibility

Users running older versions of Pro may experience inconsistent display and export results when upgrading to 6.5, and will not benefit from some of the new features which were updated in Pro 3.3.

We aim to take all possible measures to make our updates backwards-compatible. In most cases, this is possible, but unfortunately due to the huge overhaul in the infrastructure of how tables in general are now generated by Events Manager, incorporating all these features in an extendable and flexible manner, it simply wasn’t possible to transition earlier versions of Pro into the fold. Doing so would hinder the progress of development and innovation.

Over the 10+ years where Pro has been available, there have only been two major changes requiring a Pro upgrade, this will inevitably have to be the third.

Changelogs

Events Manager 6.5

  • Added multi-array support for EM_Bookings_Table::get_booking_actions() allowing for separate sections of actions
  • Removed em-bookings-action and em-bookings-action-X classes from booking actions links in preference of data- attributes and an em-list-bookings-row-action
  • Added sortable ticket columns to bookings admin tables
  • Improved bookings table search input allowing more search options, including user name and email
  • Fixed bug where em_bookings_get_sql_conditions filter is called twice in EM_Bookings_Table::get_sql_conditions()
  • Changed minimum PHP requirement to 7.0 due to use of shortcut array syntax, null coalescing and ternary operators
  • Added sanitization/decoding options for shortcode format content due to security implications.
  • Fixed bug in calendar widget preventing saving/loading on widget area.
  • Added calendar_size option to calendar widget.
  • Fixed PHP warning when calendar_size is undefined.
  • Added medium calendar size options to widget and settings ddms (in development).
  • Added .em-loading and .em-working (wrapper) classes for more cross-theme compatibility when loading something via AJAX.
  • Moved .em-warning into scss.
  • Removed legacy search form CSS from events_manager.css.
  • Updated and rewritten EM_List_Tables to provide base table functionality for other data tables, support front-end and advanced ordering/searching capabilities.
  • Updated Bookings and Event with Bookings tables to unify front/back-end, added new views (tickets, attendees), sortable columns, responsiveness and much more.
  • Unified/standardized exporting of list tables to support exporting for any EM_List_Table-extended tables.
  • Added #_BOOKING_UUID placeholder.
  • Added EM_Bookings::get(), EM_Ticket_Bookings::get() and EM_Tickets_Bookings::get() search functionality with advanced ordering capabilities.
  • Added EM_Events::get_accepted_fields() for SQL ordering detection.
  • Transitioned out of jQueryUI sortable for booking tables to a vanilla JS alternative – Sortable 1.15.2.
  • Removed all outdated tables in events-manager/admin/bookings folder.
  • Added booking dashboard charts support for front-end with option to specifically enable/disable in settings.
  • Added default calendar size option.
  • Fixed calendar JS errors when switching months.
  • Added custom event for modal opens.
  • Fixed tippy regeneration issues due to uncontained calls to tippy().
  • Fixed tooltips referencing external elements via the data-content attribute not displaying that content accordingly.
  • Fixed privacy nag issues when editing bookings already made in the past before enabling privacy settings.

Events Manager Pro 3.3

  • updated for support for new Events Manager 6.5 admin booking tables
  • added check in/out shortcuts to booking admin tables
  • added check in/out color-coded booking admin table column for quick reference
  • added support for sortable booking and attende form field meta columns in booking admin tables
  • migrated transactions booking admin tables to new EM_List_Table infrastructure
  • added multiple bookings view to booking admin tables
  • fixed nonce errors with editing multiple bookings front-end
  • fixed nonce errors with editing multiple bookings front-end
  • fixed offline transactions recording timestamp according to site time not UTC, causing time inconsistencies in tables