When the module is installed, users have to have the "Administer forums" permission in order to see the forum containers in the category list when they go to create a new forum topic. For example, I have a container called "Administrators and Moderators Only" and two forums within called "Help" and "Important Updates." I also have a container called "Web Site" which contains another "Help" forum. So, when a moderator (who does not have administer forums permission) goes to create a new topic, the drop-down category list says:
-Help
-Important Updates
-HelpUnder forum access, I have designated that Administrators and Moderators have access to view the containers as well as view the forums, post in the forums, edit posts, and delete posts.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | forum_access.20070617.patch | 1.14 KB | salvis |
Comments
Comment #1
wim leersI faced the same problem. But I'm not sure if this is by design or not.
Nevertheless, taxonomy_access may be what you need. From http://www.lullabot.com/articles/private_forums_in_drupal_forum_access_v...
Not to mention the finer-grained permissions you get there (which is why I said if I didn't know if this was by design or not).
Comment #2
salvisThis is a design glitch. The containers allow you to assign view permissions only. The attached patch adds the post permissions column to the Edit container form, and if you give post permission, then the container will show up in the list.
Of course you cannot actually post to any container — that's why the post / update / delete columns were removed — but it seems reasonable to use the native mechanism to control visibility of the containers in the forum list, rather than trying to force them to appear based on the visibility of their children.
Comment #3
salvisComment #4
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.