Putting any number in the config field for "depth of taxonomy tree" depth does nothing.

I assume that "0" would show only the first level, "1" first and second, and so on. I could not find this relationship in the documentation. For all I know, "1" means the first level and "0" is undefined. The relationship should be defined in the help blurb beneath the selection box.

It ignores whatever number I use, including negative numbers.

Comments

dejamuse’s picture

dejamuse commented

I should add that this does work for drop down select widgets but NOT for the tree widget.

JIspahany’s picture

JIspahany commented

This doesn't work in the autocomplete widget as well.

mh86’s picture

mh86 commented
Status: Active » Postponed

yes, limiting the depth isn't supported by the tree widget yet. it requires some changes in the taxonomy manager tree form element before content taxonomy can make use of it (--> bug fix postponed until I made the changes in the taxonomy manager module)

@jazza
autocompletes support depth = 1 if you set a parent. depths > 1 would slow down the autocomplete feature

dajjen_82’s picture

dajjen_82 commented

Hi, Do you know when this bug fix will be fixed?

Thanks again for a great module!
//David

xenophyle’s picture

xenophyle commented
Version: 6.x-1.0-beta6 » 6.x-1.0-rc2

Is there any way to limit the autocomplete to the top level of terms in a vocabulary? Thanks!

Chris Gillis’s picture

Chris Gillis commented
Component: Taxonomy Tree » Autocomplete - Freetagging
Status: Postponed » Active

I agree with xenophyle,

"Is there any way to limit the autocomplete to the top level of terms in a vocabulary? Thanks!"

I want new terms to go through approval process, so I assign all new terms to a parent named "Other" and now want to prevent these children from showing up in the list. (admin can move term into top level once approved).

asb’s picture

asb commented
Priority: Normal » Major

I can confirm that the "Advanced settings for hierarchical vocabularies" are also completely ignored when select fields (pulldown menus) are used - opposed to #1.

Setup/precdure: I've defined a "Parent Term" at "Advanced settings for hierarchical vocabularies"; "Advanced PHP code" and "Depth of taxonomy tree" are empty.

However, in the pulldown menu I'm getting nothing but two levels below the parent term. Opposed to this the help text claims: "Leave this field blank to show the whole hierarchy." It does not do this.

If I enter a value, e.g. "5", into the "Depth of taxonomy tree" settings, the behaviour does not change at all - I'm still getting two levels below the parent term in the pull-down. I have no idea why this mechanism chooses two and not one, three or any other number of levels.

As far as I can see, there's currently no mechanism supporting the depth settings - select fields don't work for me, autocompletes do not work (see above), and the tree widgnet is not even supposed to support this at the moment. Setting this issue to "Major" since this behaviour seriously limits the use of 'Content Taxonomy' for many use cases. In my case, I don't want to limit the depth of the displayed taxonomy, or at least show 4-5 levels below the defined Parent term.

I'm still using 6.x-1.0-rc2 which was released almost one year ago (2009-Aug-19); would it make sense and is it safe to upgrade to 6.x-1.x-dev (last updated 2010-Jul-11)?

asb’s picture

asb commented

Related issue: #588334: Child terms not visible in select list

emptyvoid’s picture

emptyvoid commented

Hello,

I have the following module versions installed and I can't reproduce the issue you describe.

- Content Taxonomy 6.x-1.0-rc2
- Taxonomy Manager 6.x-2.2

I can limit the levels returned for:

- Autocomplete
- Checkboxes/Radio buttons
- Select List

The "Tree" display didn't reinforce limited the listing.

Consequently the multiselect (module) did limit the listing base on parent and depth constraints.