Profile permissions driving me crazy
Can someone please let me known what settings need to be involved to simply create a field on a profile which is only viewable by the owner?
Of the 4 options for visibility on the profile creation page:
- Hidden profile field, only accessible by administrators, modules and themes.
- Private field, content only available to privileged users.
- Public field, content shown on profile page but not used on member list pages.
- Public field, content shown on profile page and on member list pages.
...the 2nd and 3rd would seem to possibly apply. However, using the 2nd, "Private field...", the profile is not available unless I give users the "Administer Users" permission. Which opens up All such profile fields to All users.
Trying the 3rd option, "Public field, content shown on profile page but not used on member list pages" makes the fields available to all users when viewing profiles.
What is the proper combination of Visibility and Permissions to simply have a field created on the profile that is only viewable by the author (without allowing the author the option of choosing via something like Profile Privacy)?
This should be easy and common---I have Got to be missing something...
-Daniel
Anyone??
Anyone??
...
Subscribe.
I've been looking around: annotation.module, whisper.module, cck field permissions etc. for functionality that will allow a node author to view private text (which could be a comment, field, annotation etc.) associated with their node that can be editable by admin.
So far all of the modules allow everybody with a particular role to view the 'private' text. It should be fairly easy to hack a module and add a if($user->uid == $node->uid || $user->uid == 0) condition to the access check, but I'm wondering if there' s a more elegant solution?