I written the custom plugin extend GroupContentEnablerBase. It was work for me. But when I updated the group to last version. And goto /admin/group/types/manage/{group type}/permissions
. The website is broken.
See documentation:
Custom entities as group content
It’s easy to develop for...
See the developer experience:
https://www.drupal.org/project/group/issues/2810131#comment-12364263
After this commit,
https://www.drupal.org/project/group/issues/2702735#comment-12353860
the CustomPluginDeriver.php need update like follow.
copy from gnode,http://cgit.drupalcode.org/group/diff/modules/gnode/src/Plugin/GroupCont... :
diff --git a/modules/gnode/src/Plugin/GroupContentEnabler/GroupNodeDeriver.php b/modules/gnode/src/Plugin/GroupContentEnabler/GroupNodeDeriver.php
index 744d235..ecc1a91 100644
--- a/modules/gnode/src/Plugin/GroupContentEnabler/GroupNodeDeriver.php
+++ b/modules/gnode/src/Plugin/GroupContentEnabler/GroupNodeDeriver.php
@@ -16,7 +16,7 @@ class GroupNodeDeriver extends DeriverBase {
$this->derivatives[$name] = [
'entity_bundle' => $name,
- 'label' => t('Group node') . " ($label)",
+ 'label' => t('Group node (@type)', ['@type' => $label]),
'description' => t('Adds %type content to groups both publicly and privately.', ['%type' => $label]),
] + $base_plugin_definition;
}
Comment | File | Size | Author |
---|---|---|---|
#11 | 2928190-11.patch | 964 bytes | dravenk |
|
Comments
Comment #2
dravenkThis error happen after this commit :
Please reviews.
Comment #3
dravenkAdd related issue and replenish error message:
Comment #4
dravenkComment #5
dravenkComment #6
dravenkComment #7
lawxen CreditAttribution: lawxen at Sparkpad commented2928190-2.patch looks wrong. It's a tricky patch, Not solve the root problem.
Comment #8
lawxen CreditAttribution: lawxen at Sparkpad commentedI test that, this is not a bug!
Comment #9
lawxen CreditAttribution: lawxen at Sparkpad commentedThis is a change of group, custom group content needs to be updated too,
see https://www.drupal.org/node/2702735
Comment #10
skyredwangComment #11
dravenkI think updates should not be a reason to break old functionality. Because this feature used to be good. If so, should have a way to tell the developer this update.
Comment #12
dravenkComment #13
skyredwangAccording to #9, this is work as designed.