-
Type: Bug Report
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 5.0.0
-
Fix Version/s: 5.2.0
-
Component/s: Data Management
-
Labels:None
-
External issue URL:
-
Change Log Message:Fixes validation problems in system configuration section
-
Story Points:1
-
External issue ID:1357
-
Copy Issue Key:
-
Patch Instructions:
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.
- mentioned in
-
Wiki Page Loading...