Project

General

Profile

Actions

Feature proposal #2168

closed

parameter to set registration display

Added by krileon almost 14 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
05 January 2011
Due date:
% Done:

100%

Estimated time:

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.

http://www.joomlapolis.com/component/option,com_joomlaboard/Itemid,38/func,view/id,137935/catid,124/limit,6/limitstart,0/


Files

2168a.patch (5.06 KB) 2168a.patch krileon, 02 February 2011 22:22
2168b.patch (1.97 KB) 2168b.patch krileon, 02 February 2011 22:22
2168a_rev1.patch (4.64 KB) 2168a_rev1.patch krileon, 25 June 2012 18:08

Related issues 1 (0 open1 closed)

Has duplicate CB Privacy - Feature proposal #1673: Preset privacy option by adminClosed02 May 2010

Actions

Updated by krileon almost 14 years ago

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.

Actions #2

Updated by krileon about 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.

Actions #3

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).

Actions #4

Updated by krileon over 12 years ago

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.

Actions #5

Updated by krileon almost 12 years ago

  • Assignee changed from beat to krileon
Actions #6

Updated by krileon almost 12 years ago

  • Target version set to 2.0.0
Actions #7

Updated by krileon almost 12 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.

Actions #8

Updated by krileon over 11 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF