Fehler bei Update auf 4.11.1
Guten Morgen,
ich versuche aktuell verzweifelt, eine Installation auf 4.11.1 zu bringen. Aktuell steht die Seite mit einem 500er Fehler.
Das Update inkl. aller Module ist an sich sauber durch gelaufen. Beim erzeugen des Cache bekomme ich folgende Meldung:
Code:
$ /usr/bin/php7.4-cli -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Paris /homepages/25/d107277713/htdocs/contao/vendor/contao/manager-bundle/bin/contao-console cache:clear --env=prod --no-warmup
In DefinitionErrorExceptionPass.php line 54:
You have requested a non-existent parameter "kernel.root_dir". Did you mean
one of these: "kernel.project_dir", "kernel.build_dir", "kernel.cache_dir"
, "kernel.logs_dir"?
# Process terminated with exit code 1
# Result: General error
Hier meine composer.json
Code:
{
"type": "project",
"require": {
"contao/calendar-bundle": "^4.11",
"contao/comments-bundle": "^4.11",
"contao/conflicts": "*@dev",
"contao/faq-bundle": "^4.11",
"contao/listing-bundle": "^4.11",
"contao/manager-bundle": "^4.11",
"contao/news-bundle": "^4.11",
"contao/newsletter-bundle": "^4.11",
"isotope/isotope-core": "^2.6",
"isotope/isotope_documents": "^1.0",
"madeyourday/contao-rocksolid-columns": "^2.0",
"madeyourday/contao-rocksolid-custom-elements": "^2.2",
"madeyourday/contao-rocksolid-icon-picker": "^2.0",
"madeyourday/contao-rocksolid-mega-menu": "^2.0",
"madeyourday/contao-rocksolid-slider": "^2.0",
"madeyourday/contao-rocksolid-theme-assistant": "^2.0",
"richardhj/contao-isotope_simple_stockmanagement": "^2.0",
"terminal42/contao-changelanguage": "^3.1"
},
"extra": {
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
],
"post-update-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
]
}
}
Jemand eine Idee, was hier schief läuft? Danke!
Auch bei mir Probleme mit Update auf 4.11.1
Guten Nachmittag,
ich habe auch bei 4 Sites Probleme mit dem Update von 4.11.0 auf 4.11.1. Zwar werden keine Fehler gemeldet, aber nach dem Update ist das Frontend nur weiß, das Install Tool lässt sich nicht aufrufen und der Manager läuft im ewigen Reparaturmodus Rundlauf. (Zum Glück habe ich ein Shellcript geschrieben, um alles aus meinem Backup wieder herzustellen.)
Schalte ich vor dem Update den Debug-Modus ein, wird hier ein Fehler bei diesen Bundles vermeldet:
Die »schuldigen« dabei sind wohl das heimrichhannot/contao-teaser-bundle als auch heimrichhannot/dlh_googlemaps.
Wenn ich die beiden Pakete lösche kann ich auf 4.11.1 updaten, dann scheitert aber die Neuinstallation der beiden Bundles:
Hier der Mitschrieb der Installation:
Code:
$ /usr/bin/php74 -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /usr/www/users/heimattd/web/contao-manager.phar.php composer require heimrichhannot/contao-teaser-bundle --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
Using version ^1.1 for heimrichhannot/contao-teaser-bundle
/usr/www/users/heimattd/composer.json has been updated
# Process terminated with exit code 0
# Result: OK
> Resolving dependencies using Composer Cloud v3.0.1
!!! Current server is sponsored by: Contao Association !!!
[7.3MiB/0.24s] Loading composer repositories with package information
[60.9MiB/1.42s] Updating dependencies
[1155.4MiB/9.55s] Your requirements could not be resolved to an installable set of packages.
[1155.4MiB/9.56s]
Problem 1
- contao/manager-bundle is locked to version 4.11.1 and an update of this package was not requested.
- Conclusion: don't install symfony/http-kernel v5.2.2 (conflict analysis result)
- Conclusion: don't install symfony/http-kernel v5.2.3 (conflict analysis result)
- Conclusion: install heimrichhannot/contao-utils-bundle 2.188.10 (conflict analysis result)
- Conclusion: don't install symfony/http-kernel v5.2.4 (conflict analysis result)
- contao/manager-bundle 4.11.1 requires symfony/web-profiler-bundle 4.4.* || 5.2.* -> satisfiable by symfony/web-profiler-bundle[v5.2.4].
- contao/manager-bundle 4.11.1 conflicts with symfony/config v4.4.1.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v4.4.0.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.47.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.46.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.45.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.44.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.43.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.42.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.41.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.40.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.39.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.38.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.37.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.36.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.35.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.34.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.33.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.32.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.31.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.30.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.29.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.28.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.27.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.26.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.25.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.24.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.23.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.22.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.21.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.20.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.19.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.18.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.17.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.16.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.15.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.14.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.13.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.12.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.11.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.10.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.9.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.8.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.7.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.6.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.5.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.4.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.3.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.2.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.1.
- contao/manager-bundle 4.11.1 conflicts with symfony/config v3.4.0.
- Root composer.json requires heimrichhannot/contao-teaser-bundle ^1.1 -> satisfiable by heimrichhannot/contao-teaser-bundle[1.1.0, ..., 1.1.4].
- heimrichhannot/contao-utils-bundle 2.188.10 requires symfony/config ^3.4|^4.4 -> satisfiable by symfony/config[v3.4.0, ..., v3.4.47, v4.4.0, ..., v4.4.20].
- symfony/config[v4.4.2, ..., v4.4.20] conflict with symfony/http-kernel v5.2.0.
- symfony/web-profiler-bundle v5.2.4 requires symfony/http-kernel ^5.2 -> satisfiable by symfony/http-kernel[v5.2.0, ..., v5.2.4].
- Conclusion: don't install symfony/http-kernel v5.2.1 (conflict analysis result)
[1155.4MiB/9.56s] Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
[45.5MiB/10.60s] Memory usage: 45.54MB (peak: 1156.45MB), time: 10.61s.
[45.5MiB/10.60s] Finished Composer Cloud resolving.
# Cloud Job ID Mzcy1kQ5CQQWjdotBX8cz1193ErKnFdY6JOSQRW8i7p3BEELHPNqCngpKu4eclKSLiAmBqRPUMLHT failed
Der Mitschreib hier bezieht sich nur auf das Teaser-Bundle, das Gleiche kommt aber auch bei der Installation vom googlemaps-bundle.
Grüße
Liste der Anhänge anzeigen (Anzahl: 1)
Zitat:
Zitat von
Spooky
Nein, du musst die im Ticket beschriebene Anpassung der composer.json machen (gemeinsam mit den Änderungen für das Update auf Contao 4.11 bspw.). Dann einfach ein Composer Update ausführen.
Also:
ich habe diese composer.json eingepflegt:
Code:
{
"type": "project",
"require": {
"bugbuster/contao-visitors-bundle": "^1.6",
"contao/calendar-bundle": "4.11.*",
"contao/comments-bundle": "4.11.*",
"contao/conflicts": "*@dev",
"contao/faq-bundle": "4.11.*",
"contao/listing-bundle": "4.11.*",
"contao/manager-bundle": "4.11.*",
"contao/news-bundle": "4.11.*",
"contao/newsletter-bundle": "4.11.*",
"dklemmt/contao_dk_mmenu": "^3.1",
"erdmannfreunde/euf_grid": "^3.1",
"georgpreissl/imagecrop": "^1.6",
"heimrichhannot/contao-teaser-bundle": "^1.1",
"heimrichhannot/dlh_googlemaps": "^2.3",
"ma3xl3/contao-easy-favicon": "^2.0",
"madeyourday/contao-rocksolid-slider": "^2.0",
"mindbird/contao-uitotop": "^2.0",
"oveleon/contao-cookiebar": "^1.7",
"trilobit-gmbh/contao-constants-bundle": "^1.0"
},
"extra": {
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
],
"post-update-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
]
}
}
Dann das Composer Update ausgeführt.
Anschließend das Update auf 4.11.1 gemacht, dann ist der Installer nicht mehr aufzurufen, das Frontend zeigt nur eine weiße Seite und in der Systemwartung steht dann:
Anhang 24406
Ergebnis: Website tot. So schön Contao ist wenn es läuft, aber das hier ... :-(