Bug #80578
closed
Install tool's "Check for broken extensions" does not recognize missing SpritManager
Added by Gone With the Wind over 7 years ago.
Updated over 7 years ago.
Description
I just checked a TYPO3 8.6.1 (for fun) using the composer install routine. After setup, I added the latest tt_news manually to the ext folder. The installation of tt_news causes a severe error, because it still uses the SpriteManager class (in ext_tables.php). After uninstalling, I let the install tool check my extensions - and it said that everything was fine. Which should not be the case... right?
Markus - I take the liberty to assign you to this task right away, hope this is fine with you!
- Status changed from New to Needs Feedback
- Target version deleted (
8 LTS)
Hi Robert!
Nice to hear from you.
Well few things. First if you install in composer mode, you may not install extensions manually or copy them anywhere.
Second tt_news is probably not marked compatible with CMS 8. Personally we use only news (from Georg) for years now.
Markus Klein wrote:
Hi Robert!
Nice to hear from you.
Well few things. First if you install in composer mode, you may not install extensions manually or copy them anywhere.
Second tt_news is probably not marked compatible with CMS 8. Personally we use only news (from Georg) for years now.
Hi, Markus!
Thanks for the response! I didn't realise that manual installation is prohibited, too. Makes sense, though.
(tt_news is indeed not yet compatible with v8. That's why I used it - to test the installer tool...)
So the "Check for broken extensions" function in the installer also distinguishes between "old" setup and composer setup? By using the autoloader class?
It is a bit confusing, because the explanation says:
"Checks whether the local extensions' ext_tables and ext_localconf files can be included without errors, meaning they can be loaded without breaking the system."
Digged quite a bit through the sysext/install ext, but could not find a hint, whether there is a check routine for composer and one without...
Shouldn't the check work anyway? Or could you point me to the place, where the distinction (composer yes/no) is made? Thanks!
Well, the extension list to test stems from the Package Manager, which of course depends on the installation mode.
Furthermore the autoloader works a bit different in composer mode.
For testing the install tool in a composer mode installation with tt_news it must be:
- installable via composer
- marked compatible with cms 8
I don't know if both is fulfilled.
Otherwise please use a normal installation and put tt_news there and test again.
The main logic around composer mode sits somewhere in the Bootstrap logic of ext:core.
- Priority changed from Must have to -- undefined --
Thanks for clarification, Markus!
As for me, this topic could be closed again.
Good day!
- % Done changed from 0 to 100
- Status changed from Needs Feedback to Closed
Also available in: Atom
PDF