Profile privacy, consider changing word "publicly"
izmeez - August 24, 2008 - 19:33
| Project: | Profile Privacy |
| Version: | 6.x-1.1.1 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
This is a suggestion for a minor cosmetic change.
When user is allowed to over ride default settings the text displayed to the user with the check box is "Do not display publicly". This can be misleading in setups where the fields are only displayed to registered users. Even though this may be stated in the instructions provided along with the fields it may be helpful to replace the word "publicly" with "to regular users". This would need to be changed in the module when the word "publicly" appears the second time.
$form[$category][$key]['#description']);
// Create the privacy checkbox
$privacy_checkbox = array();
$privacy_checkbox['private_'. $key] = array(
'#type' => 'checkbox',
'#title' => t('Do not display !field publicly', array('!field' => Maybe there is some other phrase that would be better to use. Thanks for your consideration. I look forward to being able to use this module.
Izzy
#1
I don't find "to regular users" to be more informative than "publicly". What constitutes a "regular" user? Of course the same problem exists for what's considered "public", so the problem exists either way.
If you wish to change the string, you might consider doing a hook_form_alter() to change the string, or use String Overrides module.
#2
I agree that "to regular users" isn't a particularly great term but it may help to distinguish between the general public and other authenticated users, whereas the word "publicly" does not make that distinction. It would be nice to find a better term but in the meantime it is easy enough to make a custom change to the module and change the second occurrence of the word "publicly" for those so inclined, like us.
Thanks for this very useful module. One that we consider essential.
Izzy
#3
Rather than altering the module you should use http://drupal.org/project/stringoverrides
I'm open to other words, but yes, "regular users" isn't right. Since user profile access is decided by roles it should technically follow which roles have that permission. Putting issue to 'needs more info' to get some other ideas. This isn't a high priority for me unfortunately.