Bug #1998
closed
fields set as read only will not save their privacy controls
100%
Description
When a field is set to Read Only and privacy is changed (drop-down fully functional and displayed) upon saving the privacy controls are not being saved properly.
Updated by krileon over 13 years ago
- % Done changed from 0 to 10
This is due to CB trigger prepareFieldDataSave not firing on frontend for readonly fields.
Updated by krileon over 13 years ago
- Status changed from New to Feedback
- Assignee set to beat
- Priority changed from Normal to High
- Target version set to CB 1.3
- % Done changed from 10 to 20
Should this trigger fire or should a new one be created? Seams logical to fire the trigger and other internal functions should handle the IF scenarios. Trigger should ALWAYS be prepared to prevent integrations from failing IMO.
Updated by beat over 13 years ago
New trigger added in r1276 / r1277 in CB, as existing trigger does save lots of things elsewhere and here does check that field is editable.
Updated by beat over 13 years ago
- Assignee changed from beat to krileon
- % Done changed from 20 to 90
- Estimated time set to 1:00 h
r1278 should fix this.
Requires testing.
Updated by krileon over 13 years ago
- Status changed from Feedback to Assigned
- Assignee changed from krileon to beat
Fatal error: Maximum function nesting level of '100' reached, aborting! in D:\xampp\htdocs\cb\j15\components\com_comprofiler\plugin\user\plug_cbprivacy\cb.privacy.php on line 297
I receive the above after saving profile.
Updated by beat over 13 years ago
- Status changed from Assigned to Closed
- % Done changed from 90 to 100
Fixed in r1284 that regression introduced by r1278 / r1279 .