Corrupted translation file blocks complete backend
The following error-message is thrown for the backend after switching the BE-Langauage:
Fatal error: Uncaught TYPO3\CMS\Core\Localization\Exception\InvalidXmlFileException: The path provided does not point to existing and accessible well-formed XML file. Reason: Premature end of data in tag xliff line 2 in typo3conf/l10n/de/about/Resources/Private/Language/Modules/de.about.xlf, line 91 in typo3\sysext\core\Classes\Localization\Parser\AbstractXmlParser.php:79 Stack trace: #0 typo3\sysext\core\Classes\Localization\Parser\AbstractXmlParser.php(60): TYPO3\CMS\Core\Localization\Parser\AbstractXmlParser->parseXmlFile() #1 typo3\sysext\core\Classes\Localization\LocalizationFactory.php(111): TYPO3\CMS\Core\Localization\Parser\AbstractXmlParser->getParsedData('...', 'de') #2 typo3\sysext\core\Classes\Localization\LanguageService.php(317): TYPO3\CMS\Core\Localization\Loca in typo3\sysext\core\Classes\Localization\Parser\AbstractXmlParser.php on line 79
While the reason is quite well explained IMHO it's unacceptable that it's blocking the whole backend.
I think there should be a parser and when the result is positive the language is applied, else the default language or even empty labels.
In other words: keep it running as long as possible.
Updated by Georg Ringer over 1 year ago
- Status changed from New to Rejected
Thanks for creating this issue.
I am still closing this issue as a language file will never be created by an editor but either by a developer or imported from a translation server. In both cases the system should fail if there is an issue