Extra parent/new term forms at bottom of user form
| Project: | CCK Taxonomy Super Select Ultra |
| Version: | 5.x-1.1 |
| Component: | User interface |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | active |
First of all, GREAT module -- I'm administering a site with a lot of members who are librarians and archivists, so allowing community participation in taxonomy building without creating a one-dimensional lump of tags is a priority for me. (A lot of the site activity will be about taxonomy and classification as a group effort). This module does exactly what I've been looking for, with a nice friendly user interface to boot.
So, the issue:
Right now, I have Super Select set up to require input from a particular vocabulary, disallow freetagging at the top level of the vocabulary, allow freetagging on leaf terms, display parent terms as selectable, and add used terms as node tags. Everything functions exactly as it should.
However, when a user is creating new content, the fieldset containing the taxonomy options displays an extra "Parent" dropdown / "Add a Term" text box at the bottom of the list of available branches, with the available Parent terms coming from a sub-level of the hierarchy rather than the top.
To sketch it out, assume the vocabulary has 3 main branches, with a few sub-branches each, e.g.:
I. Events
a. our events
b. other people's events
II. Research
a. archival practice
b. pedagogy
III. Website information
a. online help
b. user feedback
The fieldset is showing collapsible fields for I, II, and III. At the bottom of each field are the paired "Parent"/"New Term" form elements, so a user can select an existing term, or assign a parent from existing terms and create a new term.
After field III, though, there's an extra "Parent"/"New Term" pair, with its parent terms listed as "Events | our events | other people's events" (e.g.).
Obviously, as long as those parts of the form aren't used, it's not compromising function. I can just write some help text and get users to bypass the extraneous form elements, which is what I'll be doing as a stopgap. But I was wondering if you had any idea where this is coming from?

#1
That is very strange and shouldn't be there. Could you provide a screen shot? I think I know what you are describing, but would like to make sure. Normally, when top level branching is allowed, there is a set of freetagging fields where you describe these to be. Let's get on this quickly and take care of it.
What other modules do you have installed that you think could possibly affect this?
#2
Sorry for the slow reply -- work has been a nightmare. Anyway, please see the attached screenshot. Note that the taxonomy branch that shows in the dropdown for the final (extraneous) "Parent"/"Add a term" pair is actually a subcategory of the "Events" branch which shows above.
#3
Subscribing.
#4
It looks like work for me has been even worse than for you! I have verified that the problem exists. I'm not sure yet when I can get to a fix. I'll try and see if it might be an easy one, in which case I could fix it soon.
#5
For now, a work around would be to anticipate the depth you need for each branch and create one leaf term in each, then check the box to disallow turning leaves into branches. This seems to make the parent junk go away.