-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem mit Contao 4.11.1 und Parameter "kernel.root_dir" #107
Comments
same issue here by installing [omosde/contao-om-backend] |
Ursache für das Problem in Contao 4.11 dürfte folgende Änderung im Hauptcode sein: |
there was no problem, when installing first [do-while/contao-backupdb-bundle] and then [omosde/contao-om-backend] (?) |
@bamsagla No, that is not the reason. The reason is that the parameter |
To avoid such problems in the future it is always best to require all dependencies that this package uses in its
|
dann eben die neue Variante: |
It's not as simple as that. For some reason, this package uses |
- Remove the unused config part of the extension - This should solve a problem with contao 4.11
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
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
|
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 |
#111 would fix this issue. In the mean time you can add
to your root |
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:
The text was updated successfully, but these errors were encountered: