Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.<code>
Problem/Motivation
The Gutenberg editor UI is not available for group content type. When we add install the content type which has Gutenberg UI enabled inside a group, the Gutenberg editor is not available.
Steps to reproduce
Create a new content type and enable Gutenberg UI.
Go to content add the Gutenberg UI is enabled.
Go to Groups (Group module) and install this content type.
Go to content add inside Group.
Gutenberg editor UI is not coming up here.
Proposed resolution
Allow the Gutenberg inside Group node content type also.
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 3225284-content-type-resolver.patch | 12.92 KB | marcofernandes |
Issue fork gutenberg-3225284
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
szeidler commentedI'm not much into the details of Groups, but if it's using a regular node content type Gutenberg should be supported. If we're speaking about a different entity type coming from the Groups module, this is currently not supported. But you might be interested in following the progress in #3163200: Make Gutenberg entity-type-agnostic, where we're planning to support Gutenberg on all Content Entity Types and not only nodes.
Comment #3
thorandre commentedRelated to a feature not built yet, so setting that to be a duplicate related to the issue szeidler is mentioning.
Comment #4
marcofernandes commentedOk. I'm now in a project that uses group content and I understand bit more about this issue.
It all comes down to how Gutenberg gets the current node type to get Gutenberg settings. It gets from the current route.
Group module uses the "standard" node content types but it uses a different route and doesn't provide the content type as a parameter.
I'll dig a bit more but probably the "fix" should be done at Group module so we don't need to add a special case in Gutenberg for Group module.
Comment #7
marcofernandes commentedI added a kind of content type resolver + hook so Gutenberg editor doesn't load up only on the "default" routes for node and node type.
An example hook for Group Node module is provided here: https://git.drupalcode.org/project/gutenberg/-/blob/8.x-2.x/gutenberg.api.php#L151-161
Also added a patch against 2.5.