[Zope-CMF] Re: Allowed content types (CMF 1.5 - Roadmap)

[Vincenzo Di Somma]

How will you manage the permissions in the workflow ?
If you have a different permission for each type of content do you have
to update the workflow definition each time you add a new permission ?

 Vincenzo.

On Tue, 2004-03-23 at 10:12, Yvo Schubbe wrote:
> Hi!
> 
> 
> Alexander Limi wrote:
> > On Mon, 15 Mar 2004 17:50:15 +0100, Christian Heimes  
> > <heimes at faho.rwth-aachen.de> wrote:
> >> * The ftis and the product name must be the same for every type so I  
> >> used the fti from process_types().
> >>
> >> * The constructor and the class must differ for each security setting.
> >>
> >> See  
> >> http://cvs.sourceforge.net/viewcvs.py/collective/ATContentTypes/__init__.py?rev=1.1.1.1&view=auto  
> >> for an example.
> > 
> > 
> > I'm not technically up-to-date on what you are discussing, but would 
> > this  also allow you to make certain content types available only to 
> > certain  roles?
> 
> Sorry for repeating myself:
> 
> The answer depends on what you mean by 'content type'. This will not 
> work per Portal Type, just per content class. (In the Types Tool you can 
> define more than one Portal Type per content class.)
> 
> 
> Cheers, Yuppie
> 
> 
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF at zope.org
> http://mail.zope.org/mailman/listinfo/zope-cmf
> 
> See http://collector.zope.org/CMF for bug reports and feature requests
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mail.zope.org/pipermail/zope-cmf/attachments/20040418/f4b36628/attachment.bin