On 4/3/06, <b class="gmail_sendername">Allister Jenks</b> <<a href="mailto:arj@zkarj.co.nz">arj@zkarj.co.nz</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;">
<div style="direction: ltr;"><span class="q">On 4/3/06, <b class="gmail_sendername">OBUTEX / Hladůvka</b> <<a href="mailto:admin@obutex.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">admin@obutex.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;">
try<br>Site/GroupAttributes?action=attr</blockquote><div><br></div></div></span></div><div style="direction: ltr;">I've done that already. My point is which pages do I need to unprotect (allow read) to allow the site to work?
</div></blockquote><div><br>
One reason this is missing from the documentation is that there is so
much variation, from skin-to-skin, in what pages exist (and what their
names are).<br>
<br>
Most pages in Site need to be read-able by anyone who's permitted to
view the site. It's probably quicker to read-protect the few that
*do not* need to be available for reading. This is one reason I
typically create an "Admin" group on a new wiki, for what that's worth
- giving me a group that's 'behind the scenes' that I *can* make
completely read-protected.<br>
</div><br></div><br>