Unique violation warning with repeats.
tpainton - July 25, 2009 - 22:32
| Project: | Unique field |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi, when I am using multiple values for uniqueness (2). I get the following warning. It has repeats.
* This form requires that the fields name, birthdate are a unique combination. The specified values are already used. Matches are found in the following content:
o Stan:07/25/2009
* This form requires that the fields name, birthdate are a unique combination. The specified values are already used. Matches are found in the following content:
o Stan:07/25/2009
o Stan:07/25/2009
o Stan:07/25/2009
I am using automatic node titles to make the note title come from field name and field birthdate.
#1
It appears that the last three nodes listed also share the same dob. So basically, the multiple uniqueness is not working. This example is confusing because "stan" is not the first name. It is short for Standard.. The first name field is unique in the lower 3 cases, but NOT the top.
Sorry.. I always seem to make something easy difficult.
#2
Sorry accidetnly scrolled to closed.. this is open.
#3
I have the same problem with the latest version 6.x-1.1. The message is printed twice:
* This form requires that the fields Title, Author are a unique combination. The specified values are already used. Matches are found in the following content:
o unique title test
* This form requires that the fields Title, Author are a unique combination. The specified values are already used. Matches are found in the following content:
o unique title test
Other than that, great module... thanks!
#4
I do have the same problem. Any patch available ?
#5
Thanks for reporting this. I've fixed it in the latest release. Now when you use the rule that the fields must be unique in combination, all of the matching nodes are shown together.
#6
Great, thank you for fixing it!
If you use it in a another language, remember to update your translations, since the error message has been updated.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.