One option that you have is to protect the View object that you use to
do the renaming, unless you're using views that are provided by
someone/something else (the default Zope UI, etc). You can protect
your 'rename' view and inside of it use
'zope.security.proxy.removeSecurityProxy' to get access t
Hi Stephan,
Actually, my users don't have that role(permission?), because I got
the impression that having it would give them access to a number of
things I don't want them to see, such as the metadata and introspector
tabs. Is that strictly required for any kind of
renaming/copying/pasting? Is th
Thanks for the response.
They are local users, and it's specific to every container type that
I've created, I haven't had the chance to test with regular folders.
The containers that I have inherit from OrderedContainer or
BTreeContainer, and tend to be fairly minor customizations, simply
adding a
On Wednesday 30 November 2005 16:16, Alec Munro wrote:
> My users are unable to rename things, seemingly everywhere. They can
> add, remove, but not rename, or cut/copy. I'm not sure how to set the
> permission for this.
I think we need some more specific background information to help you out
he
As far as I can tell they do, the objects containers primary interface
inherits from IContainer, and they have set_schema on that interface.
Additionally, they can add new containers, and their contents, but
still be unable to rename the contents.
Thanks,
Alec
On 12/1/05, Chris Withers <[EMAIL P
Alec Munro wrote:
My users are unable to rename things, seemingly everywhere. They can
add, remove, but not rename, or cut/copy. I'm not sure how to set the
permission for this.
Do they have the necessary permissions on the objects container rather
than the object itself?
cheers,
Chris
--
Hi List,
My users are unable to rename things, seemingly everywhere. They can
add, remove, but not rename, or cut/copy. I'm not sure how to set the
permission for this.
Thanks,
Alec
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org
