Bug #94288
closed
Extension Manager throws InvalidArgumentException exception since v10.4.16
0%
Description
Hi,
I'm using v10 LTS in non-composer mode. Since v10.4.16 the extension manager in the backend is inaccessible.
It throws the following exception:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1442236317: MenuItem "" is not valid | InvalidArgumentException thrown in file /var/www/[REDACTED]/typo3_src-10.4.17/typo3/sysext/backend/Classes/Template/Components/Menu/Menu.php in line 92. Requested URL: https://[REDACTED]/typo3/index.php?route=%%2Fmodule%%2Ftools%%2FExtensionmanagerExtensionmanager&token=--AnonymizedToken--
I had ignored this problem so far because I had only updated a test installation. Today, I have investigated the problem further, because it was not fixed in 10.4.17 and I was intending to update my production installation.
I was able to fix the problem; see the attached patch. It seems the "translate" function does not correctly translate "extensionComposerStatus", even though an appropriate entry exists in locallang.xlf.
(After updating my production installation, I encountered the same problem and therefore applied my patch.)
Best regards
Files
Updated by Oliver Bartsch over 3 years ago
Hi, thanks for your report. Unfortunately, I'm not able to reproduce this in any of the mentioned versions. The referenced label exists, see https://github.com/TYPO3/TYPO3.CMS/blob/ce34dbd7af84615c976078542a114b80fd8b0508/typo3/sysext/extensionmanager/Resources/Private/Language/locallang.xlf#L24.
Even if switching to a language, which does not yet define this key (e.g. german), the fallback to the default works as expected.
Obvious question, but did you already clear all caches?
Best, Oli.
Updated by Oliver Bartsch over 3 years ago
- Status changed from New to Closed
Author responded me by mail:
Clearing the cache did indeed fix the issue. I could have sworn that I cleared it at least once between the updates...
Therefore, closing this one.