Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
The upgrade path from v2 did not work when you had old group_content_type entities with a hashed ID, which you would get when trying to combine a long group type ID with a long plugin ID.
Turns out we didn't need to up the last installed version in 3.3.1, this reverts that. People who were already on 3.x.x will now be able to upgrade to 3.3.x again.
Fixes a bug where people couldn't properly upgrade from v2.3.0 to v3.3.0 and fixes a permissions bug when group_support_revisions was enabled.
If you've already tried to upgrade from Group 2.3.0 and found that no database updates were available, you need to first install Group 2.3.1 and read those release notes for instructions. Then you should be able to go from v2 to v3
Fixes a bug where people couldn't properly upgrade from v2.3.0 to v3.3.0 and fixes a permissions bug when group_support_revisions was enabled.
If you've already upgrade to Group 2.3.0 and ran the database updates, you need to set the latest installed version back to 9211 rather than 10303. This can be done via Drush: drush php-eval "\Drupal::service('update.update_hook_registry')->setInstalledVersion('group', 9211);"
This is a feature and bugfix release that also comes with a limited upgrade path from 2.3.0! Instructions on how to upgrade can be found here. You should first update to the latest 2.x.x release before upgrading to this release.
This is a feature and bugfix release, but the most noteworthy thing is that the new 3.3.0 release now has a limited upgrade path from 2.3.0! You should first update to the latest 2.x.x release (this one) before you head over to the v3.3.0 release and try upgrading.
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: