<br><br><div><span class="gmail_quote">On 10/22/07, <b class="gmail_sendername">Jeff Schallenberg</b> <<a href="mailto:schallenberg.jeff@gmail.com">schallenberg.jeff@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10/22/07, <b class="gmail_sendername">Ben Wilson</b> <<a href="mailto:dausha@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">dausha@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;">
Have one group that is not read protected, perhaps Main, which is the<br>default group. All the pages you want public are placed there. All<br>other pages are not in group Main. Set the read permissions for Main<br>to "nopass," which should make that group visible to the public.
</blockquote><div><br>Thanks for your quick response, Ben.<br></div><br><div>I follow your recommendation up to a point. But where you lose me is 'Set the read permissions for Main<br>to "nopass,"' - where and how do I set read permissions for the Main group of pages? If that is covered in the docs, just point me there :-)
</div></div></blockquote><div><br>Start with <a href="http://pmwiki.org/wiki/PmWiki/Passwords">http://pmwiki.org/wiki/PmWiki/Passwords</a>. Maybe spend a little more time poking around <a href="http://pmwiki.org/wiki/PmWiki/DocumentationIndex">
http://pmwiki.org/wiki/PmWiki/DocumentationIndex</a><br><br>Note that with many skins, you'll need to set the read-attribute to nopass for the Site wikigroup, too, as that will be the default source of important pages that are common to all areas.
<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><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
For the "private" section, just use one of the like-cms recipes that
<br>explains how to use the PageActions page in a fashion similar to what<br>you seek.</blockquote><div><br><br></div>There, you've lost me completely. What is a recipe, what is like-cms, what is PageActions? I said I was a Newbie :-)
</div></blockquote><div><br>Site/PageActions is the page that contributes that row of "view | edit | history | upload" etc links to your pages.<br><br></div>A CMS is a Content Management System, and in wiki-speak (and possibly over-generalizing), it's a term used to distinguish a wiki like yours, which is intended for a limited group of users, from the "typical", public-contributions wiki -- such as wikipedia -- which most associate with the term.
<br><br>A "recipe" is a page in the "Cookbook", and can either provide an add-on or tips and discussion of advanced use of PmWiki's built-in functionality. Look at <a href="http://www.pmwiki.org/wiki/Cookbook/Cookbook">
http://www.pmwiki.org/wiki/Cookbook/Cookbook</a>, and read the first paragraph; follow the link to . Return to <a href="http://www.pmwiki.org/wiki/Cookbook/Cookbook">http://www.pmwiki.org/wiki/Cookbook/Cookbook</a> and see its Table of Contents -- the second item on that list is "Content Management System Add-Ons" -- you may want to use the information under that topic for guidelines to your own setup, or you may want to actually install recipes or follow detailed instructions.
<br><br>I find that you can accomplish the kinds of things that are discussed in the CMS-like recipes just by using conditional statements to determine what's visible to under what circumstances. The topic of Conditional Markup is found in the Intermediate topics section of the Documentation Index, and the Conditional Markup page has a link to some advanced usage information in the Cookbook as well.
<br></div>