Replies: 4 comments 2 replies
-
Hi @CDRO thanks for the report. I will have to check the specific project for the structure and come back to update what needs to be done :) |
Beta Was this translation helpful? Give feedback.
-
Thanks for considering, if I get the time to find the related information I'll try to help you with it and/or propose a patch to support this as well, this would probably benefit quite some projects as I don't think TYPO3 is the only framework or CMS having this kind of specifcs. |
Beta Was this translation helpful? Give feedback.
-
I just did some investigation. I don't know where normally the source is placed, maybe you can give me a hint here. But I think the problem is placed here: So the only question remains where for typo3 the typical source is found.
|
Beta Was this translation helpful? Give feedback.
-
Thanks for your quick investigation! Usually, TYPO3 will put it's packages (aka extensions) as follows:
The variable {
"extra": {
"typo3/cms": {
"web-dir": "public/"
}
}
} I guess Drupal has something similar, where the public modules are placed inside I've seen that symfony allows you to configure to have the public folder (as well as the I hope this helps! |
Beta Was this translation helpful? Give feedback.
-
In some cases, as in TYPO3, packages are not always installed in
vendor/<vendor>/<package>
as it would be expected by the plugin, in this case an error appears quickly and no scan is done.To test this, simply execute this and run
composer-unused.phar
in the directory you just created:As TYPO3 will probably shift all packages to the vendor folder in version 12 or 13 anyway, this might not be a problem in the future anymore, but regarding one of the the goals (helping remove packages before you upgrade, so you don't keep it around for nothing), this would probably be a game changer for the TYPO3 dev community, if it would work as expected 💪
Beta Was this translation helpful? Give feedback.
All reactions