Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Add a submodule with support for scheduled actions and emails.
Add global settings for registration settings sync on multilingual sites.
Prevent deletion of used registration types.
Add missing schema for a field formatter.
A cache clear must be performed after upgrading to this release.
Any sites using 7.x-2.0-beta releases should update to this release immediately.
Sites that allow non-administrative users to manage registrations because the users can update the registration host entity and have "update own registration" permission for a given registration type, may need to give those users the "administer own registration" permission for them to retain the ability to manage registrations after installing this upgrade.
Sites that allow non-administrative users to manage registrations because the users can update the registration host entity and have "update own registration" permission for a given registration type, may need to give those users the "administer own registration" permission for them to retain the ability to manage registrations after installing this upgrade.
This is a security release for the 7.x-1.x branch of the module. Information about the update can be found in the security announcement.
Changes since 7.x-1.7:
Revert "Issue #2357533 by alberto56: Improve registration_administer_registrations_access() function so one can check access for other accounts (not the current one)"
This is a complete rewrite of the module for Drupal 9 and 10. It works similarly to the Drupal 7.x-1.7 release but please consult the README for information on the differences.
Differences compared to the alpha4 release:
Various minor fixes and improvements required for the first Drupal 9/10 alpha release of Commerce Registration.
This is a complete rewrite of the module for Drupal 9 and 10. It works similarly to the Drupal 7.x-1.7 release but please consult the README for information on the differences.
Differences compared to the alpha3 release:
Various minor fixes and improvements required for the upcoming Drupal 9/10 release of Commerce Registration.
This is a complete rewrite of the module for Drupal 9. It works similarly to the Drupal 7.x-1.7 release but please consult the README for information on the differences.
This is a complete rewrite of the module for Drupal 9. It works similarly to the Drupal 7.x-1.7 release but please consult the README for information on the differences.
This release includes various bugfixes and minor feature improvements, and one security fix for anyone using anonymous registration. For more on the security issue, see the announcement. Note that if you use anonymous registrations and send out links for registrants to re-visit their registrations later, you may need to update the format for your links to use the new hash link or property.
This release includes various bugfixes and minor feature improvements, and one security fix for anyone using anonymous registration. For more on the security issue, see the announcement. Note that if you use anonymous registrations and send out links for registrants to re-visit their registrations later, you may need to update the format for your links to use the new hash link or property.
The first official release of the Registration-2.x branch, which allows for any entity with an Email Address to register. It also includes Registration Check-in, a rapid check-in tool for tracking event attendance.
This release rolls in some important community-contributed patches and bug fixes including a major one in the new handling of spaces in 7.x-1.2. It also adds a few nice UI features, including Views and Views Bulk Operation compatibility and the ability to customize the successful registration notification messaging.
It's been too long since we've had a new release for Entity Registration, so here goes. Aside from the usual slew of bug fixes, this release features the ability to set a maximum number of slots per registration, rather than just allowing 1 or many. We have more exciting features on the near term roadmap, including a "slot" system so, for example, users can register for volunteer slots on a given event. In the meantime, enjoy the full list of changes below.
Change default states form element to radio buttons which allows us to remove the registration.js file. Ensures a default is selected. Resolves #1908702.
Add views dependency to registration_views.
#1867564 by Matt V.: Provide entity cache support.
#1916432: HTML entities in host entity titles are output in the registration title.
We're thrilled to finally release a much anticipated upgrade to Entity Registration! This release contains loads of improvements and an exciting new wait list feature. Given the time since the last release and number of installs, we're forgoing further beta releases and diving right into stable ones. Please carefully review the full change log below.
ThinkShout's proud to release the first beta of the Entity Registrations module. Once again thanks to all the help and support from the community. Aside from all the goodness described below, future releases will come with an upgrade path making this module that much safer general consumption.
Hopefully a final alpha with loads of improvements and bug fixes before releasing a beta if nothing major comes up. Huge thanks to the community for all their contributions, especially @dpi, who's been very active with patches in the issue queue. Changes since 7.x-1.0-alpha4:
This release contains significant changes since 7.x-1.0-alpha1, including schema changes. There is no upgrade path from that release. Once we release a beta, hopefully very soon, we'll begin providing an upgrade path. Please take this for a spin and let us know how it works.
We're about to push some major changes to the module, namely multiple types of registration bundles and the ability to associate registrations with any entity type (rather than just nodes) or a specific entity. The schema's changing quite a bit and, at least initially, there won't be a up upgrade path. We at least want to create a stable tag for those already using the module. More to come soon.