[ewiki] Re: auth_perm_unix: new pages access

> Is there anything like inheritance from one page to a new one in the code, or 
> how is it meant to work? Or am I missing sth obvious? 
>
> Inheriting as described above would seem to me the way to go.

There is no such thing like inheritance, because ewiki (like most other
WikiWare) uses a flat database (a VERY flat one for ewiki). And there is
simply no real sub-page feature or somthing similar. That is why also
meta data (like the auth_perm_unix infos) aren't automatically transfered
to newly generated pages.

> When I (user, ring level=2) put a link to a new page onto a page owned by me, 
> also giving RWX to members of a group I am member of, I cannot follow the 
> link (" You are not authorized to access this page.").
>
> When I check it being admin (ring level=0) the new page has access rights 
> according to EWIKI_PERM_UNIX_UMASK (i.e. 0002), but neither the USER is set 
> to the owner of the page linking it nor is a group specified that has RWX 
> rights. 

ewiki does never know, from which page you came to the current one. That's
why it can't even detect that you wanted the page access rights to be
inherited from the previous one.

Also because of the flat database scheme, there is no relationship between
two pages. If you create a link to a page, that destination page won't
be created automatically. A page first comes into existence, if you press
the [save] button first. All the page ownership and access rights presented
below the initial empty textbox there is purely fictional until then.

#

So it turns out to be yet another bug here, if you cannot create a fresh
page. (I'd guess the fictional "rwxrwxr-x" access rights prevent it
here - there needed to be an exception for non-existent pages, so it
was possible to create them).
That "perm_rights_actions" ought to be that exception... (needs some
investigation)

#

The overall problem with the ewiki authentication framework is, that
it is kept highly optional, and as I personally don't use it, I don't
have an eye on these issues. Also for managing uploaded files and so
on, it was obviously better to have a deeply relational database
structure and no real page names, like CoWiki or other WikiWarez.

However, as Andy put a lot of work in integrating the authentication
and permissions into the right places (yep, search plugins are also
protected) it's only a matter of getting those extension to work
as desired.

mario

Other related posts: