copy/paste does not change ownership

Bug #142814 reported by geoffd
2
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Medium
Unassigned

Bug Description

When you copy an object owned by someone else and then paste it, the new object is still owned by the original object's owner rather than by the user who pasted the object. I think the easiest way to fix this is by modifying manage_afterClone in SimpleItem.py so that it calls changeOwnership on the new object and adds the Owner local role for the currently authenticated member to the object.

Tags: bug zope
Revision history for this message
Andreas Jung (ajung) wrote :

I think there are two usecases:

1) You are logged in as Manager to perform some copy operations
   for maintenance. Then the required behaviour is to do not
   change the ownership

2) You are logged as "normal" (but not as Manager) and you
   have the permission to copy files around. In this case
   your usecase might be wishful to be supported.

But I have no idea to bring these policies together without
breaking the existing behaviour.

Revision history for this message
Tres Seaver (tseaver) wrote :

On any modern Zope, the call to the container's '_setObject' method
inside 'manage_pasteObjects' leaves the 'set_owner' flag True (the default),
which results in having the executable ownership fixed up.

Changed in zope2:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.