TYPO3 Core

• the \TYPO3\CMS\Workspaces\Hook\DataHandlerHook::processCmdmap() hook triggers the creation of a new version by invoking \TYPO3\CMS\Core\DataHandling\DataHandler::versionizeRecord()
• in turn this calls \TYPO3\CMS\Core\DataHandling\DataHandler::copyRecord_raw()
• which itself calls \TYPO3\CMS\Core\DataHandling\DataHandler::insertNewCopyVersion() which is where "crdate", "cruser_id" and "tstamp" are forcefully set

So the solution is not an easy one, because it means interfering deep down in the DataHandler class, at a point where there's no entry point (hook, event) yet.

As a workaround for now, I have used the processCmdmap_afterFinish to restore the creation user and date information in case of a versioning operation. Not very clean, but functional.

I guess that rather than trying to modify \TYPO3\CMS\Core\DataHandling\DataHandler::insertNewCopyVersion() it might be easier to add some postprocessing to \TYPO3\CMS\Workspaces\Hook\DataHandlerHook::processCmdmap().