Features / Usability

> Thanks for both on your response.
>
> I went ahead and tested Colorado's second method which I think is easier and less tedious. Just felt that Gary's method is a bit tedious as you have to set permissions on every wiki page.
>
> Sadly, after trying out Colorado's method...I still could not get it to perform the way I wanted. Maybe I am missing something here....
>
> Below are the steps that I have performed:
> 1. Created a wiki page for each subject, named: Fish, Cat and Dog.
> 2. Created a Group for named: FISH, CAT and DOG. Assign user A & B to group FISH, C to CAT and D to DOG. Users A to D are assigned Editors level of permissions.
> 3. Create a Category for each subject, named: Fish, Cat and Dog.
> 4. Assign Fish, Cat and Dog wiki page object to its respective category.
> 5. Assign permission for Fish category as Anonymous - tiki_p_view_categories and FISH - tiki_p_admin_categories.
> 6. Log out and log in as users A-D to look at the outcomes.
>
> Still users A-D can edit all pages as if there is no control. But non-logged in users works as it only allow viewing.
>
> Colorado, apprecaite your help on this.

I was waiting to here how Colorado manages this, but will reply in the meantime. At my sites (running 1.9.0), assigning a wiki page to a category seems to give the page the same viewing permissions as the other pages in the category, but I don't actually understand why this should be the case. My understanding is that "tiki_p_view_categories" only controls visibility of the category information itself — the tree, links, etc. — and it doesn't address the accessibility of the categorized objects themselves. In fact, wiki pages within a category can have different viewing permissions, so which ones are supposed to be assigned automatically via category assignment? There's no interface to control this, as far as I can tell.

For example, I have a category Bugs, and generally this is private content. Bugs pages are visible only to the Elmer user group. I found that categorizing a new page in the Bugs group does in fact make it inaccessible to anonymous users, even if no specific perms are assigned to it, if "Assign permissions automatically" is checked on the admin categories page. Is this an undocumented feature? On the other hand, there are other objects at the site in the Bugs category, such as a Directory category, and anonymous users can view these. Therefore, I think we can't assume that viewing permissions are inherited automatically based on category assignment.

I'd like to do some more tests, and would like to hear about other people's experiences with categorizes and permissions. But in the meantime, I'd recommend assigning permissions via single objects or wiki structures.

-- Gary