On Thu, Mar 7, 2013 at 2:29 PM, John Bowling <[email protected]> wrote: > I have a site where I need to block read access to eveyone I have not given > the password to. Having username/password protection is to much. It's only > to protect possible contact information on a calendar. > > I have default passwords in local/config.php and have added (and later > removed) ?action=attr to the group for the pages I want protected. What I > ended up with was the protection over the entire site. > > The read password must be entered before the list of group/pages is shown. > I have since used ?action=attr everywhere I had it, and set all passwords to > clear. It still wants the read password on first site entry. > > To revert back to normal access, I removed all passwords from config.php, > ftp, re-opened the site (still needed a password?) and then placed admin and > edit back in, ftp, and this time it it is back to normal operation. > > But still no effective page read protection. > PmWiki version is 2.2.48
Not *exactly* sure I understand what you want, but if you want to set permissions for an entire group, you need a page Group.GroupAttributes, and set the attributes on that: http://www.example.com/wiki/Calendar.GroupAttributes?action=attr Set the read password to what you'd like, and it will be used across the Calendar group. (Again, assuming that's what you want.) If you want some pages in the Calendar group readable, I *think* you can set attributes for those individual pages and that will override what is set in Calendar.GroupAttributes. If you bring up SiteAdmin.AuthList, you can see the setting for all the pages in the wiki. _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
