Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
With fresh install of Group module (v3), I can't install Group Media.
Steps to reproduce
- composer require 'drupal/group:^3.0'
- composer require 'drupal/groupmedia:^3.0@alpha'
Result
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/groupmedia ^3.0 -> satisfiable by drupal/groupmedia[3.0.0-alpha1].
- drupal/groupmedia 3.0.0-alpha1 requires drupal/group ^2.0 -> found drupal/group[2.0.0-alpha1, ..., 2.0.0-beta3] but it conflicts with your root composer.json require (^3.0).
Proposed resolution
Add support for group v3. Probably will need to add a new version of the module. groupmedia v4
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | groupmedia-v3.patch | 29.91 KB | rivimey |
Issue fork groupmedia-3315927
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
le72Comment #3
lobsterr commentedThe version for group 2.0 has been recently released , the version for group 3.0 is not yet there, It would be the next step
Comment #4
le72Thank you @LOBsTerr. Looking forward to seeing v3. I am understanding right, if you start a new project Groups v3 should be chosen, not v2?
I mean for the new Drupal project built with Groups, Group Media is not ready yet.
Comment #5
lobsterr commentedIt would be like this:
V3 -> Group 2.0, This version can be used, if you already using group 1.0
V4 -> Group 3.0. This version for new projects.
Comment #6
le72Yep, @LOBsTerr, looking forward to seeing v4. Ready to help with review and testing.
Comment #7
rivimeyDare I say... me too?
Just exploring group and of course I'm using group:3.0
Comment #8
rivimeyOk, posting this as a starting point, as I thought I'd see how much work was needed.
I've updated core reqs to ^9 || ^10, dropping 8.8 as being EOL.
I'm not sure how to deal with the service "plugin.manager.group_content_enabler", which seems to be expected to come from group but group:3 doesn't export that or "plugin.manager.group_relationship_enabler". Should it be "group_relation_type.manager"?
Hoping this will serve as a useful base.
Comment #9
lobsterr commented@rivimey, yes, it looks like a good start. I will check it today.
Comment #10
lobsterr commentedComment #11
lobsterr commented@rivimey, Your patch has been created based on 2.0 version, where you should have used 3.0.x version. I did a quite a lot of changes there and I am afraid we can miss it. I will continue the work in the current fork.
Comment #12
rivimeySorry for my mistake... I did a git clone and didn't realize the default fork was not the latest one. I switched fork to 3.0.x and at least the module now installs (previously lots of errors!). Don't know any more at present.
[Used git clone because 3.0.x isn't showing up in composer require as an available branch, though v2 is.]
Comment #13
lobsterr commented@rivimey, Don't worry, it is almost done, I have faced some issues with media overview page. Trying to understand if it is a group bug or not.
Comment #14
lobsterr commentedComment #17
lobsterr commented