TYPO3 Core

If dealing with nested parent-child-structures, it happens that the proper UID of a record (either parent or child) has not been persistend yet and therefore it's only a "NEW..." which will be replaces in a later step during several "remapping" actions.

If copying a page which many sub-pages and sub-records this remap action is processed very late. Results are invalid record relations (like content elements now having duplicated images since the remapping has not updated the real parent pointer yet).