Anonymous | Login | Signup for a new account | 2023-09-27 12:24 CDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Vertical ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001357 | [In-Portal CMS] Data Management | bug report | always | 2012-07-18 08:50 | 2012-07-25 05:29 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001357: Validation of system settings is shared across multiple settings | ||||
Description |
There is a special feature in In-Portal (that I bet nobody knew about) that allows each system setting have it's own validation logic, e.g. be always required or allow only numbers. To use it you need to place serialized array of field validation options into "Validation" column of that system setting. Because of we are not using this very often (I think we should start using it at some point) error, where validation logic from system setting A is passed on to next system setting in same subsection was unnoticed for a long time. For example you have 2 system settings one after each other: * Site name * Session expiration timeout When you apply "required" validation to "Site name", then "Session expiration timeout" settings become required too. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic![]() In-Portal Open Source CMS |