| Summary | prefs engine does not warn on missing keywords |
| Queue | Horde Framework Packages |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | birnbacs (at) gmail (dot) com |
| Created | 06/25/2018 (2568 days ago) |
| Due | |
| Updated | 06/25/2018 (2568 days ago) |
| Assigned | |
| Resolved | 06/25/2018 (2568 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
When this is missing, the pref will be readable and writable for
users who already have a value stored in the prefs container but
others will be unable to change the pref.
A log notification about a missing keyword in a preference would be
nice for developers all around
preference, but I believe every type does require this. This is
(perhaps not clearly enough) explained in the prefs.php file in horde
base. So, not going to add a log entry for this, but perhaps some
clearer language in prefs.php
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ prefs engine does not warn on missing keywords
Type ⇒ Enhancement
State ⇒ New
When this is missing, the pref will be readable and writable for users
who already have a value stored in the prefs container but others will
be unable to change the pref.
A log notification about a missing keyword in a preference would be
nice for developers all around