Hi,
We've noticed another possible bug with the Tagging module. We are using the Tagging module/widget with the Extractor module and tagging_extractor_suggest. We are getting duplicate suggestion buttons for every suggested term. I've verified that there aren't duplicate entries in the actual taxonomy. When you click the button to select one of the terms, it's duplicate stays as an available suggestion, but is not clickable. Since there is no indication which button is the actual term this is causing duplicate terms to actually be created in the taxonomy when the user clicks on the "wrong" term button. For now I've disabled the Extractor and tagging_extractor_suggest module to prevent users from entering duplicate terms into the DB. I've attached a screen shot of what we are seeing on the node edit screen.
We are using Tagging 6.x-2.1 and Extractor 6.x-1.0-alpha3.
Incidentally, using the auto-complete suggest box does NOT list or enter duplicate terms into the taxonomy.
Thanks for the help!
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | dup-suggest-tagging.png | 7.34 KB | timwood |
Comments
Comment #1
timwoodWeird, the screenshot didn't make it into Drupal.org. I've never had this problem before. Trying to attach again...
Comment #2
EugenMayer commentedHmm could it be that the hook is called twice, could you check this? (dsm)
Thanks for the report!
Comment #3
timwoodCan you explain how to check if the hook is called twice?
Thanks,
Tim
Comment #4
EugenMayer commentedusing dsm ( developer module) or echo whatever. Just go into the suggestion submodule and look for the api hook
Comment #5
timwoodEugen,
You were right. It looks like nearly the exact same code is being called twice, once in the tagging module and once in the tagging_extractor_suggest module. I guess the code in the tagging module is left-over from before you created the sub-module. Below is the code straight out of each .module files.
tagging/tagging.module
modules/tagging_extractor_suggest/tagging_extractor_suggest.module
So, for now, I've disabled the tagging_extractor_suggest module because the code is running twice due to that module being enabled. With the sub-module disabled I get one suggestion for each term as expect.
Comment #6
EugenMayer commentedAh i see. Your suggestion was completely correct, this is a leftover!
Thanks for the help and effort!
Comment #7
EugenMayer commentedwill be fixed in 2.2
Comment #8
EugenMayer commentedreleased in 2.2
Comment #9
EugenMayer commentedreleased in 2.2