[Setup] Re: Permissions
phil at xfr.co.uk
Tue Jan 3 10:47:05 UTC 2006
Most of my work with Plone involves what are essentially "Zope"
applications in a "Plone/CMS Site", so the border between Plone's
content and the Zope artefacts that make up my application is of
particular interest to me.
FWIW, I use ZPT/ZSQL/Python objects in Plone folders, and implement
workflow on the Plone folders and use the Zope security for the
(non-Plone) folders contents, which works very well.
Raphael Ritz wrote:
> Even if you think it's bad I think there are situations in which
> it is perfectly fine to fall back to Zope's (as opposed to
> CMF/Plone's) security handling.
> I do that (sometimes) with what I call "structural folders".
> By that I mean folders that aren't subject to workflow at all
> and that cannot be created by individual users but
> only by site admins (that know what they are doing)
> when setting up a site to (pre-)define some structure.
> In those cases you may actually want to be able to define
> permissions on instance base - as opposed to type base
> which is what DCWorkflow does.
Does this refer to Plone content, or to other artefacts?
> I know that there are efforts on the way to provide
> a "placeful" workflow for Plone but even when it's
> there it might feel like overkill for some of those
Whether working with current or future workflow, would not the
"Plone-ish" way of doing this be to create a type with a "null" (e.g.
one state, no transitions) workflow?
> Sorry Alan, I just want people to know their options.
I'm not 100% sure whether we are talking about Plone content here, but
we all need to know our options (including the option to shoot ourselves
in the foot!). Since I get so much leverage from using Zope products
which "play nice" with Plone, I think that there is some benefit in
making such options better understood.
Email: phil at xfr.co.uk
PGP Public key: http://www.xfr.co.uk
Voicemail & Facsimile: 07092 070518
"You'll find that one part's sweet and one part's tart:
say where the sweetness and the sourness start."
- Tony Harrison
More information about the Setup