Anonymous | Login | Signup for a new account | 2024-05-18 05:26 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001047 | [In-Portal CMS] Data Management | bug report | always | 2011-05-04 15:26 | 2011-10-21 12:24 |
Reporter | alex | View Status | public | ||
Assigned To | erik | ||||
Priority | normal | Resolution | won't fix | ||
Status | closed | ||||
Summary | 0001047: Misplaced field format validation code | ||||
Description |
In-Portal has ability to validate value in the field using given regular expression (regexp option in field definition). All works fine, unless you need to change field value (not on form, but in code) before validation takes place. To solve that problem I'm proposing to move processing of "regexp" option from kFormatter class into kDBItem class. |
||||
Additional Information |
This "regexp" option is specified in unit config file, like "core/units/users/users_config.php" in "Fields" array, e.g. 'Fields' => Array ( 'Login' => Array ('type' => 'string', 'formatter' => 'kFormatter', 'regexp' => '/^user.*$/', 'default' => ''), ), This will force all new users to have "user" in front of their login name to be entered before registration could continue. |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |