<div class="gmail_quote"><div class="Ih2E3d">On Thu, Jan 22, 2009 at 10:44 AM, Patrick R. Michaud <span dir="ltr"><<a href="mailto:pmichaud@pobox.com" target="_blank">pmichaud@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
SiteAdmin/ is for things that are definitely not user-visible,<br>
such as passwords. There aren't many things that fall into this<br>
category.<br>
<br>
Site/ is for things that are shared across the entire site,<br>
such as edit forms, page not found messages, search pages,<br>
pagelist templates, etc. These pages must be readable by<br>
non-admins, otherwise non-admins cannot edit, perform searches,<br>
etc.</blockquote></div><div><br> The
cmsmode recipe uses some simple code to prevent users from accessing
such pages directly, while still allowing read access for includes and
searchs. Is it foreseeable that such a page attribute could be added to
allow an easier way for admins to do this kind of organizing?<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">This is why we have per-page passwords and authorization.<br>
<div>
<br>
</div></div><div class="Ih2E3d">No, it's exactly what categories are intended to do. If we<br>
provide an easy way for admins to enable/disable site and recipe<br>
documentation, then I think it all just works out.<br>
<font color="#888888"><br>
Pm</font></div></blockquote><div><br>I
agree. An easy enable/disable would alleviate all of my concerns. More
than anything, I simply have a different view of organization, which I
always implement anyway. My main concern was that I should be able to
exercise that control post-implementation of the handy new features
proposed, because the future of PmWiki is bright indeed!<br>
</div></div><br>Mike