I'm getting a hard error if I edit content with the group selector widget enabled, or if I view content with the groups formatter enabled.
The setup is very default, a single test group type, a single test group of that type, and a single content plugin enabled. Editing/viewing any node of that content type produces an error, whether the node is already a member of a group or not.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 3154400-6.patch | 2.65 KB | dww |
Comments
Comment #2
johnpitcairn commentedTo avoid polluting the issue summary, here's the trace:
Comment #3
johnpitcairn commentedYup, there is no such method in group 8.x-1.0-rc5 or current 8.x-1.x-dev. How on earth is this expected to work?
Comment #4
johnpitcairn commentedI needed Group dev and the patch at #3152324: Add a getPluginIdsByEntityType() method to src/Plugin/GroupContentEnablerManager to make this module usable.
Comment #5
dwwSorry you spent time on this. I probably should have mentioned that issue/patch on the project node. This is all exactly expected (for now).
But that issue is taking a while, so I'm thinking of doing our own thing until that solution lands in Group core.
Comment #6
dwwI looked into service decoration and that whole fancy mess, but it seems to be a huge PITA and a ton of bloat for such a trivial thing. I'll probably be struck down by lightning for such blasphemy, but this simple procedural solution seems way easier, especially since this is just stop-gap code until this method is provided by Group core.
Thoughts?
-Derek
Comment #7
johnpitcairn commentedI share your skepticism about some of the sillier OO complexity that gets produced ;-)
This at least allows me to not chase group dev, a practice that I really try to avoid, and at least I'm patching the module that has the issue. I'm prototyping to determine whether group can reasonably support the slightly offbeat access model I need. I suspect it will be more work and custom code to bend group to do what I want than to just write the node access grant code myself, and group UI is pretty awful for my use-case (which is why this module seems promising), so I suspect I won't be around for long.
Anyway, I'm happy to call this RTBC. It doesn't explode when I touch it any more.
Comment #8
dwwMore specific title and saving credits. Thanks!
Comment #10
dwwComment #11
johnpitcairn commentedThanks for the fast alpha update!