If a vocabulary is marked as required and the person has vocabulary permissions set for it, it shows up, but there are no terms in it. Unless they are given the permission "administer taxonomy".

The problem is...I don't want them to have the ability to delete wholesale terms from a vocabulary, or administer it in any way. This wasn't a problem before, but adding this module to restrict by role seems to have inadvertently required I escalate their permissions.

Am I doing something wrong? Thanks!

CommentFileSizeAuthor
#2 taxonomy-issue.jpg32.9 KBjgarbe

Comments

jcisio’s picture

Could you be more clear, please? As I can't understand.
- The "administer taxonomy" permission is to add new vocabularies
- The "admin vocab perms" permission is to define permission for each vocabulary. If a user has this permission, he can set which role can edit/view which vocabulary.

And in nocase a vocabulary shows up with no term (more detail, or a screenshot please?)

jgarbe’s picture

StatusFileSize
new32.9 KB

I was hoping it might be simple user error, but I'm beginning to suspect (and fear) that it may be some sort of interaction that's going on. Here's the breakdown:

There are three vocabularies: Moderation, Website sections, and Right Sidebar

Moderation- two terms (moderated or unmoderated)
Website sections- multiple terms, no ability to add terms
Right Sidebar- multiple terms, ability to add terms

We're using your module to hide the "Moderation" vocab from page edit / creation forms, because only the administrator can change a page's moderation status, although people who aren't moderators can create pages.

However, if we apply your module (as far as I can tell) the following behavior occurs (see screenshot):

1. All un-required taxonomies are removed from the edit page
2. All required taxonomies show up on the page but have no options to select
3. But if a user is granted the "administer taxonomy" permission under the Taxonomy module, everything works perfectly as it should. Except now they can delete vocabularies, etc.

Here are the other modules that we're using that are taxonomy related:

1. Taxonomy Access Control
2. Taxonomy Other
3. Context taxonomy (sub-module of Context)
4. GMap Taxonomy (sub-module of GMap)

Thanks for the fast response!

jcisio’s picture

Ok, I see. Now you need to go to each vocabulary edit page, and edit the permission for each role!

jgarbe’s picture

Yep, did that too. We set them to "edit and view" for the content types they effect (picture attached) and it's the same behavior. I also thought perhaps this module required the administer taxonomy permission enabled, then fine-grained it through those controls, but that didn't seem to be the case.

One thing that may be strange is that we have the "User Permissions" module installed, which creates a role for each person and manages it behind the scenes. The user in question that best exhibits our problem is a Basic Editor, and is user 21. Both do not have the "administer taxonomy" permission checked, and the behavior exhibits.

jcisio’s picture

Priority: Critical » Normal

Vocabperms does not remove terms from a list. In your screenshot, the vocabularies were still there, but terms were removed. Could you disable each taxonomy module to check which module is incompatible with vocabperms?

Incompatibility with a contrib module is not critical.

jcisio’s picture

Status: Active » Closed (fixed)

This is an issue of 1.1. Now 1.2 is out, feel free to reopen if it doesn't fix.