using this module to select taxonomy items. If a partial value is typed then selecting the associated taxonomy item creates a new item based on the partial value entered ... example, taxonomy has a value "Gandia", typing "nd" shows "Gandia", click to select then save and a new value "nd" is created and stored as the value of this item.

I have had to remove all uses of this module because of this - shame because it initially worked exactly as needed.

Comments

Infoloko’s picture

Infoloko commented

this may be the same as #1754164 (https://drupal.org/node/1754164) - can't test at moment as I've replaced all Autocompletes with standard droplists .. will test against my code asap

virtuid’s picture

virtuid commented

Same problem here, applieng this .js file SOLVED the problem
https://www.drupal.org/node/2044431

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
commented
Title: typing a partial value creates new value based on the partial value » Typing a partial value and clicking on the match creates new value based on the partial value
Version: 7.x-2.0-beta2 » 7.x-2.0
Issue summary: View changes
Priority: Normal » Major

I'm seeing this behavior again, and I don't think I saw it in the last beta, just in the update to the full release.

I would describe this as a major bug. Just to recapitulate what is happening, because it looks like the same as what was reported back in 2012:

1. Have a taxonomy with the term "ABCDEF" present.
2. Use an autocomplete deluxe-enabled field and type "CD".
3. Click on "ABCDEF" that appears.

Expected behavior: The tag "ABCDEF" is selected and added to the field.
Actual behavior: Both the tag "ABCDEF" and a new tag "CD" are selected and added to the field.

This does seem to be a function of the click itself -- using the keyboard to select the match doesn't result in the same bug.

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
commented

Oh and in responding to #2 (its recentness makes me think that this is in fact a bug that re-appeared in the recent full version): The .js file linked in that other issue is a forked version of an old copy of autocomplete_deluxe. I don't know why it wasn't uploaded as a patch, but using that file in place of the current version means effectively downgrading to a copy of this module from several years ago. (If it had been uploaded as a patch, we could reroll it and apply the changes to the newest version of the module's JS.)

So I don't think that's really a solution, although a careful comparison of that file with the current one might reveal the fix for this issue.

k.skarlatos’s picture

k.skarlatos commented

Issue is caused by last commit, here are git bisect results
7b939aab21d9e9dc76fdcccf0dc3109456c800bc is the first bad commit
commit 7b939aab21d9e9dc76fdcccf0dc3109456c800bc
Author: s.Daniel
Date: Wed Feb 25 10:14:26 2015 +0100

Issue #1853896 by s.Daniel: Submit on blur option

:100755 100755 0bca13dec4e3976010bcd0c24da05f754cf5bd99 3c219a5ecb9f1da3b405a31995f8ede484b35ec3 M autocomplete_deluxe.js

  • sepgil committed c67a0ad on 7.x-2.x 
    Reverted the last commit, since it caused the bug described in Issue #...
sepgil’s picture

sepgil commented
Status: Active » Fixed

I ran into this issue today and reverted the last patch. I also reopended the issue #1853896: Submit on blur option and will create a new release.

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
commented

Thanks for the quick response & release on this!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

freelylw’s picture

freelylw commented

same problem here, after update to the latest 7.21 version, problem is gone for registered user, but still exist for admin.