Bug #60864
closed
EXT with composer.json and Extension-Keys (just directory Extension-Key does not work)
0%
Description
If I have an ext with a composer.json then the composer name is used for the extension key which is OK.
However, the extension key that uses the directory does not work then.
This is a problem for multiple reasons:
1.) Extension should also support older versions e.g. 6.1 there were no PackageStates.php
So I would have to make sure I use the corresponding name depending on the typo3 Version which is just "annoying"
2.) The Extension could already have been installed under the old name, so basically the extension is there but it uses the old key.
Same goes for e.g. typo3 upgrade where the old name was noted.
So I actually would have to make sure to retrieve the correct key depending on which ext key is loaded.
If there is a composer.json both keys (the directory based and the composer based) should work.
Updated by Andreas Allacher over 10 years ago
The static includes in typoscript template also have the same issue.
If I install an extension with a composer name based key, the composer name based key would be in the static include - which would mean I have to re-add static includes that might have existed under the old name. However, that is not that important as elsewhere (e.g. if I use files in typoscript or siteRelPath etc.)
I am not sure (have not tested and yet and I don't have a typo3 installation currently accessible to test) if it might also have cause troubles with dependencies in ext_emconf.php
Updated by Andreas Allacher over 10 years ago
The same problem also exists with the extension key used for the extension configuration via the extension manager (might be required to add the configuration for both keys)
Updated by Andreas Allacher about 10 years ago
I just noticed that I can actually achieve this by defining the non composer name via replace.
At least it works for EXT: references and extRelPath etc.
It does not work for the configuration however but there I can just clone the other configuration (directly in the ext_localconf.php if necessary).
Updated by Andreas Allacher about 10 years ago
Can be closed. I just noticed that I used the wrong type.
If I use "type": "typo3-cms-extension" then it will be recognized as extension and only use the extension key as previously which also means that the configuration is stored that way.
Updated by Sascha Egerer about 10 years ago
- Status changed from New to Rejected
Closed as requested by Author.