"Cornelis J. de Brabander" wrote:
Hi Tres,
[snip]
At a guess, the folder that you clone has local roles attached? I think you would be best off to just force the ownership yourself after the clone:
Bull's eye. But why? Is there any reasoning why the owner role can only be set on a object when it has no other local roles. After all the the creator conceptually stays the owner, whether the object has other local roles or not. Furthermore, is there a place where these changes are documented, for without that simply upgrading within version 2.x.x becomes a hazardous adventure.
It looks like a side effect of fixing another problem: [/home/tres/Zope2/lib/python/OFS] $ cvs log ObjectManager.py ... (tags snipped ) keyword substitution: kv total revisions: 83; selected revisions: 83 description: ---------------------------- revision 1.83 date: 2000/02/17 19:32:21; author: jim; state: Exp; lines: +8 -2 FTP listings are now sorted. Yee ha! ---------------------------- revision 1.82 date: 1999/11/04 19:34:20; author: brian; state: Exp; lines: +10 -7 Fixed a bug that caused _setObject to overwrite the Owner local role whenever an object was moved or renamed. It now only tries to set the Owner role if the current local roles are None (which should only be the case for a new object). In all other cases (moves, copies, renames) the existing local roles will be preserved and the 'Owner' role is not updated.
<dtml-let username="AUTHENTICATED_USER.getUserName()"> <dtml-call "manage_setLocalRoles( username, [ 'Owner' ] )"> </dtml-let>
In the meantime I will follow your suggestion and thank you very much for your helpful response.
Glad it helped! Tres. -- ========================================================= Tres Seaver tseaver@palladion.com 713-523-6582 Palladion Software http://www.palladion.com