[pmwiki-users] 2.2 Series & Blog/comments

[Patrick R. Michaud]

On Sat, Sep 23, 2006 at 01:22:58PM -0500, George wrote:
> On Sat, 23 Sep 2006 13:15:18 -0500, Patrick R. Michaud  
> <pmichaud at pobox.com> wrote:
> 
> >On Sat, Sep 23, 2006 at 01:04:36PM -0500, George wrote:
> >>On Sat, 23 Sep 2006 12:40:36 -0500, Patrick R. Michaud
> >><pmichaud at pobox.com> wrote:
> >>
> >>>The ability to add content will have a separate authorization level
> >>>from the ability to edit.  It will default to be the same authorization
> >>>as editing, so that edit passwords continue to restrict the ability
> >>>to change content, but the authorization can be set independently
> >>>to say "I'm allowing people to add content but not edit it."
> >>
> >>Maybe this should be extended to allow user-definable authorizations...
> >
> >What do you mean by the word "user" here -- do you mean "author",
> >"administrator", "visitor", or ... ?
> 
> Administrator.  Currently, there are authorizations for view, edit,  
> delete, attribute, and upload.

Oh.  Administrators can already define custom authorization levels.
(that's been in PmWiki since v0.3 :-).

The base pmwiki.php script defines only 'read', 'edit', and 'attr'
authorization levels.  If scripts/upload.php is load, then that
adds an 'upload' level.

The PmWiki core doesn't define a 'delete' authorization level,
but it can be added by a recipe or local customization.

Essentially, for an administrator or recipe to add a new 
'xyz' authorization level, they simply do:

    $DefaultPasswords['xyz'] = crypt('xyzpassword');
    $PageAttributes['passwdxyz'] = 'Set new xyz password:';

This tells PmWiki there's an 'xyz' authorization level, and
to display a field for it in the ?action=attr form.

This is also described at the bottom of the PasswordsAdmin
page (http://www.pmwiki.org/wiki/PmWiki/PasswordsAdmin).

Is that what you were looking for...?

Pm