We are still actively sifting through previously reported bugs across all our add-ons and you can expect multiple updates over the coming weeks.

Security Vulnerability Patches

This update includes some security vulnerability patches which were reported to us recently and prompted this early update, as we are still working through older reported issues. We strongly recommend you update due to these known vulnerabilities.

CVE numbers are in the readmes and will be disclosed in due time. We’d like to thank WordFence for their ongoing security efforts and responsible disclosure policy.

Whilst Pro add-ons are not affected by these vulnerability reports, we also encourage Pro customers to upgrade and have also extended our Cyber Week promotional period a few more days to encourage those that have not recently renewed to do so and have the most supported versions of both the free and Pro plugins.

Reserved vs. Pending Bookings

Another noteworthy change, moreso for developers, in the latest update is the separation of reserved vs. pending bookings. Previously, a pending booking would be considered ‘reserved’ if the setting to reserve pending bookings was enabled.

We have also added #_UNAVAILABLESPACES and #_RESERVEDSPACES as additional event placeholders.

Developer Notes

This caused a few issues with correctly counting ‘pending’ bookings with special statuses, such as offline payments in Pro versions, given the Pro gateways have the option to reserved a pending space or not, overriding the default option for free bookings.

Not all pending bookings are necessarily reserved once you introduce custom pending statuses, and now we count available spaces by considering reserved spaces, vs. previously counting pending spaces (and only if pending spaces are considered reserved).

This is a subtle change, and is backwards compatible with previous Pro versions (and in fact fixes this issue in older Pro versions too). Developers should take note that using the following new filters and functions to count reserved spaces will produce more reliable results:

em_bookings_get_reserved_spaces
em_ticket_get_reserved_spaces

It’s essentially the same as the pending filters, but specific to a reserved state, whereas the original pending filters count as pending and not necessarily reserved.

Changelogs

Events Manager 7.2.3

Events Manager Pro 3.7.2.3

The post Events Manager 7.2.3 and Pro 3.7.2.3 appeared first on Events Manager for WordPress.

Changelogs

Events Manager 7.2.2

Events Manager Pro 3.7.2.2

The post Events Manger 7.2.2 & Pro 3.7.2.2 appeared first on Events Manager for WordPress.

This major new feature involved another overhaul of time-based logic under the hood. Now, you can create single-day events without needing to create recurring events to add multiple times in a day.

What this means

Whilst seemingly a nuance on event creation, this powerful new feature opens the door to a LOT of new possibilities, including truly supporting different event types, such as appointments and general bookings based on multiple times in a day. Along with a new timeslot picker during the booking process, this new coding structure makes the logistics of managing multiple fractions of the same event on the same day much easier.

If you want to go crazy, timeslots are also supported in recurring events too! That means you could create the same event for multiple parts of the week, month, year (or whatever) with different timeslot patterns, date ranges or even different timezones! We’ve meticulously developed this framework of code to layer into all our features to create truly flexible and powerful event structures.

As an example, having wrapped up 7.2, we spent only a few hours to develop a new Pro feature in 3.7.2 for recurring events (launched in 7.1) and timeslots; moving bookings between dates and times. Previously, this sort of feature would have involved clunky coding and required a significantly longer amount of time to implement.

Events Manager Pro Compatibility

We always strive to make our updates compatible with previous Pro versions. In some situations such as this, it’s impossible to implement such powerful features without requiring some updates to our Pro version. Therefore, Pro 3.7.2 is required for timeslot support, and timeslot support is automatically disabled to prevent undesirable and unintended behaviour. However, earlier Pro versions will still work normally but without timeslot support, just as before.

Going Forward

The latest three major updates (7.0, 7.1 and 7.2) have required monumentous amounts of time and effort to implement in this relatively short amount of time. This follows up on a big push for a mountain of different feature updates over the past year.

We’re going to focus momentarily on resolving known bugs, compatibility issues with third party plugins and updating our documentation and website which has had a hard time keeping up with all our addtitions, enhancements and overhauls! We look forward to having the chance to show you all the power of our new suite of functionality before we continue with this exciting journey of creating the most powerful event framework out there.

Developer Notes

Whilst we’ll now be reviewing and updating our documentation to match these new features, there are some general cosiderations to keep in mind especially with current custom code:

• event_id can now be a string, representing the event ID and a timeslot ID, for example $EM_Event->event_id may produce something like 123:123 if the event has timeslots.
• We will now refer to event IDs which include the timeslot as an Event UID
• Supplying an event UID to em_get_event() or new EM_Event() will load an event with a timeslot_id populated.
• To get the actual event ID you can now use the get_event_id() method on the EM_Event, EM_Booking, and EM_Ticket_Booking(s) objects.
• Individual Event timeslots are not stored in wp_em_events, rather are combined with the new table wp_em_event_timeslots re-using the same event_id for same-day timeslots.
• The general event containing timeslots will have the first time and ending time of all the timeslots on that day, and acts like a normal start/end datetime if you load up the general event ID without a timeslot context.

There’s a ton more that goes on under the hood, but we hope these important considerations will help you transition your custom code if necessary. Generally speaking, if you load event with supplied event IDs, just ensure you don’t do any is_numeric() checks, and change that to something like preg_match( '/^(\d+):(\d+)$/', $event_id, $matches ) instead.

Changelogs

Short but sweet, here’s the changes, each one packs a punch!

The post Events Manager 7.2 and Pro 3.7.2 appeared first on Events Manager for WordPress.

We know, we know. Every time we release a major version, we say it’s one of the biggest updates yet. With 7.0, we truly meant it ; that was a complete rewrite of Events Manager. But here we are again, and this release is another massive leap forward. It might not be the biggest rewrite by comparison to 7.0, but it’s certainly right up there, reflecting the level of hard work and dedication we’re putting in right now to push Events Manager further than ever.

With this release, we’re introducing Archetypes, a new foundation that completely redefines how events are created, customized, and managed.

This update also comes with a Pro 3.7 update (integrating some features with Archetypes), deep developer improvements, and a major rewrite of our underlying codebase, setting the stage for endless flexibility.

What Are Archetypes?

Archetypes are a new way to create multiple event types within Events Manager. Instead of being locked into a single “Events” post type, you can now create distinct post types (archetypes), each with its own settings, labels, and behaviors while still powered by the same reliable Events Manager engine.

Flexible Event Types

• Each archetype is its own WordPress post type.
• Separate admin areas for each archetype.
• Independent labels and front-end slugs (for example, /events/, /courses/, /workshops/).
• Dedicated booking areas per archetype.

Some practical examples of archetypes:

• Workshops
• Appointments
• Rentals

Customizable Features

For each archetype, you can enable, disable, or customize features, including:

• Bookings
• Locations
• Taxonomies
• Formatting
• Custom fields
• Time zone support
• Custom formats
• Search forms
• Repeating events
• Email templates
• Recurring events

Separate Booking Management

Each archetype has its own bookings section. In future updates, we’ll expand this further with unified dashboards and cross-archetype lists.

Multisite Integration

• Network admins can create custom archetypes network-wide.
• Choose to enforce all, restrict to certain archetypes, or allow subsites to create their own.
• Define a default archetype for each subsite.

Custom Labels and Slugs

Rename “Events” to anything you like, such as “Activities,” “Workshops,” or “Seminars.” You can even change the underlying post type and slug.

Developer Extensibility

We’ve built Archetypes with extensibility in mind. Almost any option in Events Manager can now be overridden on a per-archetype basis, and more will be added in future releases.

Events Manager Pro 3.7

With Pro 3.7, bookings now report separately for each archetype in the transactions section. This means you can clearly see which transactions belong to archetype bookings.

The Custom Automated Emails and Custom Event Booking Emails features in Pro have also been integrated with custom archetypes. This allows you to create unique automated email rules per archetype, further tailoring communications for each type of event.

In upcoming releases, additional Pro features such as custom booking forms, gateways, and coupons will be toggleable per archetype, with individual formatting overrides.

Note: Users must upgrade to Pro 3.7 to make use of these Archetype-related PRO features.

Developer Notes

This release includes a major rewrite of how post types are generated and registered. Event post types are now arbitrary and flexible with the option to create more than one event CPT while running off the Events Manager engine.

This work lays the foundation for future expansions while maintaining stability and performance. For developers, there are important new functions and best practices:

Option Handling

• Replace get_option() with em_get_option(). This ensures Events Manager returns the correct archetype-specific option value.

Archetype Helper Functions

• Use new helpers in EM\Archetypes for context checks:
  • EM\Archetypes::isevent( $object ) : check if an object belongs to an event post type, instead of checking against EM_EVENT_POST_TYPE
  • More helpers are available for checking locations and related contexts.

Output and Widgets

• Shortcodes and PHP functions (lists, calendars, etc.) accept:
  • event_archetype : specify which archetype to display.
  • If omitted, defaults to the main archetype (the shipped Events post type, regardless of renamed label or slug).

Custom Loops and Displaying Events

• Wrap custom loops to ensure correct archetype context:
  • Start with EM\Archetypes::set_current( $post_type ).
  • End with EM\Archetypes::revert_current().
• This guarantees that archetype-specific settings are respected during rendering.

What’s Next?

Archetypes unlock near-limitless customization possibilities. Adding integration for features or settings that can be customised on a per archetype basis is actually relatively easy. However each one does require testing, there’s a lot of features, so a lot of time consuming testing is required!

Here’s a glimpse of what’s coming regarding further work on this feature:

• Override Anything
  The architecture allows almost any feature or option to be customized per archetype, from categories and locations to booking forms and notifications. We will be adding more and testing them as we go.
• Cross-Archetype Views
  Unified booking dashboards, lists, and calendars that can combine multiple archetypes.
• PRO Feature Matrix
  Toggle individual PRO features per archetype, with independent formatting overrides.

Terminology and Inheritance

With this major new concept inevitably comes new terminology. Below we explain the key terms that will now be used throughout Events Manager and our documentation.

• Archetype: the new umbrella term in Events Manager for defining event types.
• Main Event Archetype: the default event post type shipped with Events Manager. Cannot be removed but can be renamed and altered.
• Location Archetype: tied to location usage. Only one exists, but it’s still considered an archetype.
• Custom Archetypes: unlimited; inherit from the main archetype by default but can override settings independently.

This new terminology will be used consistently in our plugin and documentation moving forward.

Wrapping Up

Archetypes will be a game-changer for many users that run different event flows. They bring flexibility, control, and scalability to Events Manager like never before. Whether you’re a site owner, a developer, or a multisite admin, this update opens up new levels of customization.

And this yet another stepping stone to something bigger! We’re already hard at work on Events Manager 7.2, which will be another major update, possibly our biggest yet in terms of shifting functionality. We’re keeping details under wraps for now (though there might be a subtle hint in this very post ).

Changelogs

Events Manager 7.1

Events Manager Pro 3.7

The post Events Manager 7.1 – Introducing Archetypes appeared first on Events Manager for WordPress.

Additionally, we’ve added some functionality that disables duplication of events and locations on the three most popular duplication plugins, including Yoast Duplicate Post, Duplicate Page, and Duplicate Post. This has caused a lot of confusion and headaches, because duplicating with these plugins break data integrity of our post types, given we store more data outside traditional tables (tickets, bookings, etc.). Whilst this won’t fix issues with already-duplicated events, we hope this will minimize future confusion!

To compensate the above disabling of duplication plugins for our post types, we’ve added location duplication, so copying is always possible for both events and now locations!

7.0.5 Changelog

The post Events Manager 7.0.5 appeared first on Events Manager for WordPress.

We were notified of this just over 24 hours ago, these were reported to WordFence by security researches on the 24th and 25th of June. These will be responsibly disclosed to the public in 30 days as per WordFence disclosure policy, giving everyone time to update.

Updating is Strongly Recommened

These issues are graded 6.1, 6.4 and 7.4 in severity., comprised of 3 different reports / vulnerabilities. Whilst these vulnerabilities should not directly enable unauthorized access your website if exploited for correctly configured websites, they are certainly vulnerabilities we strongly recommend get patched by the latest update.

We recommend everyone upgrades to the latest version of Events Manager 7 or 6.6.5 (see below).

Given we have just released a major update and there is a significant enough number of users still transitioning we have released a version 6.6.5, allowing users to update to that version as well, without jumping to version 7.

Updating older versions to Version 6.6.5

To update to version 6.6.5 from version 6.6.4.4 or earlier, you have quite a few options.

One easy way is by using the WP Rollback plugin. Install that, visit the plugins page and you’ll see a ‘Rollback’ link on the Events Manager plugin. You can then click on that and select 6.6.5 to roll back to.

To update manually, you can download version 6.6.5 directly and install it on your site via FTP or by uploading the ZIP file directly as covered in our installation instructions.

Changelogs

Changelog 7.0.4

Changelog 6.6.5

• Fixed 3 security vulnerabilities reported by Muhammad Yudha and @mikemyers via WordFence.

The post EM 7.0.4 – Security Vulnerability Fix appeared first on Events Manager for WordPress.

Events Manager 7.0.3 Changelog

Events Manager Pro 3.6.2 Changelog

The post Events Manager 7.0.3 & Pro 3.6.2 appeared first on Events Manager for WordPress.

We’re committed to quickly iterating with updates fixing reported issues (new and old), free and Pro users alike. We’re currently primarily focused on any issues being reported due to the 7.0 update, helping everyone get up to the latest version.

Extended support for WordPress.org forum users

Whilst for our Pro customers we’re able to quickly request more information and diagnose issues faster, we would like to extend our support to free users during this time so we can quickly identify, reproduce/debug and fix wider-spread issues.

We are restricted in what we can ask on the wordpress.org forums due to forum guidelines in place, we cannot request login info from users, with the interest of keeping the forum safe to the public in general. Whilst we’ve been providing support for 15 years on there, we understand this is a blanket policy to keep people from providing sensitive information to unknown parties.

If you are experiencing a widespread issue and asking for help on the .org forums, you can also follow-up with a comment on our contact form, providing a link to the forum thread and any further information that may be relevant, which will be kept securely in confidence. If necessary we can get in touch to get more information about your setup so we can debug issues faster.

Thanks to everyone for their supportive comments and patience whilst we take Events Manager to the next level. This is just the beginning of something awesome!

Events Manager 7.0.2 Changelog

The post Events Manager 7.0.2 appeared first on Events Manager for WordPress.

Check out our demo site, and see a recurring event in action!

This release introduces an entirely new way of handling recurring events, with layered scheduling logic, smarter management tools, and a brand-new terminology that distinguishes between traditional repeating events and the new recurring format.

New Terminology: Recurring vs. Repeating Events

To better reflect the underlying architecture, we have to add and change some terminology. Recurring events, as we know them in version 6, are now effectively called Repeating events, because recurring events are now a different beast altogether!

• Recurring Events are events with multiple dates and/or times managed on a single page. They share a single booking form with a calendar picker to choose the individual date and time.
• Repeating Events (formerly “recurring”) are still supported and behave as before, with individual entries for each event recurrence managed independently.

Both types now benefit from our revamped recurrence pattern builder, offering a streamlined and flexible interface for scheduling.

Key New Features in Events Manager 7

A Smarter Recurrence Engine

• Create complex recurrence rules with multiple layers, inclusions, and exclusions. Pretty much any recurrence pattern can now be created!
• Manage individual occurrences with custom times or cancellations, while retaining centralized control of content and booking settings.

Backward compatibility

• All existing repeating events continue to work as before, but allow you to add new recurrence rules.
• Easily convert old events to the new recurring system via admin tools or within the event editor itself

Enhanced User Experience

• Timezone-aware booking forms and calendar displays for a recurring event.

Getting Started

For those upgrading, you need to activate recurring events, any users who previously had recurring events enabled in v6 will now see them as ‘Repeated Events’.

New installations will, by default, have recurring events enabled, and repeated events disabled.

To enable and disable these types of events:

1. Go to Events > Settings > General and make sure both “Enable Recurrence” and “Enable Repeating Events” are selected.
2. If you wish to convert your repeating events into a single recurring event, use the Admin Tools tab to convert legacy repeating events to the new system in bulk, or convert them individually within the editor.

Whether you’re building flexible class schedules, global webinars with timezone support, or want more control over repeating sessions, Events Manager 7.0 gives you the tools to do it all — smarter, faster, and more intuitively.

Stay tuned for more guides and tips as we roll out additional support content in the coming days.

The post Events Manager 7.0 Released: Powerful New Recurrence Features and Smarter Scheduling appeared first on Events Manager for WordPress.

This update is fresh off the press, and we’re sharing it now to give everyone as much time as possible to start testing. This is a preliminary post. More information, screenshots, technical details, and updated documentation will follow over the coming days and weeks.

This release completely redefines how recurring events are structured and managed, laying the groundwork for more flexible and powerful scheduling capabilities moving forward.

Early Access for Testing

Events Manager 7.0 Beta is now available, along with Events Manager Pro 3.6.0 Beta — both ready as development versions to test the new recurrence features in action.

The new updates can also be seen on both our demo and trial sites, you’re welcome to give it a go there!

A New Recurrence System

The core of this release is a brand-new recurrence system built from the ground up. It enables:

• Multiple recurrence sets per event
• Layered recurrence rules with exclusions
• True timezone-based calendar and search functionality
• Smarter rescheduling that retains unchanged recurrences
• Seamless upgrade paths from repeated events to the new recurring system
• Booking form improvements including date pickers and calendar selectors

These changes not only solve long-standing limitations but open the door to a range of new use cases and configurations.

As part of this shift, traditional recurring events are being renamed to “repeated events”. The new recurring events system allows all recurrences to be managed and displayed from a single event page. Repeated events can also be converted to the new recurring events structure, including 302 redirect pages for old single recurrence pages.

Backward Compatible and Safe to Test

If you’ve previously worked with repeated (formerly “recurring”) events, you’ll now have access to a vastly more dynamic system that’s designed to scale with your needs. At the same time, we’ve focused on maintaining backward compatibility where it matters — while the architecture has been overhauled, database changes have been minimal and designed with rollback safety in mind.

Try the Beta Now

The beta is available now via the development version. You can start testing it today, ideally on a staging site, upgrading is easy and can be done from your dashboard.

Although this release has undergone extensive internal testing, we always recommend backing up your site before upgrading.

Feedback is welcome and encouraged — we’re eager to see how you use these new tools and look forward to hearing from you!

The post Events Manager 7.0 (Beta) appeared first on Events Manager for WordPress.