Cannot create node in taxonoy term if parrent term hasn't checked create permision

This is a follow up to the issue with TAC under drupal 5.1 and mysql 5.0.x

I cannot avoid posting to "Solid" and "Liquid"!
I have unchecked the flags in the Create columns, and checked everything under "List".

Users (belonging to the role I am editing with TAC) can create posts under any term in the vocabulary!
Seems that checking "Create" boxes has no effect.

Anyone can confirm the issue?

Thanks a lot in advance.

I have a same problem: if I uncheck Create checkbox in parrent caterogy, then users see only blank combobox in add node page (although there are checked Create checkboxes for this user).

Is there any solution?

I run Drupal 5.1 and mysql 5.0.x.

why not create multiple taxonomies..or get rid of the offending holding containers? "solid" doesnt provide so much information, does it? especially since this is so granular?

I have the same problem, no terms show up in the Taxonomy window if I want to create a new page and "create" for the partent taxonomy term ist unchecked.
I run Drupal 5.1, PHP 4, MYSQL 4.1.22.
Is there any solution?

A quick reply to #4: solid may seem too generic, but the taxonomy in this post is only an example.

I don't have any "solid" in my own taxonomy, and the module just does not work as it did in drupal-4.7

OK, I will provide details about my needs.

I have one vocabulary with hierarchy and I need for user to choose one term in his scope (it means where he has priviledges).
Structure is following:
-Department IT
--Clients
--Servers
--Mail system
--Others

So I want to have pages in 2nd level and also in 1st level (in Department IT).
And I need to provide privilegdes for managers for Department IT, and for chief of Clients, Servers, ... ONLY to their categories, but not to top level "Department IT".

So, is there any way how to do this?

Drupal Forum seems to behave as expected, but I can't get TAC to work with regular posts.
One tricky solution would be to convert all your posts and taxonomy to forums, where the "parent" (i.e. where you can't post) is the forum container. That's not elegant, and could be a hard work: you have to manually re-create posts, re-create taxonomy and acls.

This is very tricky solution. I don't want ot do it this way. I just need to allow user to add node when he has permision for it, althrough he hasn't create permision of parent term.

I think it looks logical that in company is manager allowed to do anything and employees can do only part but not everything. So in this logic, I have:

Company
-Department1
--Section1.1
--Section1.2
-Department2
--Section2.1
--Section2.2

and I want some user to create nodes only in Section2.1, but not anywhere else (not in Department2, not in Company).

Is there any help for this?

I run Drupal 5.1, mysql5, taxonomy_access 5.x-1.1 and tried 5.x-2.x (everywhere it is the same).

This is very tricky solution. I don't want ot do it this way. I just need to allow user to add node when he has permision for it, althrough he hasn't create permision of parent term.

I think it looks logical that in company is manager allowed to do anything and employees can do only part but not everything. So in this logic, I have:

Company
-Department1
--Section1.1
--Section1.2
-Department2
--Section2.1
--Section2.2

and I want some user to create nodes only in Section2.1, but not anywhere else (not in Department2, not in Company).

Is there any help for this?

I run Drupal 5.1, mysql5, taxonomy_access 5.x-1.1 and tried 5.x-2.x (everywhere it is the same).

I've confirmed that if you don't have create for a term, you won't be able to create in any descendant. I had not been aware of this behavior. Presumably it is a bug, not a feature?

I've been planning to change the mechanism for limiting available terms from hook_db_rewrite_sql (which limits the terms before they are passed to taxonomy module) to hook_form_alter (alter the taxonomy select form after taxonomy is done with it). This would fix the parent problem.