Feature proposal #2168
closed
parameter to set registration display
Description
Allow setting display of privacy controls on registration on a privacy by privacy basis. For example Field A can choose to show privacy controls on registration, but Field B can choose not too yet still have privacy controls on profile edit.
Files
Updated by krileon almost 14 years ago
- File 2168a.patch 2168a.patch added
- File 2168b.patch 2168b.patch added
- Status changed from New to Resolved
- Assignee set to beat
- % Done changed from 0 to 100
Patch adds parameter to change the default selected privacy. So the selected is not always '' (visible on profile) when no privacy setting has been specified.
Updated by krileon almost 13 years ago
- Status changed from Resolved to Assigned
- Assignee changed from beat to krileon
- % Done changed from 100 to 80
With patch applied it reverts the setting back to default everytime a user is edited. The default should only apply if no database value is supplied.
Updated by krileon over 12 years ago
This is due to visible on profile does not store a privacy setting, which IMO it should (missing privacy shouldn't assume visible on profile was selected).
Updated by krileon over 12 years ago
- File 2168a_rev1.patch 2168a_rev1.patch added
- Status changed from Assigned to Resolved
- Assignee changed from krileon to beat
- % Done changed from 80 to 100
Rev1 ensures it only applies if the user does not exist. So it only applies the default during registration (frontend or backend). Will not apply for already existing users.
Updated by krileon over 11 years ago
Implemented default privacy parameter for tab, field, and profile privacy settings. Note not as provided here as 2.0.0 is a complete rewrite.