Recurring Events

The plug-and-play recurring events and registration system for Drupal.

The Recurring Events module is a plug-and-play recurring events and registration system designed to be site agnostic and extensible. Detailed information about the module is available on the module's external documentation page.

Module Basics

The module allows site editors to create and manage events which recur in a variety of ways - including consecutively, daily, weekly, monthly, yearly, and custom recurrence configurations. An event series comprises of multiple event instances, each of which inherits data from the series, but can also be managed and viewed independently from the series itself. This offers great flexibility when it comes to modifying event instance dates and times or removing them altogether.

The module also has four submodules:

* recurring_events_registration enables registration for events
* recurring_events_views which swaps entity lists for flexible views
* recurring_events_reminders which allows sending of reminder emails for event registrants
* recurring_events_ical provides iCal download links for events

Dependencies

The recurring_events module has 2 core dependencies and 1 contrib dependency:

* datetime_range (core)
* options (core)
* field_inheritance

The views submodule also has a dependency on the core views module.

Similar Modules

The closest comparison would be the smart_date module, which adds a field type that allows RRule compliant date recurrence configuration to be added. While that module does a really great job, this module approaches things differently. With smart_date, a content editor would have a single entity with a recurrence field that builds instances of that event. With recurring_events, eventinstances are separate entities completely and therefore can be overridden or extended, without affecting the rest of the series. This module also comes with a registration submodule, including the ability to register either for an entire series, or individual events. Using smart_date that would not be possible as there is only one entity.