The ability for users to add terms on the fly is a life saver really, but I am having an issue. This is my setup:

Salary
1. Hourly
I. $10
II. $20
III. etc.
2. Yearly
I. $40000
II. $50000
III. etc.

I have it arranged so that a user may select any of the general salary guidelines, however, they may add a more specific amount if they choose so. That's where your module saved my life. However, I would really like if these custom terms would not show up in the dropdown after being created. I double checked and indeed, every user can see these custom terms after being created.

Now this seems to be a large task seeing as the terms still need to be in the vocabulary to show up in the published node, so am I missing a feature (such as a filter for default terms) or just going about this the wrong way? If it's the wrong way, would creating a vocabulary for these custom terms only and setting up proper permissions be the ideal way?

I'm not opposed to digging in and rigging something up myself if given a proper way to approach it, but I feel like I am missing something important.

Thanks

Comments

Anonymous’s picture

edit:
I found this, naturally, right after I posted this thread.

"The ID for excluding or including this element is admin/content/taxonomy/edit/term/59.edit-description."

I'm going to work with this for a bit and assuming this is what I need. If that's not the right way, feel free to correct me.

wim leers’s picture

Status: Active » Postponed (maintainer needs more info)

I have no idea what you are referring to, but to me it sounds like you need something like Taxonomy access control. And as far as I know, that doesn't work with HS. It might, but I doubt it. It's a very, very rarely requested feature. I can see its use, but I won't work on this myself. Patches are welcome, as always.

Anonymous’s picture

Cool I'll put that on my project list for the future, but for now let's keep it postponed.

wim leers’s picture

Status: Postponed (maintainer needs more info) » Fixed

Once #505090: Term Permissions support for Hierarchical Select Taxonomy is in (likely later today), you may be able to use that.

Status: Fixed » Closed (fixed)

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