On 10/22/07, <b class="gmail_sendername">Jeff Schallenberg</b> <<a href="mailto:schallenberg.jeff@gmail.com">schallenberg.jeff@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span class="q">On 10/22/07, <b class="gmail_sendername">Tegan Dowling</b> <<a href="mailto:tmdowling@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">tmdowling@gmail.com</a>> wrote:
</span><span class="q"><div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span></span><div><div><br>(just do it and see)<br></div></div></blockquote></div><br></span>OK, thanks, Tegan! I did it and saw a form. I had no idea what the form was for. I put "@nopass" in the "Read" box, and that seems to work. And then I set an "Edit" password on the
Site.Sidebar page. I hope that will have the effect of preventing the great unwashed public from editing the Sidebar :-)<br><br>As for the cookbook, I have yet to see what it has to do with setting up access to my pages.
<br><br>CMSLike says:<br>"To make PmWiki behave as a CMS, by showing only the actions the current user is allowed to perform."<br><br>My wiki does not use user authorizations - yet. Only passwords.</blockquote>
<div><br>If you have passwords, then a user's permissions are determined by the password(s) that he/she has used in the current browser session. It is NOT necessary to have a user-based authentication system in order to set up a cms-like wiki. This is one reason I suggested that you might use the cms-like recipes as guidelines, rather than taking them literally, and why I said that I use conditional markup (
<a href="http://pmwiki.org/wiki/PmWiki/ConditionalMarkup">http://pmwiki.org/wiki/PmWiki/ConditionalMarkup</a>) to accomplish a cms-like setup, since I almost never set up AuthUser or UserAuth, and instead stick to the native password-based authentication system.
<br><br>For example, on a page named "Pagename", you could have <br><br>(:if auth edit:)<br></div>[[Pagename?action=edit | Edit]]<br>(:ifend:)<br><br>That would say that if, in the current browser session, the user has already employed a password that confers edit permission for the page Pagename, then the user will see an "Edit" link.
<br><br>You can have<br><br>(:if ! enabled AuthPw:)<br>[[Main/HomePage?action=login | Log in]](:if enabled AuthPw:)[[Main/HomePage?action=logout | Log out]](:ifend:)<br><br>which says if I haven't employed a password in this session, show me a login link, but if I have (even if it was a typo and doesn't confer any rights at all), then show me a logout link.
<br></div>