Bug #5783
closed
Implement removal of edit display for static conditions
Added by krileon almost 9 years ago.
Updated about 7 years ago.
Description
Currently if a field has a static condition in profile edit it's still rendered. When the condition doesn't match it should flat out remove the inputs view as CB Privacy does. Once implemented it's likely this functionality can be removed from CB Privacy.
- Related to Task #5784: Remove field edit parameters added
- Related to deleted (Task #5784: Remove field edit parameters)
- Due date set to 16 March 2016
- Start date changed from 12 February 2016 to 16 March 2016
- Follows Task #5784: Remove field edit parameters added
- Follows deleted (Task #5784: Remove field edit parameters)
- Precedes Task #5784: Remove field edit parameters added
- Due date deleted (
16 March 2016)
- Target version changed from 701 to 821
- % Done changed from 0 to 50
Edit display also needs to be removed if the $formatting is set to "none".
- Tracker changed from Feature proposal to Bug
- Status changed from Assigned to Resolved
- % Done changed from 50 to 100
Tabs or Fields that are static hidden (custom value, usergroup, or view access level conditions) will now flat out be removed before rendering. In addition to this tabs that are hidden and $formatting is set to "none" will also be removed before rendering.
- Target version changed from 821 to 5.0.0
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by