This is not supported by default. Copy is finalized with publish operation, so It should be possible to run after-publish workflow event that redirects user to edit mode after copy, then you can have new node/object ID, etc. You can give a try.
If I was to use a work to throw a user immediately into edit mode after making a copy how would that workflow distinguish between a normal publish object and a fresh copy?
Also any idea's about how to rename or make the copied object easy to identify?
Cheers
www.dbinformatics.com.au
We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.