[pmwiki-users] pmwiki-2.0.beta50 released

[Patrick R. Michaud]

On Thu, Jul 21, 2005 at 06:20:35PM +0200, Joachim Durchholz wrote:
> I just noted that PmWiki uses these settings:
>   $HandleAuth['browse']       == 'read'
>   $HandleAuth['source']       == 'read'
>   $HandleAuth['edit']         == 'edit'
>   $HandleAuth['attr']         == 'attr'
>   $HandleAuth['postattr']     == 'attr'
>   $HandleAuth['approveurls']  == 'edit'
>   $HandleAuth['approvesites'] == 'edit'
> 
> This seems to mean that _actions_ are separate (and use different 
> terminology than) _authorisation levels_. An _authorisation level_ just 
> seems to be a group of things that the admin wants to authorise as a unit.
> 
> Is that correct?

Yes (it's always been this way).

> Are the authorisation level values visible to end users? If so: can I 
> change the texts (say, "schreiben" statt "edit" for my German visitors)?

One can customize the prompts in the ?action=attr form;
beyond that there are a few places that these values cannot
yet be internationalized.

> >2. Passwords can now "cascade" -- that is, if a page sets a 
> >'read' password but not an 'edit' password, then the read 
> >password is also used as the edit password. Similarly, if a 
> >page sets an 'edit' password but not an 'attr' password, 
> >then the edit password is also used as the attr password.
> 
> Is that configurable?
> I.e. could I switch off parts of the cascade, or add a new intermediate 
> authorisation level that becomes part of the cascade?

Yes, it's configurable via the $AuthCascade array.

Pm