On 1/29/06, <b class="gmail_sendername">Tegan Dowling</b> <<a href="mailto:tmdowling@gmail.com">tmdowling@gmail.com</a>> wrote:<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>On 1/29/06, <b class="gmail_sendername">Ryan D'Baisse</b> <<a href="mailto:ryan.dbaisse@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
ryan.dbaisse@gmail.com</a>> wrote:<span class="e" id="q_109170c4c2448cd0_1"><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;">
Am I just not getting something? I was under the impression that the<br>default passwords had a hierarchy effect. I thought, they worked in<br>the following order...<br><br> READ: Visitors can read content<br> EDIT: Visitors can read and edit content
<br> UPLOAD: Visitors can read, edit, and upload content<br> ATTR: Visitors can read, edit, upload, and change attributes<br> ADMIN: The equivalent of a "PmGod" ... can do anything<br><br>Is this not the case?
<br><br>For this reason, I had the following passwords<br><br> READ: password01<br> EDIT: password02<br> UPLOAD: password02<br> ATTR: password03<br> ADMIN: password03<br><br>Unfortunately, this had problems:
<br><br> 1. Visitors logging in with "password01" could read and edit<br>pages... not good; and,<br><br> 2. Visitors could not log in with "password02" at all (regardless of<br>how many times I reset it).
<br><br>What am I missing? I would like to have the following...<br><br> A. Visitors logging in with "password01" should be able to read the<br>site but not edit or alter anything;<br><br> B. Visitors logging in with "password02" should be able to read,
<br>edit, and upload; and,<br><br> C. Visitors logging in with "password03" should be able to do<br>anything with the site.<br><br>Is this possible? If so, how do I accomplish this?</blockquote></div></span>
</div></blockquote><div><br>
</div>You may have an error somewhere, since as you have it, password01 should definitely not be enabling users to edit.<br>
<br>
But you also have a misunderstanding: if you want password02 to enable
editing of pages that are read-protected, you also have to also make
password02 a read-password.<br>
<br>
Maybe you should review <a href="http://www.pmwiki.org/wiki/PmWiki/PasswordsAdmin" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.pmwiki.org/wiki/PmWiki/PasswordsAdmin</a>?<span class="e" id="q_109170c4c2448cd0_1">
<br>
</span><br>
------------<br>
<br>
(Sorry about the top-post, previously - <span style="font-style: italic;">stupid </span>computers.)<br>
<br>
We have something like this in our config.php files:<br>
<br>
// Passwords<br>
$PmWikiAdminPassword = crypt('password03');<br>
$PmWikiReadEditUploadPassword = crypt('password02');<br>
$DefaultPasswords['admin'] = $PmWikiAdminPassword;<br>
$DefaultPasswords['read'] =
array(crypt('password01'),
$PmWikiReadEditUploadPassword); <br>
$DefaultPasswords['attr'] = $PmWikiAdminPassword;<br>
$DefaultPasswords['edit'] = $PmWikiReadEditUploadPassword;<br>
<br>
// Uploads<br>
<br>
$EnableUpload = 1;<br>
$UploadUrlFmt = $ScriptUrl.'/uploads';<br>
$DefaultPasswords['upload'] = $PmWikiReadEditUploadPassword;<br>
<br>
</div><br>