96766[BUGFIX] Keep creation date when moving or renaming a file
Commit message
Review
-
Code review CR +2 Done
- Benni Mack +2
- Markus Klein +1
- Simon Schaufelberger +1
-
Verified V +2 Done
- Benni Mack +2
- Markus Klein +1
- Simon Schaufelberger +1
- core-ci +1 CI
Issues 1
Files 3
Review log 1113
-
Georg Ringer uploaded patch set 1 10/16/26, 17:12
-
Georg Ringer commented on patch set 1 10/16/26, 17:13
This change is ready for review. -
core-ci voted on patch set 1 V +1 10/16/26, 17:20 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/111386
-
Markus Klein commented on patch set 1 10/16/26, 19:52
Actually not sure how to deal with this. changing the creation date when content is modified? does not seem right. But depending on the underlying driver the ctime might change if we move between drivers? (local to remote) -
Benni Mack commented on patch set 1 10/31/26, 20:03
similr to this one? https://review.typo3.org/c/Packages/TYPO3.CMS/+/97056 -
Georg Ringer uploaded patch set 2
V +111/03/26, 19:36 -
Georg Ringer commented on patch set 2 11/03/26, 19:37
Reply
Replacing or changing a file's content still updates the creation date as before; this patch only covers move and rename, so that would be a separate issue. Moving between storages is covered by a new test in patch set 2 (it fails without the change): the stored creation date is kept, the target driver's ctime is not used. -
core-ci voted on patch set 2 V +1 11/03/26, 19:44 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/113212
-
Benni Mack voted on patch set 2 CR +1 V +1 11/04/26, 08:31
-
Markus Klein voted on patch set 2 CR +1 V +1 11/04/26, 11:38
-
Simon Schaufelberger voted on patch set 2 CR +1 V +1 11/06/26, 00:53
-
Benni Mack voted on patch set 2 CR +2 V +2 11/19/26, 09:56
-
Benni Mack merged patch set 3 11/19/26, 09:56