TYPO3 Exception 1338996122

Note

Below, the TYPO3 community may have provided additional information or solutions for this exception. However, these may or may not apply to your particular case. If you can provide more information, you should come back here and add your experience and solution steps to this issue once you have resolved it.

General TYPO3 troubleshooting tips can be found in the section “Troubleshooting” of the menu, and live support is available in the TYPO3 Slack channel #typo3-cms.

To add your experience, click “Edit on GitHub” above and follow the “Edit on GitHub” workflow. Also check out our tip on Coding Style and reST.

Package “…” is already registered.

Accidental double install

When installing extensions twice (for example by inadvertently using a copied folder) this exception might occur. To get rid of it again, remove the extension from the typo3conf/PackageStates.php manually.

Duplicate composer.json package name:

Another package uses the same name in its composer.json file. Even if composer mode is not enabled and the composer file is just copied, it will cause the TYPO3 Package Manager to throw the correct exception. This may happen if you copy an extension, e.g. from typo3conf/ext/acme to typo3conf/ext/acme.old. Just search the filesystem for any other instances of the same package name and rename one of them.

Warning

Composer files allow aliases for package names in the replace section, catch them as well.