View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0001176 | Pending Requests | Core Infrastructure | public | 2012-08-21 03:39 | 2014-04-05 17:22 | ||||||||
Reporter | Korkonius | ||||||||||||
Assigned To | |||||||||||||
Priority | high | Severity | feature | Reproducibility | N/A | ||||||||
Status | new | Resolution | open | ||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001176: Core functionality that allows non-core modules to store user preferences | ||||||||||||
Description | In my work with the Order management module I've encountered several scenarios where it would be preferable to save some settings as user preferences, and since there is no functionality for this provided by Web2Project each module would have to implement it's own settings system. I feel that the core system should allow module authors to add/remove user preferences, perhaps with the restriction that it is only allowed to edit its own preferences... | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files |
|
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2012-08-21 03:39 | Korkonius | New Issue | |
2013-09-08 22:20 | caseydk | Priority | normal => high |
2013-12-03 21:17 | caseydk | Project | v3.1 Release => v3.2 Release |
2014-01-21 17:58 | caseydk | Target Version | => 3.2 |
2014-01-25 00:42 | caseydk | Category | General => Core Infrastructure |
2014-03-13 12:43 | caseydk | Project | v3.2 Release => Pending Requests |
2014-03-13 12:43 | caseydk | Category | Core Infrastructure => General |
2014-04-05 17:22 | caseydk | Category | General => Core Infrastructure |
2014-04-05 17:22 | caseydk | Target Version | 3.2 => |