Task #5784
closed
Remove field edit parameters
Added by krileon about 8 years ago.
Updated over 7 years ago.
Description
Remove the parameters to control field edit based off moderator only edit or view access level. CB Conditional should handle this scenario. This will prevent double coding.
- Related to Bug #5783: Implement removal of edit display for static conditions added
I'm not sure if it is the same use-case, even if similar implementation.
Also isn't there is a B/C issue of settings if we flat out remove that feature ?
And those settings are sensitive settings, since related to privacy.
The parameters will be migrated as needed on install. Those parameters have nothing to do with privacy and were simply implemented to fill a need now properly done by CB Conditional. CB Conditional didn't exist at the time of that implementation. I'm maintaining double the code doing the same thing and they conflict. It will be removed, but not until 5.0.0 which isn't anytime soon and only after CB Conditional can absolutely cover this exact case.
- Due date set to 15 March 2016
- Start date changed from 12 February 2016 to 15 March 2016
- Follows Feature proposal #5853: Implement custom condition for moderators only added
- Related to deleted (Bug #5783: Implement removal of edit display for static conditions)
- Precedes Bug #5783: Implement removal of edit display for static conditions added
- Precedes deleted (Bug #5783: Implement removal of edit display for static conditions)
- Due date changed from 15 March 2016 to 17 March 2016
- Start date changed from 15 March 2016 to 17 March 2016
- Follows Bug #5783: Implement removal of edit display for static conditions added
- Status changed from Assigned to Rejected
- Target version deleted (
5.0.0)
- % Done changed from 0 to 100
After much consideration these parameters will goahead and remain. It's a much simpler usage than CB Conditional even if they are accomplishing the same things.
Also available in: Atom
PDF
Updated by 
Updated by