[ewiki] auth plugins: new page access (was Re: Re: auth_perm_unix:new pages access)

I've snipped down the message below just a bit because I haven't looked
at the auth_unix_perm plugin.  I have however had continuing problems
with creating pages in the liveuser_auth plugins and wanted to comment. 
Creating pages is one of the most difficult problems I've had in
creating and maintaining these plugins.  Currently my plugins regard a
page as new if:

* the ["id"] is present in $data
* the ["content"] is not
* it is not a page plugin

this test is actually based on a rejected suggestion that $data be
passed as complete or not at all, but none of the plugins I've looked at
pass $data["id"] without $data["content"].

If the other plugins are having similar problems maybe it is time to add
a "create" action(probably "binary-create" too) that would check for the
existance of the page in the ewiki_page() function just as the AUTO_EDIT
check does presently and sets the action to "create."  This would also
allow plugins to change behavior as in an aedit_ plugin to display pages
that the user may want to edit rather than creating a new page.  What do
you think Milky?

As I develop a need for it, my plan is to base the rights for newly
created pages primarily on the user's id.  It would however be possible
for page's rights to be based on their backlinks if that were useful.

Andy

On Mon, 2004-03-01 at 07:34, Mario Salzer wrote:
> > 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.").
> >
> 
> 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
> 
> 
> 
> _________________________________________________
> Scanned on 01 Mar 2004 15:31:54
> Scanning by http://erado.com

Other related posts: