Feature proposal #2168
closed
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.
- 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.
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).
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.
- Assignee changed from beat to krileon
- Target version set to 2.0.0
Implemented default privacy parameter for tab, field, and profile privacy settings. Note not as provided here as 2.0.0 is a complete rewrite.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by