Support for Group CCK Fields
| Project: | OG User Roles |
| Version: | 6.x-1.5 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Hi there,
I'm really loving the power of OGUR... however either its missing a core piece of functionality (in which case this is a feature request!) or I'm missing something.
Am I right in assuming that the role within the group only applies to content INSIDE the group, and not the group itself? I want a scenario where I have quite a long list of cck fields attached to my group node type (called Project). The project has some information which is "public" to all group members, however I also want some fields to be visible (viewed only - not edited) by a role (called "Co-Organiser"). Co-Organisers can not edit any group details, but they can see more fields.
I set up the permissions on a co-organiser to view the fields using the core node access module and to be hidden for an authenticated user, but neither see the hidden fields.
Wondering if there is an easy way of doing this, and if not, if there is anyway the OG role could apply also to the actual group node in question.
Thanks,
Adam
#1
After the rise of the rewritten OGUR 4.x for Drupal 6, in which many unrelated features of OGUR were removed, and nearing a release of Drupal 7, I'm closing down old issues.
#2
I have actually sort of achieved this by using OGUR node access permissions. A user can actually see nodes that his group roles give him access to in a view outside of the group.
But, I don't believe that we will allow a user to edit a node outside of group context if the user only has permission to edit the node within group context.
The person who changed the status of these issues to "won't fix" was not authorized to do so: http://drupal.org/node/352139#comment-2352234
OGUR 6.x-1.x will continue to be maintained by me.
However, in this case, am continuing to maintain the status at "won't fix".