TYPO3 v15 dev-main snapshot ()

2026-08-10 22:31:09 +02:00
commit af8cc155b5
6818 changed files with 642608 additions and 0 deletions
@@ -0,0 +1,65 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-55419:
+
+============================================================
+Deprecation: #55419 - Streamline file conflict mode handling
+============================================================
+
+See :issue:`55419`
+
+
+Description
+===========
+
+Conflicts in file names and folder names when uploading new files or creating new folders are now handled
+uniformly with constants within the core. Therefore a new enumeration has been introduced to provide the available
+values: `\TYPO3\CMS\Core\Resource\DuplicationBehavior`.
+
+Provided constants are:
+
+* `DuplicationBehavior::CANCEL`
+* `DuplicationBehavior::REPLACE`
+* `DuplicationBehavior::RENAME`
+
+Before this change there were two sets of strings used to define the behavior upon conflicts.
+
+* Set1: `cancel`, `replace` and `changeName`
+* Set2: `cancel`, `overrideExistingFile` and `renameNewFile`
+
+As they are redundant they are now represented by a new set of constants:
+
+* `CANCEL`, `REPLACE` and `RENAME`
+
+All usages of strings of the former sets have been replaced with their counterparts from the new set. In the enumeration
+the former values have been mapped to the new values and marked for deprecation.
+
+
+Impact
+======
+
+Using `changeName`, `overrideExistingFile` or `renameNewFile` for file conflict handling will result in a deprecation log entry.
+
+
+Affected Installations
+======================
+
+All third party code that calls one of the listed methods with `$conflictMode` either set to `changeName`, `overrideExistingFile` or `renameNewFile`.
+
+
+Migration
+=========
+
+Use the provided enumeration `\TYPO3\CMS\Core\Resource\DuplicationBehavior` instead.
+
+
+Example
+=======
+
+.. code-block:: php
+
+   $resourceStorage->copyFile($file, $targetFolder, 'target-file-name', DuplicationBehavior::RENAME);
+
+
+.. index:: FAL, PHP-API, Backend