On Fri, Oct 2, 2009 at 2:25 AM, Hans <[email protected]> wrote: > Friday, October 2, 2009, 7:33:51 AM, Christian Bartolomaeus wrote: > >> My suggestion was to override the global passwords (from config.php) >> in a page customization file (say Main.Test.php for page Main.Test). > > I think it is unwise to set any default password > in a page or group customisation file, because > a page protected in such a way will not be protected if it is for > instance included by another page. > To have proper protection for an individual page its > password attributes need to be set in the page with action=attr, > or for the group in the GroupAttributes page with action=attr. > Do not use a page customization php file for this!
Whoa! This is a bit off-topic but, Hey! This could come in really handy. There have been times when that's *just* what I wanted -- to protect a page itself from being read (or edited) directly, but still allow it to show up in an include. Good to keep in mind. _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
