Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I am using the latest OG 7.x-1.x dev version 22-June-2011 on drupal 7.2
On enabling og field access, the authenticated users can't access their profile fields. ( custom fields that I created e.g. Age, College, etc.)
On the other hand , admin can access it.
Comments
Comment #1
amitaibuDid you allow permissions for non-group/ gorup members?
Comment #2
nikkubhai CreditAttribution: nikkubhai commentedAll the groups are open and anyone can subscribe. But, I am not getting how are profile fields of the user related to groups.
I mean even if some group is closed, a user won't see the group content. But, how is he denied from editing his own profile fields?
Comment #3
Joe Vallender CreditAttribution: Joe Vallender commentedI've just come across this issue after thinking this behaviour was due to corrupt data in a massive D5->D7 migration I am doing in the next week. Thank goodness it isn't!
I'm not sure if this extra info helps....
When OG field access is enabled, users who are a member of at least one group do not have access to edit their custom user fields unless either
- the global OG permissions have the edit link checked for each field
- the same boxes are checked on any groups using custom permissions
It doesn't quite make sense but the fix is a quick enough one for now. I should also mention I may not be using the absolute newest OG release which may have set sensible defaults in global permissions etc...
Comment #4
mrfelton CreditAttribution: mrfelton commentedI spent a long time trying to work out why the profile fields were not visible for editing. The reason was because the OG Field Access permissions for those fields had not been set.
So, @Amitaibu - to confirm - setting the OG Field Access permissions for those fields does make them visible/editable.
However, it does seem strange that these field permissions are governed by OG, when the user profiles, or profile fields are not in OG context at all.
Comment #5
amitaibu> setting the OG Field Access permissions for those fields does make them visible/editable.
If the profile entity is a group/group content (i.e. it's in an OG "context") then yes, og-field-access takes control over those fields.
Comment #6
mrfelton CreditAttribution: mrfelton commentedMy profile fields are attached directly to the User - would that be considered in an OG context? I never specified that the User entity should be a Group or Group content, but it does have a 'Groups audience' field attached to it - this field was added by OG automatically.
Comment #7
amitaibu> My profile fields are attached directly to the User
If the fields are attached to a user, so yes, they are in OG context (as the user is a "group content").
Comment #8
mrfelton CreditAttribution: mrfelton commentedOk, thanks for the clarification. I consider this as solved then, but I'll leave it open since I don't know the details of the original poster's setup.
Comment #9
amitaibuComment #10
bjaxelsen CreditAttribution: bjaxelsen commentedI think this could be more easy if the "groups audience" did not have a double meaning
1) content audience
2) user's membership of one or more groups
How about keeping the term "groups audience" for no. 1 and use the term "group membership" for no. 2?