Hi,
I am grateful for this module. It would be even better if the default group role could be different for different group content types.
Hi,
I am grateful for this module. It would be even better if the default group role could be different for different group content types.
Comments
Comment #1
dejan.maric.max commentedHi Sarenc,
I've rewrote the module to accomplish that (Sorry SUN, it is quite simple patch that you can include in main branch)
so Now You can choose default role to be different by OG content type
Comment #2
sun@destination_node: Can you attach a patch with the required changes for this issue only?
Comment #3
mrfelton commentedHere is the above as a patch against the latest in CVS.
Comment #4
massud commentedThere is a bug in this patch. Node is not loaded for user update case in the hook_og() implementation:
should be like this:
Comment #5
held69 commentedsubscribing
Comment #6
hefox commentedHaven't tested it quite yet, but here's a patch with the above in mind. the preview patch also had an unrelated slight bug fix, so did not include that.
However, settings this to needs review as the upgrade patch for existing sites isn't handled.
Comment #7
izmeez commentedsubscribe
Comment #8
hefox commentedUpdated to remove calls during node_load during hook_nodeapi 'insert' (as user [author] is added during insert of group)
Comment #9
hefox commentedAdd setting the cache during 'insert' to prime it for user insert
Comment #10
hefox commentedMissed a spot needing to be changed