Unique field found, although there is none.

Created on 6 February 2015, almost 10 years ago
Updated 18 April 2024, 8 months ago

Hello!

I've found the following strange issue today:

"The date field requires a unique value, and the specified value is already used. Matches are found in the following content:"

So unique field finds a match, but even it can not point it out, there is none displayed.
The field in question is a date, with only the start date collected and only year-month-day. The unique field settings does not seem to matter, it always finds a match, but only at a certain date (2015-02-10).
I've tried to make other fields unique in that content type instead, and it works. Even if I try it with another date field.
I've deleted all the other nodes in that particular content type.
No unpublished nodes in that content type.
I don't use that particular date field anywhere else.
Also I tried to add other fields to the unique field group, and use the "combination of fields to be unique" setting, but still shows this error.

Rather strange, any ideas?

Thanks!

πŸ› Bug report
Status

Closed: outdated

Component

Code

Created by

πŸ‡­πŸ‡ΊHungary csero

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡¦Ukraine AstonVictor

    I'm closing it because the issue was created a long time ago without any further steps.

    if you still need it then raise a new one.
    thanks

Production build 0.71.5 2024