[pmwiki-users] PmWiki Magazine proposed Submission/Approval Process

marc gmane at auxbuss.com
Mon Oct 2 08:26:12 CDT 2006

Patrick R. Michaud said...

To throw in my 2c...

> I don't think of permission levels as having an intrinsic "order"
> to them as implied here, nor does PmWiki implement them that way.

I concur.
> Also, "draft" doesn't sound to me like a separate permission level,
> if we need something like this, then it likely will be handled 
> in terms of edit permissions on the "-Draft" pages.  But I'm
> still mulling this over (and PmWikiPhilosophy #3 applies here).

Read protecting a draft page, where the live page has global read 
access, would be very useful to me. So, being able to assign permissions 
to a page's draft, before it exists, would be useful - perhaps 
defaulting to the page's edit permissions.
> Essentially, PmWiki's core permission levels will be read, edit, 
> insert (comment), upload, attr, and admin.  
>   - anyone with admin permission can do anything
>   - if a page doesn't have an edit password, it uses the read password
>   - if a page doesn't have an insert password, it uses the edit password
>   - if a page doesn't have an attr password, it uses the edit password
> It might look to many that this has "insert" and "edit" backwards --
> i.e., that "edit should be a higher level than insert".  But I think
> this is contrary to what authors will expect.  If as a page author
> I put an edit password on a page, I don't expect people to be able
> to later sneak content into the page by using ?action=insert or 
> ?action=comment.

$EnableSneak = 1 :-)


More information about the pmwiki-users mailing list