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.
This should be the final release of Group 8.x-1.x and merely adds proper Drupal 10 support. Please consider upgrading to Group 2.x.x, making sure to read the release notes and change records.
Sponsored by Idéative
Even though many people are still on version 1, I am heavily invested in development of new features on version 2/3. The API of version 1 has reached its limits of what can be done, whereas the new systems in version 2/3 simply allow for way more feature requests to be considered.
You are viewing the release notes for the fresh install version, upgrades from 8.x-1.x should update to version 2.0.0. There is no direct upgrade path to version 3 from version 1 or 2 (requires migration, see image below).
You are viewing the release notes for the upgrade path from 8.x-1.x, new installs should use version 3.0.0. By design, version 2 and version 3 are functionally identical. Therefore no upgrade path is needed nor exists from version 2 to version 3.
A lot of code has gone into the 8.x-1.x branch that I later ended up regretting. Time to clean house and get rid of it!
It's been a long run for Group 8.x-1.x but the time has come to move on. Existing projects should look into upgrading to 2.0.0. New projects can simply install the twin version 3.0.0.
This release was tagged as supporting D10, but it sadly doesn't yet. A final version adding just D10 support is being looked at by a volunteer, but you'll have to sit tight until they have some budget to work on this.
This branch will only receive security fixes from now on.
You are viewing the release notes for the fresh install version, upgrades from 8.x-1.x should update to version 2.0.0 first
Both version have identical functionality. The only difference between version 2 and 3 is that this version has the latest naming pattern in its machine names for 2 entity types:
A lot of code has gone into the 8.x-1.x branch that I later ended up regretting. Time to clean house and get rid of it!
This release contains several reworks, new features and new APIs for you to work with. Please check out the change records for a full list of changes, but I'll list the key parts below.
This would not have been possible without the generous sponsorship by Global Game Jam. I've been advocating for more sustainable contribution for a while now and GGJ heard that call and answered by fully sponsoring the review, development and approval of this new functionality.
After the recent nightmare of security releases following the 1.0 release, we can hopefully get back to the planned system of smaller releases with bugfixes and smaller new features.
The "I should have known node grants were a powerful enemy" release
By removing node grants in 8.x-1.0, we made some regular access checks (not query access) too permissive but only if Group was the only module implementing hook_node_grants().
The "I can't believe it's finally here, what will I do with my life now?" release.
Of special note
The Group module now requires the VariationCache module. If you use Composer to update Group, you will automatically download this new dependency. You will need to run updates to be able to enable the module.
Minor update that mainly fixes a bug where RC3's update hooks were insufficient. Now, every view should be properly updated to use the new cache contexts without the need for people to manually edit and resave the view.