Organic Groups and Category module

Jeremy,

I cannot report this as a bug, because you never said that your Category module could work with the Organic Group module and I know that you are working on a Category_access module.

But, as you are asking on your site for feedback, I would like to report to you (and other readers) what I have found.

Yesterday I have installed Drupal, Category and OG from CVS. No other contrib modules were installed. I have also applied the patch in drupal.org/node/51850.

As expected, the access (by /node/n) to nodes of type category or container is well controlled by OG: a user not in an organic group cannot see a node private to that group.

But when adding or editing other type of node (for example /node/add/story) the author see, in the categories collapsing fieldset, the containers and the full list of categories even if the containers and/or some categories are private to an organic group for which the author has no access.

The only case where it is working is with "freetag" (autocompletion field): the result of the autocompletion only shows categories accessible to the user (controled by OG). This is already very good and can be used :)

Making visible only categories fields (dropdown list or freetag) corresponding to accessible containers seems now an evident feature to request. I don't know what difficulties this imply.

It is more difficult to decide on what to do with non accessible categories in dropdown lists mainly if they are in a hierarchy. When a category is not accessible, should all its sub-categories hidden? If not how to list them properly??

I am looking forward to discovering your category_access solution.

Jean