Issue Bug Closed

#72968Missing files during import cause abort

Bernhard Kraft 01/27/16, 14:38 updated 11/06/26, 07:43

Description

When doing an import and some files are really missing in the T3D/XML file this will cause an abort of the import process as an exception gets thrown. This bugfix wraps a “try” block around the failing method of DataHandler. The default behaviour is not influenced as the exception will get thrown again except if the new DataHandler variable “handleCheckValueExceptionsGraciously” is set.

Reviews 1

History 810

  1. Gerrit Code Review pushed patch set 1 for master to change 46265 status New Under Review <span data-processor="relativetime" data-value="2016-01-27T14:52:10+00:00" > 01/27/16, 14:52 </span>

  2. Markus Klein commented <span data-processor="relativetime" data-value="2016-02-12T11:35:17+00:00" > 02/12/16, 11:35 </span>

    How can files be “really missing” in t3d?

  3. Oliver Hader changed Complexity medium Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2017-11-24T22:07:31+00:00" > 11/24/17, 22:07 </span>

  4. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-06T07:43:13+00:00" > 11/06/26, 07:43 </span>

    Closing this issue, as it no longer applies to current TYPO3 versions. The exception came from the legacy file handling of group fields with internal_type=file (DataHandler->alternativeFileName/alternativeFilePath), which was removed in TYPO3 v10.0. Impexp now imports files through FAL. A file missing from the T3D/XML file is logged (“No file found for ID …”) and skipped, records related to it are reported as lost relations, and the rest of the import still runs. The collected errors are reported at the end. A functional test covers this (PagesAndTtContentWithImagesInEmptyDatabaseTest::importPagesAndRelatedTtContentWithMissingImageRemovesSysFileReferenceToo).

    If you think this still needs to be addressed, please comment and we will reopen the issue.