Contao-Community - Installation / Update

4.13.x Update von 4.13 auf 5.3 schlägt fehl

Claudi — Thu, 23 Apr 2026 14:24:02 GMT

Hallo,

will gerade von 4.13.58 auf 5.3.* per Contao Manager installieren.
Update schlägt leider fehl und bekomme folgende Consolen Ausgabe:

Code:

> Resolving dependencies using Composer Cloud v3.9.2

[7.0MiB/0.24s] Loading composer repositories with package information

[102.8MiB/23.80s] Updating dependencies

[203.7MiB/26.42s] Your requirements could not be resolved to an installable set of packages.

[203.7MiB/26.42s] 

  Problem 1

    - Root composer.json requires contao/newsletter-bundle 5.3.* -> satisfiable by contao/newsletter-bundle[5.3.0, ..., 5.3.45].

    - Root composer.json requires do-while/contao-backupdb-bundle ^1.4 -> satisfiable by do-while/contao-backupdb-bundle[1.4.0, ..., 1.6.0].

    - contao/core-bundle[4.9.0, ..., 4.10.4] require php ^7.2 -> your php version (8.5.5.0) does not satisfy that requirement.

    - contao/core-bundle 4.4.0 requires terminal42/header-replay-bundle ^1.0 -> satisfiable by terminal42/header-replay-bundle[1.0.0, ..., 1.5.3].

    - contao/core-bundle[4.4.1, ..., 4.4.17] require php ^5.6|^7.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - contao/core-bundle[4.4.18, ..., 4.4.57] require php ^5.6 || ^7.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - contao/core-bundle[4.5.0, ..., 4.8.8] require php ^7.1 -> your php version (8.5.5.0) does not satisfy that requirement.

    - contao/core-bundle[5.3.0, ..., 5.3.18] require scheb/2fa-backup-code ^6.0 -> satisfiable by scheb/2fa-backup-code[v6.0.0, ..., v6.13.1].

    - contao/newsletter-bundle 5.3.0 requires contao/core-bundle 5.3.0 -> satisfiable by contao/core-bundle[5.3.0].

    - contao/newsletter-bundle 5.3.1 requires contao/core-bundle 5.3.1 -> satisfiable by contao/core-bundle[5.3.1].

    - contao/newsletter-bundle 5.3.10 requires contao/core-bundle 5.3.10 -> satisfiable by contao/core-bundle[5.3.10].

    - contao/newsletter-bundle 5.3.11 requires contao/core-bundle 5.3.11 -> satisfiable by contao/core-bundle[5.3.11].

    - contao/newsletter-bundle 5.3.12 requires contao/core-bundle 5.3.12 -> satisfiable by contao/core-bundle[5.3.12].

    - contao/newsletter-bundle 5.3.13 requires contao/core-bundle 5.3.13 -> satisfiable by contao/core-bundle[5.3.13].

    - contao/newsletter-bundle 5.3.14 requires contao/core-bundle 5.3.14 -> satisfiable by contao/core-bundle[5.3.14].

    - contao/newsletter-bundle 5.3.15 requires contao/core-bundle 5.3.15 -> satisfiable by contao/core-bundle[5.3.15].

    - contao/newsletter-bundle 5.3.16 requires contao/core-bundle 5.3.16 -> satisfiable by contao/core-bundle[5.3.16].

    - contao/newsletter-bundle 5.3.17 requires contao/core-bundle 5.3.17 -> satisfiable by contao/core-bundle[5.3.17].

    - contao/newsletter-bundle 5.3.18 requires contao/core-bundle 5.3.18 -> satisfiable by contao/core-bundle[5.3.18].

    - contao/newsletter-bundle 5.3.19 requires contao/core-bundle 5.3.19 -> satisfiable by contao/core-bundle[5.3.19].

    - contao/newsletter-bundle 5.3.2 requires contao/core-bundle 5.3.2 -> satisfiable by contao/core-bundle[5.3.2].

    - contao/newsletter-bundle 5.3.20 requires contao/core-bundle 5.3.20 -> satisfiable by contao/core-bundle[5.3.20].

    - contao/newsletter-bundle 5.3.21 requires contao/core-bundle 5.3.21 -> satisfiable by contao/core-bundle[5.3.21].

    - contao/newsletter-bundle 5.3.22 requires contao/core-bundle 5.3.22 -> satisfiable by contao/core-bundle[5.3.22].

    - contao/newsletter-bundle 5.3.23 requires contao/core-bundle 5.3.23 -> satisfiable by contao/core-bundle[5.3.23].

    - contao/newsletter-bundle 5.3.24 requires contao/core-bundle 5.3.24 -> satisfiable by contao/core-bundle[5.3.24].

    - contao/newsletter-bundle 5.3.25 requires contao/core-bundle 5.3.25 -> satisfiable by contao/core-bundle[5.3.25].

    - contao/newsletter-bundle 5.3.26 requires contao/core-bundle 5.3.26 -> satisfiable by contao/core-bundle[5.3.26].

    - contao/newsletter-bundle 5.3.27 requires contao/core-bundle 5.3.27 -> satisfiable by contao/core-bundle[5.3.27].

    - contao/newsletter-bundle 5.3.28 requires contao/core-bundle 5.3.28 -> satisfiable by contao/core-bundle[5.3.28].

    - contao/newsletter-bundle 5.3.29 requires contao/core-bundle 5.3.29 -> satisfiable by contao/core-bundle[5.3.29].

    - contao/newsletter-bundle 5.3.3 requires contao/core-bundle 5.3.3 -> satisfiable by contao/core-bundle[5.3.3].

    - contao/newsletter-bundle 5.3.30 requires contao/core-bundle 5.3.30 -> satisfiable by contao/core-bundle[5.3.30].

    - contao/newsletter-bundle 5.3.31 requires contao/core-bundle 5.3.31 -> satisfiable by contao/core-bundle[5.3.31].

    - contao/newsletter-bundle 5.3.32 requires contao/core-bundle 5.3.32 -> satisfiable by contao/core-bundle[5.3.32].

    - contao/newsletter-bundle 5.3.33 requires contao/core-bundle 5.3.33 -> satisfiable by contao/core-bundle[5.3.33].

    - contao/newsletter-bundle 5.3.34 requires contao/core-bundle 5.3.34 -> satisfiable by contao/core-bundle[5.3.34].

    - contao/newsletter-bundle 5.3.35 requires contao/core-bundle 5.3.35 -> satisfiable by contao/core-bundle[5.3.35].

    - contao/newsletter-bundle 5.3.36 requires contao/core-bundle 5.3.36 -> satisfiable by contao/core-bundle[5.3.36].

    - contao/newsletter-bundle 5.3.37 requires contao/core-bundle 5.3.37 -> satisfiable by contao/core-bundle[5.3.37].

    - contao/newsletter-bundle 5.3.38 requires contao/core-bundle 5.3.38 -> satisfiable by contao/core-bundle[5.3.38].

    - contao/newsletter-bundle 5.3.39 requires contao/core-bundle 5.3.39 -> satisfiable by contao/core-bundle[5.3.39].

    - contao/newsletter-bundle 5.3.4 requires contao/core-bundle 5.3.4 -> satisfiable by contao/core-bundle[5.3.4].

    - contao/newsletter-bundle 5.3.40 requires contao/core-bundle 5.3.40 -> satisfiable by contao/core-bundle[5.3.40].

    - contao/newsletter-bundle 5.3.41 requires contao/core-bundle 5.3.41 -> satisfiable by contao/core-bundle[5.3.41].

    - contao/newsletter-bundle 5.3.42 requires contao/core-bundle 5.3.42 -> satisfiable by contao/core-bundle[5.3.42].

    - contao/newsletter-bundle 5.3.43 requires contao/core-bundle 5.3.43 -> satisfiable by contao/core-bundle[5.3.43].

    - contao/newsletter-bundle 5.3.44 requires contao/core-bundle 5.3.44 -> satisfiable by contao/core-bundle[5.3.44].

    - contao/newsletter-bundle 5.3.45 requires contao/core-bundle 5.3.45 -> satisfiable by contao/core-bundle[5.3.45].

    - contao/newsletter-bundle 5.3.5 requires contao/core-bundle 5.3.5 -> satisfiable by contao/core-bundle[5.3.5].

    - contao/newsletter-bundle 5.3.6 requires contao/core-bundle 5.3.6 -> satisfiable by contao/core-bundle[5.3.6].

    - contao/newsletter-bundle 5.3.7 requires contao/core-bundle 5.3.7 -> satisfiable by contao/core-bundle[5.3.7].

    - contao/newsletter-bundle 5.3.8 requires contao/core-bundle 5.3.8 -> satisfiable by contao/core-bundle[5.3.8].

    - contao/newsletter-bundle 5.3.9 requires contao/core-bundle 5.3.9 -> satisfiable by contao/core-bundle[5.3.9].

    - do-while/contao-backupdb-bundle[1.4.0, ..., 1.4.2] require contao/core-bundle >=4.4.0,<5.0 -> satisfiable by contao/core-bundle[4.4.0, ..., 4.13.58].

    - do-while/contao-backupdb-bundle[1.5.0, ..., 1.6.0] require contao/core-bundle >=4.9.0,<5.0 -> satisfiable by contao/core-bundle[4.9.0, ..., 4.13.58].

    - scheb/2fa-backup-code[v6.0.0, ..., v6.3.0] require php ~8.0.0 || ~8.1.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - scheb/2fa-backup-code[v6.10.0, ..., v6.12.0] require php ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - scheb/2fa-backup-code v6.13.0 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - scheb/2fa-backup-code v6.13.1 requires php ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - scheb/2fa-backup-code[v6.4.0, ..., v6.9.0] require php ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - terminal42/header-replay-bundle[1.0.0, ..., 1.4.4] require php >=5.6,<8 -> your php version (8.5.5.0) does not satisfy that requirement.

    - terminal42/header-replay-bundle[1.5.0, ..., 1.5.3] require php ^5.6 | ^7.0 -> your php version (8.5.5.0) does not satisfy that requirement.

    - Conclusion: don't install contao/core-bundle 5.3.20 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.21 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.22 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.23 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.24 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.25 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.26 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.27 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.28 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.29 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.30 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.31 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.32 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.33 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.34 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.35 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.36 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.37 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.38 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.39 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.40 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.41 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.42 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.43 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.44 (conflict analysis result)

    - Conclusion: don't install contao/core-bundle 5.3.45 (conflict analysis result)

    - You can only install one version of a package, so only one of these can be installed: contao/core-bundle[4.1.0, ..., 4.13.58, 5.0.0, ..., 5.7.3].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

[203.8MiB/26.42s] 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.

[66.8MiB/26.56s] Memory usage: 66.84MB (peak: 239.99MB), time: 26.57s.

[66.8MiB/26.56s] Finished Composer Cloud resolving.

# Cloud Job ID hJVene3fcGjhVk5XIqBAjq5qXiYGj0VLSjIHrofrajeqOORgwB9FMaHMI0TnaF1NlRSY1mIX4nT4d8ElT3tBC7IF3d8vTveCatXRioh8NLAeBaCYs failed

Hier noch meine composer.json

Code:

{

    "type": "project",

    "require": {

        "codefog/contao-cookiebar": "^2.1",

        "codefog/contao-mobile_menu": "^2.7",

        "contao/calendar-bundle": "4.13.*",

        "contao/comments-bundle": "4.13.*",

        "contao/conflicts": "*@dev",

        "contao/faq-bundle": "4.13.*",

        "contao/listing-bundle": "4.13.*",

        "contao/manager-bundle": "4.13.*",

        "contao/news-bundle": "4.13.*",

        "contao/newsletter-bundle": "4.13.*",

        "do-while/contao-backupdb-bundle": "^1.4",

        "madeyourday/contao-rocksolid-columns": "^2.0",

        "madeyourday/contao-rocksolid-custom-elements": "^2.2",

        "madeyourday/contao-rocksolid-slider": "^2.0",

        "netzmacht/contao-font-awesome-inserttag": "^2.0"

    },

    "extra": {

        "contao-component-dir": "assets"

    },

    "scripts": {

        "post-install-cmd": [

            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"

        ],

        "post-update-cmd": [

            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"

        ]

    },

    "config": {

        "audit": {

            "block-insecure": false

        }

    }

}

Kann mir hier bitte jemand weiterhelfen?
(Muss dazu sagen, wir kommen bei dieser Website von einer ursprünglich installierten Version 4.4)

5.7.x Neuinstallation 5.7: Schleife in der DB

mv-soft — Wed, 22 Apr 2026 12:05:29 GMT

Hallo,

installiere soeben CONTAO 5.7 neu, doch über den Contao- Manager hänge ich bei der DB in einer Schleife:

Code:

Feld webauthn_credentials.transports ändernJSON NOT NULL

Feld webauthn_credentials.trustPath ändernJSON NOT NULL

Feld webauthn_credentials.otherUI ändernJSON DEFAULT NULL

ALTER TABLE webauthn_credentials CHANGE transports transports JSON NOT NULL, CHANGE trustPath trustPath JSON NOT NULL, CHANGE otherUI otherUI JSON DEFAULT NULL

Feld tl_content.jsonData ändernJSON DEFAULT NULL

ALTER TABLE tl_content CHANGE jsonData jsonData JSON DEFAULT NULL

Was habe ich übersehen ?

Vielen Dank für Hinweise.

Mehrere Websites in einer Installation?

bowman — Tue, 21 Apr 2026 06:56:13 GMT

Hallo zusammen!

Ich stehe gerade vor einer für mich neuen Aufgabe und wollte Euch um Eure Einschätzung bitten.

Ich soll innerhalb einer bestehenden Contao-Installation (also neben der bisherigen Hauptseite) eine weitere Website aufbauen. Wenn ich es richtig verstanden habe, würde das über einen eigenen Seitenbaum mit eigenem Theme und eigener Domain laufen – korrekt?

Bisher habe ich immer nur mit „eine Installation = eine Website“ gearbeitet, daher fehlt mir hier etwas die Erfahrung.

Meine konkrete Frage:
Ist es möglich (und sinnvoll), die neue Seite zunächst lokal aufzubauen und anschließend in die bestehende Installation zu übertragen?

Ich hätte jetzt naiv gedacht:

* Theme lokal entwickeln und als cto-Datei exportieren
* benötigte Dateien aus dem Dateisystem übernehmen
* Theme in der Zielinstallation importieren

Aber wie sieht es mit den Inhalten aus?
Müssen Seiten, Artikel und Inhaltselemente im Zielsystem komplett neu angelegt werden (was in diesem Fall überschaubar wäre) oder gibt es dafür einen sauberen Migrationsweg?

Wie würdet Ihr hier vorgehen bzw. was ist Best Practice in so einem Fall?

Hinweis: Da wir erst einmal nur ein Angebot für dieses Projekt erstellen, und ich noch keinen Einblick in das bestehende System habe, weiß ich nicht, um welche Contao-Version es sich handelt. Ich gehe aber davon aus, dass es 5.3 oder 4.13 sein wird.

Vielen Dank Euch!

5.7.x Upgrade von 4.13 auf 5.7: DB Problem trotz erfolgreichem Testlauf

mv-soft — Mon, 20 Apr 2026 08:50:18 GMT

Hallo,

habe in 4.13 alte Erweiterungen gelöscht und einen Testlauf gemacht... kein Fehler.

Jetzt wurde das Upgrade zwar umgesetzt, aber die DB meldet einen Fehler:

Code:

Datenbank-Probleme

Exception in file vendor/doctrine/dbal/src/Driver/API/MySQL/ExceptionConverter.php on line 91



An exception occurred in the driver: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: NO)

#0 vendor/doctrine/dbal/src/Connection.php(1460): Doctrine\DBAL\Driver\API\MySQL\ExceptionConverter->convert()

#1 vendor/doctrine/dbal/src/Connection.php(1402): Doctrine\DBAL\Connection->handleDriverException()

#2 vendor/doctrine/dbal/src/Connection.php(224): Doctrine\DBAL\Connection->convertException()

#3 vendor/doctrine/dbal/src/Connection.php(792): Doctrine\DBAL\Connection->connect()

#4 vendor/doctrine/dbal/src/Connection.php(332): Doctrine\DBAL\Connection->executeQuery()

#5 vendor/contao/core-bundle/src/Command/MigrateCommand.php(528): Doctrine\DBAL\Connection->fetchOne()

#6 vendor/contao/core-bundle/src/Command/MigrateCommand.php(73): Contao\CoreBundle\Command\MigrateCommand->compileConfigurationErrors()

#7 vendor/symfony/console/Command/Command.php(341): Contao\CoreBundle\Command\MigrateCommand->execute()

#8 vendor/symfony/console/Application.php(1117): Symfony\Component\Console\Command\Command->run()

#9 vendor/symfony/framework-bundle/Console/Application.php(123): Symfony\Component\Console\Application->doRunCommand()

#10 vendor/symfony/console/Application.php(356): Symfony\Bundle\FrameworkBundle\Console\Application->doRunCommand()

#11 vendor/symfony/framework-bundle/Console/Application.php(77): Symfony\Component\Console\Application->doRun()

#12 vendor/symfony/console/Application.php(195): Symfony\Bundle\FrameworkBundle\Console\Application->doRun()

#13 vendor/contao/manager-bundle/bin/contao-console(45): Symfony\Component\Console\Application->run()

#14 {main}

Was habe ich übersehen ?

Vielen Dank für Hinweise.

5.7.x Contao Manager: Endlos Schleife bei DB Aktualisierung

mv-soft — Fri, 17 Apr 2026 08:04:04 GMT

Hallo,

am Ende des Upodates fon 5.3 auf 5.7 gibt es eine Endlos- Schleife:

Code:

Feld webauthn_credentials.transports ändern



JSON NOT NULL

Feld webauthn_credentials.trustPath ändern



JSON NOT NULL

Feld webauthn_credentials.otherUI ändern



JSON DEFAULT NULL

ALTER TABLE webauthn_credentials CHANGE transports transports JSON NOT NULL, CHANGE trustPath trustPath JSON NOT NULL, CHANGE otherUI otherUI JSON DEFAULT NULL

Feld tl_content.jsonData ändern



JSON DEFAULT NULL

ALTER TABLE tl_content CHANGE jsonData jsonData JSON DEFAULT NULL

Nach Abbruch ist alles korrekt aufrufbar, nur bleibt der Hinweis im CONTAO Manager (Datenbank) bestehen.

Vielen Dank für Hinweise.

5.7.x Laden der jquery.min.js,modernizr.min.js

Birden — Thu, 16 Apr 2026 05:07:32 GMT

Ich vermute, daß das Problem mit dem aktuellen Update des Contao-Managers auf die Version 1.10.13 zusammenhängt. Nach dem Update steht eine Datenbankaktualisierung an. Ich habe vergessen, zu notieren, was genau. Auf jeden Fall wird jetzt im Entwicklerwerkzeug des Browsers Folgendes ausgegeben, und das in allen lokalen Installationen mit der Aktualisierung:

Layout-Darstellung wurde erzwungen, bevor die Seite vollständig geladen war. Falls Stylesheets noch nicht geladen sind, kann dies zu einer kurzzeitigen Darstellung des Inhalts ohne Formatierung führen. jquery.min.js,modernizr.min.js-xxxxxxxxx.js:6:8582

Update 4.13 -> 5.7 : Fehler und irritierende Meldung des Composers

volkermb — Thu, 09 Apr 2026 07:07:07 GMT

Hallo!

Ich habe von einer bestehenden 4.13-Installation einen Klon erstellt (läuft einwandfrei) - und möchte den Klon nun auf 5.7 aktualisieren. Das habe ich bereits mit zwei anderen Installationen problemlos hinbekommen. Bei der jetztigen aber nicht.

Ausgangspunkt ist Contao 4.13 mit vier installieren Extensions: codefog/news-categories sowie mademyday/slider und mademyday/custom-elements und maymyday/anti-spam. Alle Mademyday-Extensions sind auf dem aktuellsten Stand. Die Extension News-Categories liegt in der Version 3.5.8 vor (aktuellste mit 4.13 kompatible Version).

Wie bei den zwei anderen Installationen (gleiches Setting) war mein Plan, in einem Rutsch das Contao-Paket sowie die Extensions zu aktualisieren (New-Categories muss auf 4.0.x aktualisiert werden, um mit 5.7 kompatibel zu sein). Leider scheitert dieses.

Ich bin kein Contao oder Composer-Profi, aber die Fehlermeldung, dass PHP > 7.2 erforderlich ist, PHP 8.3 diese Anforderung aber nicht erfüllt, erscheint mir verwunderlich. Auch ist in der Fehlermeldung vom Contao-Core 4.9 -> 4.10 die Rede...

Hier die vollständige Composer-Meldung:

composer require codefog/contao-news_categories=4.0 contao/manager-bundle=5.7.* contao/news-bundle=5.7.* contao/calendar-bundle=5.7.* contao/faq-bundle=5.7.* contao/comments-bundle=5.7.* contao/newsletter-bundle=5.7.* contao/listing-bundle=5.7.* --no-update
composer update --no-install
> Resolving dependencies using Composer Cloud v3.9.1
[7.2MiB/0.21s] Loading composer repositories with package information
[99.4MiB/22.10s] Updating dependencies
[196.1MiB/23.70s] Your requirements could not be resolved to an installable set of packages.
[196.1MiB/23.71s]
Problem 1
- Root composer.json requires contao/newsletter-bundle 5.7.* -> satisfiable by contao/newsletter-bundle[5.7.0, 5.7.1, 5.7.2, 5.7.3].
- Root composer.json requires do-while/contao-backupdb-bundle ^1.6 -> satisfiable by do-while/contao-backupdb-bundle[1.6.0].
- contao/core-bundle[4.9.0, ..., 4.10.4] require php ^7.2 -> your php version (8.3.30.0) does not satisfy that requirement.
- contao/newsletter-bundle 5.7.0 requires contao/core-bundle 5.7.0 -> satisfiable by contao/core-bundle[5.7.0].
- contao/newsletter-bundle 5.7.1 requires contao/core-bundle 5.7.1 -> satisfiable by contao/core-bundle[5.7.1].
- contao/newsletter-bundle 5.7.2 requires contao/core-bundle 5.7.2 -> satisfiable by contao/core-bundle[5.7.2].
- contao/newsletter-bundle 5.7.3 requires contao/core-bundle 5.7.3 -> satisfiable by contao/core-bundle[5.7.3].
- do-while/contao-backupdb-bundle 1.6.0 requires contao/core-bundle >=4.9.0,<5.0 -> satisfiable by contao/core-bundle[4.9.0, ..., 4.13.58].
- Conclusion: don't install contao/core-bundle 5.7.1 (conflict analysis result)
- Conclusion: don't install contao/core-bundle 5.7.2 (conflict analysis result)
- Conclusion: don't install contao/core-bundle 5.7.3 (conflict analysis result)
- You can only install one version of a package, so only one of these can be installed: contao/core-bundle[4.3.0, ..., 4.13.58, 5.0.0, ..., 5.7.3].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[196.1MiB/23.71s] 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.
[65.8MiB/23.83s] Memory usage: 65.79MB (peak: 233.92MB), time: 23.84s.
[65.8MiB/23.84s] Finished Composer Cloud resolving.
# Cloud Job ID HyAQm5tNvdzY5QGFwKQZwZaK9ywMTF0CPQrQMq9mDa5nR1IyFm bQ9ZjRXC6kAN7bZfqDyhHmHFBRRAW2evnV6f8h7R6znR8zS4bG vdmPBj34l failed

Habt Ihr eine Idee, was ich hier falsch mache?

Bin dankbar für jeden Hinweis.

VG, Volker

Installation Contao 5.3.

hendele — Tue, 07 Apr 2026 12:55:19 GMT

Hallo liebe Gemeinde,
heute macht die Installation von Contao 5.3 (auch 5.7) Probleme. Beim installieren hägt das System (siehe Anhang). Habe es mehrfacht versucht.
Gibt es da ein allgemeines Problem? Gestern hatte ich noch eine Installation gemacht, ohne Probleme.

Danke
Erwin

Angehängte Grafiken

Bildschirmfoto 2026-04-07 um 14.54.34.png (65,7 KB)

CONTAO Server für Update Arbeiten gestört ?

mv-soft — Tue, 07 Apr 2026 09:37:19 GMT

Hallo,

kann seit ca. 1h KEINE Update- Arbeiten per CONTAO- Manager umsetzen ( aktuell 26 Aufgaben auf 0 Servern )?

Code:

composer update contao/manager-bundle contao/news-bundle contao/calendar-bundle contao/faq-bundle contao/comments-bundle contao/newsletter-bundle contao/listing-bundle contao/conflicts contao/core-bundle contao/installation-bundle --no-install --dry-run



Berechnung startet in ca. 457 Sekunden (aktuell 26 Aufgaben auf 0 Servern)

Kann das bestätigt werden ?

Vielen Dank für eine Rückmeldung.

4.13.x Upgrade zu 5.3 -> 5.7

John Doe — Mon, 06 Apr 2026 10:16:37 GMT

Hallo
ich wollte (jaja, reichlich spät ich weiss, asche auf mein Haupt) von meiner 4.9 LTS auf die aktuelle 5.7 LTS wechseln.
Das ganze wird aktuell bei Strato gehostet.

4.9 -> 4.13 ging recht problemlos mit dem Contao Manager.

4.13 -> 5.3 scheiter immer. Ich habe "notofication center" schon aktualisiert, das sollte so wie ich das verstehe mit 17x funktionieren. Allerdings schlägt das Update immer noch fehl:

Code:

$ /opt/RZphp84/bin/php-cli -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=MET /mnt/web121/c3/72/546472/htdocs/CRASH2/web/contao-manager.phar.php composer require contao/manager-bundle=5.3.* contao/news-bundle=5.3.* contao/calendar-bundle=5.3.* contao/faq-bundle=5.3.* contao/comments-bundle=5.3.* contao/listing-bundle=5.3.* contao/newsletter-bundle=5.3.* --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction



Deprecation Notice: ContaoCommunityAlliance\Composer\Plugin\Plugin::__construct(): Implicitly marking parameter $runonceManager as nullable is deprecated, the explicit nullable type must be used instead in /mnt/web121/c3/72/546472/htdocs/CRASH2/vendor/contao-community-alliance/composer-plugin/src/Plugin.php:65

More deprecation notices were hidden, run again with `-v` to show them.

/mnt/web121/c3/72/546472/htdocs/CRASH2/composer.json has been updated



# Process terminated with exit code 0

# Result: OK





> Resolving dependencies using Composer Cloud v3.9.1



[7.0MiB/0.21s] Loading composer repositories with package information

[85.9MiB/14.34s] Updating dependencies

[133.6MiB/15.89s] Your requirements could not be resolved to an installable set of packages.

[133.6MiB/15.89s] 

  Problem 1

    - Root composer.json requires contao/calendar-bundle 5.3.* -> satisfiable by contao/calendar-bundle[5.3.0, ..., 5.3.45].

    - contao/calendar-bundle 5.3.0 requires contao/core-bundle 5.3.0 -> found contao/core-bundle[5.3.0] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.1 requires contao/core-bundle 5.3.1 -> found contao/core-bundle[5.3.1] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.10 requires contao/core-bundle 5.3.10 -> found contao/core-bundle[5.3.10] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.11 requires contao/core-bundle 5.3.11 -> found contao/core-bundle[5.3.11] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.12 requires contao/core-bundle 5.3.12 -> found contao/core-bundle[5.3.12] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.13 requires contao/core-bundle 5.3.13 -> found contao/core-bundle[5.3.13] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.14 requires contao/core-bundle 5.3.14 -> found contao/core-bundle[5.3.14] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.15 requires contao/core-bundle 5.3.15 -> found contao/core-bundle[5.3.15] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.16 requires contao/core-bundle 5.3.16 -> found contao/core-bundle[5.3.16] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.17 requires contao/core-bundle 5.3.17 -> found contao/core-bundle[5.3.17] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.18 requires contao/core-bundle 5.3.18 -> found contao/core-bundle[5.3.18] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.19 requires contao/core-bundle 5.3.19 -> found contao/core-bundle[5.3.19] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.2 requires contao/core-bundle 5.3.2 -> found contao/core-bundle[5.3.2] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.20 requires contao/core-bundle 5.3.20 -> found contao/core-bundle[5.3.20] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.21 requires contao/core-bundle 5.3.21 -> found contao/core-bundle[5.3.21] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.22 requires contao/core-bundle 5.3.22 -> found contao/core-bundle[5.3.22] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.23 requires contao/core-bundle 5.3.23 -> found contao/core-bundle[5.3.23] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.24 requires contao/core-bundle 5.3.24 -> found contao/core-bundle[5.3.24] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.25 requires contao/core-bundle 5.3.25 -> found contao/core-bundle[5.3.25] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.26 requires contao/core-bundle 5.3.26 -> found contao/core-bundle[5.3.26] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.27 requires contao/core-bundle 5.3.27 -> found contao/core-bundle[5.3.27] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.28 requires contao/core-bundle 5.3.28 -> found contao/core-bundle[5.3.28] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.29 requires contao/core-bundle 5.3.29 -> found contao/core-bundle[5.3.29] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.3 requires contao/core-bundle 5.3.3 -> found contao/core-bundle[5.3.3] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.30 requires contao/core-bundle 5.3.30 -> found contao/core-bundle[5.3.30] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.31 requires contao/core-bundle 5.3.31 -> found contao/core-bundle[5.3.31] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.32 requires contao/core-bundle 5.3.32 -> found contao/core-bundle[5.3.32] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.33 requires contao/core-bundle 5.3.33 -> found contao/core-bundle[5.3.33] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.34 requires contao/core-bundle 5.3.34 -> found contao/core-bundle[5.3.34] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.35 requires contao/core-bundle 5.3.35 -> found contao/core-bundle[5.3.35] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.36 requires contao/core-bundle 5.3.36 -> found contao/core-bundle[5.3.36] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.37 requires contao/core-bundle 5.3.37 -> found contao/core-bundle[5.3.37] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.38 requires contao/core-bundle 5.3.38 -> found contao/core-bundle[5.3.38] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.39 requires contao/core-bundle 5.3.39 -> found contao/core-bundle[5.3.39] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.4 requires contao/core-bundle 5.3.4 -> found contao/core-bundle[5.3.4] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.40 requires contao/core-bundle 5.3.40 -> found contao/core-bundle[5.3.40] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.41 requires contao/core-bundle 5.3.41 -> found contao/core-bundle[5.3.41] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.42 requires contao/core-bundle 5.3.42 -> found contao/core-bundle[5.3.42] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.43 requires contao/core-bundle 5.3.43 -> found contao/core-bundle[5.3.43] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.44 requires contao/core-bundle 5.3.44 -> found contao/core-bundle[5.3.44] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.45 requires contao/core-bundle 5.3.45 -> found contao/core-bundle[5.3.45] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.5 requires contao/core-bundle 5.3.5 -> found contao/core-bundle[5.3.5] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.6 requires contao/core-bundle 5.3.6 -> found contao/core-bundle[5.3.6] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.7 requires contao/core-bundle 5.3.7 -> found contao/core-bundle[5.3.7] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.8 requires contao/core-bundle 5.3.8 -> found contao/core-bundle[5.3.8] but these were not loaded, likely because it conflicts with another require.

    - contao/calendar-bundle 5.3.9 requires contao/core-bundle 5.3.9 -> found contao/core-bundle[5.3.9] but these were not loaded, likely because it conflicts with another require.



[133.6MiB/15.89s] 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.

[56.7MiB/15.96s] Memory usage: 56.73MB (peak: 199.89MB), time: 15.97s.

[56.7MiB/15.96s] Finished Composer Cloud resolving.





# Cloud Job ID DJuaUFelPq5xbksB7s4SOoVAb8hURgj6GH1pqEtTy6q6nUPywAPmXHBMs1rk8zG2Vzrf9aw2USH4 failed

Ich hatte zwischendurch mal versucht alle Plugins vom "contao-bundle" zu entfernen. Das hat aber an der Fehlermeldung nix geändert, im Gegenteil er wollte die dann wieder haben...

Bin ich zu doof die Fehlermeldung zu lesen oder gibt es da einen Trick?

Merci.

Sonstiges XAMPP - Fehler bei der Installation (Uncaught Error)

NehCoy — Sat, 04 Apr 2026 20:07:23 GMT

Hallo!

Ich habe soeben unter Windows 11 die Version v3.3.0 von XAMPP installiert und den Contao-Manager gestartet.
Nach der Auswahl des Verzeichnisses public bekomme ich eine Fehlermeldung angezeigt. In der Log-Datei ist folgendes zu finden:

Code:

[04-Apr-2026 21:56:47 Europe/Berlin] PHP Fatal error:  Uncaught Error: Class "_ContaoManager\Contao\ManagerApi\HttpKernel\ApiProblemResponse" not found in phar://C:/xampp/htdocs/contao-manager.phar.php/dist/api.php:25

Stack trace:

#0 C:\xampp\htdocs\contao-manager.phar.php(69): Phar::webPhar(NULL, 'index.html', NULL, Array, 'rewrites')

#1 {main}

  thrown in phar://C:/xampp/htdocs/contao-manager.phar.php/dist/api.php on line 25

[04-Apr-2026 21:56:47 Europe/Berlin] PHP Fatal error:  Uncaught Error: Class "_ContaoManager\Symfony\Component\ErrorHandler\Error\FatalError" not found in phar://C:/xampp/htdocs/contao-manager.phar.php/vendor/symfony/error-handler/ErrorHandler.php:529

Stack trace:

#0 [internal function]: _ContaoManager\Symfony\Component\ErrorHandler\ErrorHandler::handleFatalError()

#1 {main}

  thrown in phar://C:/xampp/htdocs/contao-manager.phar.php/vendor/symfony/error-handler/ErrorHandler.php on line 529

Ich kann danach manuell den Manager über die URL http://localhost/public/contao-manager.phar.php erneut aufrufen und die Installation fortführen, aber ich denke dieser "Uncaught Error" ist dennoch so nicht gwünscht!?

Viele Grüße
NehCoy