Closed hwit-biz closed 3 years ago
same issue here by installing [omosde/contao-om-backend] communitythread
Ursache für das Problem in Contao 4.11 dürfte folgende Änderung im Hauptcode sein: https://github.com/contao/contao/pull/2774 bzw. https://github.com/contao/contao/pull/2773 Grund hierfür ist wohl die Umstellung von Symfony 4.4 auf Version 5.2 mit der Auswirkung "Do not use Kernel::$rootDir anymore"... Bin leider zu wenig im Code drin, um einen Commit herstellen zu können - löschen der betroffenen Zeile bringt nur weitere Fehler.
there was no problem, when installing first [do-while/contao-backupdb-bundle] and then [omosde/contao-om-backend] (?)
Ursache für das Problem in Contao 4.11 dürfte folgende Änderung im Hauptcode sein: contao/contao#2774 bzw. contao/contao#2773
@bamsagla No, that is not the reason. The reason is that the parameter kernel.root_dir
is not available in Symfony 5 - or more specifically in version 5.x of symfony/http-kernel
. Contao 4.11 supports both Symfony 4 and 5.
To avoid such problems in the future it is always best to require all dependencies that this package uses in its composer.json
and not rely on anything that the contao/core-bundle
requires, because that can always change. In this case, the following packages could be added to the composer.json
(in the appropriate version):
symfony/http-kernel
(this is the package relevant to this issue)symfony/event-dispatcher
symfony/config
symfony/dependency-injection
symfony/http-foundation
symfony/translation
$container->getParameter('kernel.root_dir'),
dann eben die neue Variante: $container->getParameter('kernel.project_dir')
, das sollte doch auch in Symfony 4 funktionieren
dann eben die neue Variante:
$container->getParameter('kernel.project_dir')
, das sollte doch auch in Symfony 4 funktionieren
It's not as simple as that. For some reason, this package uses Contao\CoreBundle\DependencyInjection\Configuration
and passes $container->getParameter('kernel.project_dir')
as the third parameter. However, the constructor of that class only takes two parameters - and they seem to be used wrong in this case. So I think its usage needs to be evaluated.
I have removed the config part which makes trouble. We didn't need it so we can remove it. There is a new version for testing. If you add this line to the composer.json
"menatwork/contao-multicolumnwizard-bundle":"dev-hotfix/3.4.11-config as 3.4.12"
You can test it. But you can't use it with Symfon 5.2 because there is one requirement wich only allowes symfon 3 and 4
contao-community-alliance/dependency-container
composer why symfony/yaml
contao-community-alliance/dependency-container 2.0.4 requires symfony/yaml (^3.0 || ^4.0)
contao/calendar-bundle 4.11.2 requires symfony/yaml (4.4.* || 5.2.*)
contao/core-bundle 4.11.2 requires symfony/yaml (4.4.* || 5.2.*)
contao/faq-bundle 4.11.2 requires symfony/yaml (4.4.* || 5.2.*)
contao/installation-bundle 4.11.2 requires symfony/yaml (4.4.* || 5.2.*)
contao/manager-bundle 4.11.2 requires symfony/yaml (4.4.* || 5.2.*)
contao/news-bundle 4.11.2 requires symfony/yaml (4.4.* || 5.2.*)
nelmio/security-bundle v2.10.3 requires symfony/yaml (~2.3|~3.0|~4.0|~5.0)
Fix for Contao 4.11 is on master. Support for symfony 5 needs update from contao-community-alliance/dependency-container.
This is still an issue. If you install an extension in Contao 4.11 which requires the MCW, only version 3.4.0 might get installed due to the dependency tree.
Imho MCW should drop the dependency to contao-community-alliance/translator
and increase the minimum requirement for contao/core-bundle
to ^4.9
.
In the mean time you can add
"conflict": {
"menatwork/contao-multicolumnwizard-bundle": "<3.4.11",
"menatwork/contao-multicolumnwizard": "<3.3.4"
}
to your root composer.json
and run composer update
again.
There is a new version 3.5.x which should fix this. So we will close this issue.
Guten Tag.
Ich habe gestern Abend eine Neuinstallation von Contao 4.11.1 über den Contao-Manager auf einem neuen VPS vorgenommen und bin über ein Problem gestolpert.
Zum Selbermachen:
Ursache:
Fehlerprotokoll /var/log/apache2/error.log: