Comma in string (non-delimiter) prevents adding new terms if partially match

Created on 16 July 2018, over 6 years ago

Updated 21 August 2024, 5 months ago

According to the release notes, terms with commas are supported since 7.x-2.0-beta1 and the delimiter can be configured since 7.x-2.0-beta3.

With the delimiter configured to ";" if you type a new term containing the coma, the sentence «The term '@term' will be added.» appears as far as both parts of the term, left and right to the coma, does not match exhisting terms.

I mean, If I try to add "Smith, John" it works only if you don't have any other "John" in the list, otherwise those items are displayed instead of letting you add a new term.

🐛 Bug report

Status

Closed: won't fix

Version

2.0

Component

Multiple values

Created by

🇪🇸Spain mtoscano

Live updates comments and jobs are added and updated live.

Missing content requested by

🇦🇺Australia dpi

5 months ago

Comments & Activities

Issue created by @mtoscano
Comment 5 months ago →
🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
Who the hell uses terms with commas? Even titles/labels should not have comma in web systems. Sorry this is absolutely wrong assumption and usage of terms or reference labels ... especially in a context like Autocomplete fields whre commas are used to delimit terms. I do not even understand why this module wants to support it while core does not. This module should only extend core and do not reverse core assumptions.

Apart from that this issue is 6 years old with no activity and EOL of Drupal 7 is around the corner, so I assume maintainers would agree to have this closed.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024