On 4/12/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote: [...] > Administrators often want to restrict browse access to pages > in the Site.* group. The natural (and obvious) approach is > to place a read password on Site.GroupAttributes, but that's > often problematic because some pages in Site.* need read > access in order to work properly. These pages include: > [...] > > So, I'm thinking that perhaps the cleanest approach would be > to add special read passwords (similar to '@nopass') to the above > so that they can be accessed even when the Site group is > read protected. > > Thoughts?
Funny you should mention that. I just deployed a wiki that is private except for Main.*, and had to go to just those pages to @nopass. If I had any influence with the wonderful development effort of PmWiki (waves two pennies seductively) I would suggest @nopass by default for those site pages. :-) In the alternative, could an administrator set up a list of @nopass pages in local/config.php? That could prevent somebody from accidentally restricting critical pages. -- Ben Wilson "Words are the only thing which will last forever" Churchill _______________________________________________ pmwiki-users mailing list [EMAIL PROTECTED] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
