Bug #103908
closed
Inability to carry out './vendor/bin/typo3 extension: setup' on new typo3 13.1 Composer install
Added by Ken Tingey about 1 month ago.
Updated about 1 month ago.
Tags:
extension setup composer
Description
Thank your for your commitment and work on this important project
I have an new Composer install of Typo 13.1 on Ubuntu 20.04. I would like to have a higher OS level, but it is not available in this environment.
I have implemented a Tyop3 Composer install and am working in the backend environment. I have not been able to add extensions. I am repositioning a group of sites that are in version 9.5.4 that has been operational for about ten years.
When I enter this: www-data@hpt95:~/public$ ./vendor/bin/typo3 extension:setup
I get this:
====================
Uncaught TYPO3 Exception Too few arguments to function TYPO3\CMS\Core\DataHandling\SoftReference\SoftReferenceParserFactory::__construct(), 0 passed in /var/www/html/public/vendor/typo3/cms-core/Classes/Utility/GeneralUtility.php on line 2985 and exactly 2 expected
thrown in file /var/www/html/public/vendor/typo3/cms-core/Classes/DataHandling/SoftReference/SoftReferenceParserFactory.php
in line 33
====================
I am working through the two listed files. One thing I have learned is that there has been a good deal of change to these files and functions. Please let me know what needs to be done.
Thank you
Kenneth Tingey
- Status changed from New to Rejected
Hey.
TYPO3 core development won't be able to help you much, here. This sounds as if some outdated installed extension instantiates SoftReferenceParserFactory without using dependency injection. Making SoftReferenceParserFactory DI aware has been added with core v11 already. This roughly looks as if some extension misses a proper typo3 version constraint that it does not yet work with v11 and above, so you end up with an invalid combination of extensions that composer would otherwise prevent. You could try removing extensions to see which one triggers this, or debug into makeInstance() to see where this stems from.
You may want to start looking for usages of that class (directly), or start debugging within GeneralUtility::makeInstance() to see which offending extension triggers this broken instantiation.
This is beyond the core code support of this issue tracker though - core can't help much if some extension does such things. If you're still stuck in this area, you may better want to ask in friendly slack channel #typo3-cms to help with upgrading issues like that.
Note it smells fishy that some extension instantiates SoftReferenceParserFactory within extension:setup in the first place. I think no extension should trigger this at this lowlevel bootstrap phase, and i guess this may be the root of all evil, here.
I hope it's ok to close here.
Thank you. I will work through these suggestions.
This is a clean Composer install. I am trying to install Bootstrap and the Introduction Package. Perhaps the problem lies there. When I remove them though, the problem persists.
Also, thank you for your prompt response and for the suggestions.
Also available in: Atom
PDF
Updated by 
Updated by