Jump to:
| Project: | Taxonomy Super Select (TSS) |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I encountered two problems assigning categories to content nodes. Both problems went away when I removed this module.
Lesser problem: The taxonomy/category words were all sorted Z->A instead of A->Z. They were correct in admin taxonomy screens and forms, but in content nodes the sort order was inverted. Not a show-stopper but annoying.
Major problem: Choosing certain category words would result in the wrong term ID being assigned to the content node. I never found a pattern, but for instance selecting "Health", which was term id 140, ended up with term id being assigned to the content, which in-turn caused term "Travel" to be displayed when viewing the content. This was entirely repeatable and we never found a way to prevent it. Every time we tried to fix this type of problem in content, it immediately happened again. The onl;y cure was to uninstall Taxonomy Super Select. Then we could fix the content nodes and they stayed fixed.
Comments
#1
Sorry, correcting a typo (wish I could edit the original post).
In a content node, selecting "Health" with term id 140 resulted in term id 137 "Travel" being actually assigned to the content node.
We tried deleting the term with id 140 and re-adding it. The new term id of "Health" was 164. When we selected Health, we again ended up with Travel ! A few other terms were also goofed up, but this was the most common because Health is a term we use a lot.
#2
I believe this will be fixed with the patch in #140609: Only could get it to alphabetize by weighting.
#3
This is now in 5.x-1.10.
#4
Automatically closed -- issue fixed for two weeks with no activity.
#5
Sorry, I have to reactivate this issue. The problem still occurs. I have the same problem with changes in selected term IDs.
dg, darktiger
#6
I also have two terms that seem to be messed up somehow. Any article tagged with term1 appears in term2 (when we go to edit the article, term2 is selected).
The two terms are in the same vocabulary, and each have child terms, but they have no relationship to each other. Disabling Taxonomy Super Select lets me go in and fix the articles that have been wrongly tagged.
#7
Hi,
have you found a solution to solve this serious problem? the problem (like #6 by kathc) continues to generate serious errors in pages of our sites. It is very important because it forces us to uninstall the module and thus not able to use the functionality of the module.
thanks.
gluca rivalta
#8
Subscribing
This and http://drupal.org/node/496738 are duplicate bugs (this for 5.x, the other for 6.x, but same problem)
#9
Only security bug will be fixed in 5.x. Who gets this problem can fix yourself with the same method in #369656: TTS doesn't save parent terms?.