Bug #39477
check if value's empty before calling checkUniqueField
| Status: | Resolved | Start date: | 2012-08-02 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | 2012-08-10 | |
| Assignee: | Federico Bernardin | % Done: | 0% |
|
| Category: | Generic FE code | Spent time: | - | |
| Target version: | 1.2.0 version | |||
| Branch: | Tags: | |||
| Votes: | 0 |
Description
If no value's provided the unique-check shouldn't be called on a field. Otherwise it returns false giving e.g. the message that a user with this name is existing already.
Patch attached.
History
Updated by Federico Bernardin 10 months ago
- Category set to Generic FE code
- Status changed from New to Accepted
- Assignee set to Federico Bernardin
- Target version set to 1.2.0 version
Updated by Federico Bernardin 10 months ago
- Due date set to 2012-08-10
With this behavior an empty field will be accepted al if it set as unique. In this situation you should set also required if you want a not empty field.
Updated by Federico Bernardin 10 months ago
- Status changed from Accepted to Resolved