It didn't make it unfortunately (not enough time). It should be a nice and simple exercise if someone wants to get into eZ publish development though..
We needed this feature, and implemented is as an action.
if ($http->hasPostVariable("ActionSwitchOwner")) {
// Fetch the ID of the group to change ownership to
$groupID = eZHTTPTool::variable('group');
// Create database connection
$db =& eZDB::instance();
// Execute query
$db->query( "UPDATE ezcontentobject SET owner_id='$groupID' WHERE id='$objectID'" );
}
Who knows, I might do that later. But we don't have much use for a gui at the moment, and we are under a tight deadline, so it's not my highest priority. :)
Well, changing the owner shouldn't be granted to every user able to modify the content.
However, that shouldn't be too complicated to test if the user has the right to access the extension "owner/set" from the content edit page and decide to display or not the drop down.
The idea of a separated page to select the user was so it can be extended easily (eg display the users grouped by usergroups, limit the user displayed to a subset...).