Re: [Zope-dev] manage_addZClass* permission question

2003-05-30 Thread Shane Hathaway
Jamie Heilman wrote: Shane Hathaway wrote: It is. Older Zope code uses the manage_ prefix to require the Manager role by default. Needless to say, that strategy did not cope well with later enhancements to Zope. OK. So what about the stuff in ZClasses/__init__.py, pure fluf? After yesterday

Re: [Zope-dev] manage_addZClass* permission question

2003-05-29 Thread Jamie Heilman
Shane Hathaway wrote: > It is. Older Zope code uses the manage_ prefix to require the Manager > role by default. Needless to say, that strategy did not cope well with > later enhancements to Zope. OK. So what about the stuff in ZClasses/__init__.py, pure fluf? After yesterdays App.Permission

Re: [Zope-dev] manage_addZClass* permission question

2003-05-29 Thread Shane Hathaway
Jamie Heilman wrote: I can't fathom the ZClass code. Can somebody tell me if manage_addZClass, manage_addZClassForm, and manage_subclassableClassNames are supposed to be protected by the 'Add Zope Class' permission, or if the code in ZClasses/__init__.py is pure fluf? That permission never shows

[Zope-dev] manage_addZClass* permission question

2003-05-28 Thread Jamie Heilman
I can't fathom the ZClass code. Can somebody tell me if manage_addZClass, manage_addZClassForm, and manage_subclassableClassNames are supposed to be protected by the 'Add Zope Class' permission, or if the code in ZClasses/__init__.py is pure fluf? That permission never shows up in any folder's se