Probleme beim Update von Contao 4.13.18 auf 5.1

**Schnippel** · 24.03.2023, 13:01

Hi Leute,

ich führe gerade ein Update durch und stehe vor folgendem Problem:

> Resolving dependencies using Composer Cloud v3.5.1
[7.3MiB/0.17s] Loading composer repositories with package information
[69.5MiB/6.99s] Updating dependencies
[133.5MiB/7.52s] Your requirements could not be resolved to an installable set of packages.
[133.5MiB/7.52s]
Problem 1
- codefog/contao-news_categories[3.5.0, ..., 3.5.1] require contao/news-bundle ^4.13 -> found contao/news-bundle[4.13.0, ..., 4.13.18] but it conflicts with your root composer.json require (5.1.*).
- Root composer.json requires codefog/contao-news_categories ^3.5 -> satisfiable by codefog/contao-news_categories[3.5.0, 3.5.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[133.5MiB/7.52s] <warning>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.</warning>
[38.5MiB/7.58s] Memory usage: 38.53MB (peak: 181.38MB), time: 7.59s.
[38.5MiB/7.58s] Finished Composer Cloud resolving.
# Cloud Job ID i2ikNCeVcUWu5ZOFth1PvD3wQBcP1mNTK8Px1nHqeAzpehOUA4 yAo9dNpORV0cntVX0Im6P9999WBR13mX4Cfs70rIoqL1pN3Vja ppuXyN58Fj9e4DMWIz5cW4KSLi failed

Meine composer.json schaut so hier aus:

HTML-Code:

{
    "type": "project",
    "require": {
        "php": "^8.1",
        "alnv/catalog-manager": "^1.32",
        "codefog/contao-news_categories": "^3.5",
        "contao/calendar-bundle": "5.1.*",
        "contao/comments-bundle": "5.1.*",
        "contao/conflicts": "*@dev",
        "contao/faq-bundle": "5.1.*",
        "contao/listing-bundle": "5.1.*",
        "contao/manager-bundle": "5.1.*",
        "contao/news-bundle": "5.1.*",
        "contao/newsletter-bundle": "5.1.*",
        "do-while/contao-backupdb-bundle": "^1.5",
        "hypergalaktisch/contao-parallax": "^2.0",
        "jrgregory/m17-sticky-backend-footer": "^2.0",
        "mathcontao/be_piwikcharts": "^1.8",
        "numero2/contao-marketing-suite": "^1.0",
        "oveleon/contao-cookiebar": "^1.12",
        "symfony/framework-bundle": "^5.4",
        "terminal42/contao-changelanguage": "^3.3",
        "terminal42/contao-easy_themes": "^2.2",
        "terminal42/contao-mailusername": "^1.0",
        "terminal42/contao-rte_table": "^1.0",
        "terminal42/notification_center": "^1.7",
        "trilobit-gmbh/contao-headerfootercode-bundle": "^1.1"
    },
    "extra": {
        "contao-component-dir": "assets",
        "symfony": {
            "require": "^4.2"
        },
        "public-dir": "web"
    },
    "scripts": {
        "post-install-cmd": [
            "@php vendor/bin/contao-setup"
        ],
        "post-update-cmd": [
            "@php vendor/bin/contao-setup"
        ]
    }
}

Wie muß man hier weiter verfahren?

**tblumrich** · 24.03.2023, 13:31

Bin wirklich kein Experte, aber für mich stehts doch eigentlich da...
codefog/contao-news_categories ist nicht kompatibel mit Contao 5.1

Oder?

***lucina*** · 24.03.2023, 13:33

Wenn Du Erweiterungen unter Contao 5 nutzten möchtest, dann müssen sie auch in einer kompatiblen Version vorliegen, um sie zu installieren.

Detailinformationen zu Extensions findest du auf Packagist, und manchmal lohnt es sich, weiter auf Github zu schauen, ob es eventuell installierbare Dev-Versionen gibt.

**cliffparnitzky** · 24.03.2023, 13:33

Zitat von tblumrich

codefog/contao-news_categories ist nicht kompatibel mit Contao 5.1
Oder?

Würde ich auch so sehen.

**Schnippel** · 24.03.2023, 13:55

Danke für Eure Hinweise.

Ich habe diese Erweiterung erstmal deinstalliert.

Jetzt kommen diese Probleme hier:

> Resolving dependencies using Composer Cloud v3.5.1
[7.3MiB/0.18s] Loading composer repositories with package information
[14.1MiB/0.86s] Updating dependencies
[15.7MiB/1.06s] Your requirements could not be resolved to an installable set of packages.
[15.7MiB/1.06s]
Problem 1
- Root composer.json requires contao/calendar-bundle 5.1.*, found contao/calendar-bundle[5.1.0, 5.1.1] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 2
- Root composer.json requires contao/comments-bundle 5.1.*, found contao/comments-bundle[5.1.0, 5.1.1] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 3
- Root composer.json requires contao/faq-bundle 5.1.*, found contao/faq-bundle[5.1.0, 5.1.1] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 4
- Root composer.json requires contao/listing-bundle 5.1.*, found contao/listing-bundle[5.1.0, 5.1.1] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 5
- Root composer.json requires contao/manager-bundle 5.1.*, found contao/manager-bundle[5.1.0, 5.1.1] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 6
- Root composer.json requires contao/news-bundle 5.1.*, found contao/news-bundle[5.1.0, 5.1.1] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 7
- Root composer.json requires contao/newsletter-bundle 5.1.*, found contao/newsletter-bundle[5.1.0, 5.1.1] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 8
- Root composer.json requires symfony/framework-bundle ^6.2, found symfony/framework-bundle[v6.2.0, ..., v6.2.7] but these were not loaded, likely because it conflicts with another require.
Problem 9
- Root composer.json requires terminal42/notification_center ^1.7, found terminal42/notification_center[1.7.0, 1.7.1] but the package is fixed to 1.6.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 10
- contao/core-bundle 4.13.18 requires symfony/framework-bundle ^5.4 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.21] but it conflicts with your root composer.json require (^6.2).
- trilobit-gmbh/contao-headerfootercode-bundle 1.1.0 requires contao/core-bundle ~4.4 -> satisfiable by contao/core-bundle[4.13.18].
- trilobit-gmbh/contao-headerfootercode-bundle is locked to version 1.1.0 and an update of this package was not requested.
[15.7MiB/1.06s] <warning>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.</warning>
[11.4MiB/1.07s] Memory usage: 11.42MB (peak: 31.63MB), time: 1.07s.
[11.4MiB/1.07s] Finished Composer Cloud resolving.
# Cloud Job ID Yy80JSDrCqjkcdLRIm4FRIN2GY745wpzXLO0XZEX6dQUpOntzF wkY2WAM1NNecDJZM9eGwQKbeqe9tyk2aHdVxv95mUpSG failed

hier die geänderte composer.json

Code:

{
    "type": "project",
    "require": {
        "php": "^8.1",
        "alnv/catalog-manager": "^1.32",
        "contao/calendar-bundle": "5.1.*",
        "contao/comments-bundle": "5.1.*",
        "contao/conflicts": "*@dev",
        "contao/faq-bundle": "5.1.*",
        "contao/listing-bundle": "5.1.*",
        "contao/manager-bundle": "5.1.*",
        "contao/news-bundle": "5.1.*",
        "contao/newsletter-bundle": "5.1.*",
        "do-while/contao-backupdb-bundle": "^1.5",
        "hypergalaktisch/contao-parallax": "^2.0",
        "jrgregory/m17-sticky-backend-footer": "^2.0",
        "mathcontao/be_piwikcharts": "^1.8",
        "numero2/contao-marketing-suite": "^1.0",
        "oveleon/contao-cookiebar": "^1.12",
        "symfony/framework-bundle": "^6.2",
        "terminal42/contao-changelanguage": "^3.3",
        "terminal42/contao-easy_themes": "^2.2",
        "terminal42/contao-mailusername": "^1.0",
        "terminal42/contao-rte_table": "^1.0",
        "terminal42/notification_center": "^1.7",
        "trilobit-gmbh/contao-headerfootercode-bundle": "^1.1"
    },
    "extra": {
        "contao-component-dir": "assets",
        "symfony": {
            "require": "^4.2"
        },
        "public-dir": "web"
    },
    "scripts": {
        "post-install-cmd": [
            "@php vendor/bin/contao-setup"
        ],
        "post-update-cmd": [
            "@php vendor/bin/contao-setup"
        ]
    }
}

Kann das etwa mit dem hier zu tun haben?
"extra": {
"contao-component-dir": "assets",
"symfony": {
"require": "^4.2"
},

**cliffparnitzky** · 24.03.2023, 14:11

Das gehört da sicherlich nicht mehr hin.

Anonsten kommst du vlt. schneller zum Ergebnis, wenn du alles außer Core Bestandteile entfernst, dann auf Contao 5 gehen und dann dein Erweiterungen wieder reinholen, wenn sie denn kompatibel sind.

**mineralwa** · 26.03.2023, 22:23

Das "trilobit-gmbh/contao-headerfootercode-bundle" ist ab Version 2 auch für Contao 5 kompatibel (https://packagist.org/packages/trilo...tercode-bundle)

**Schnippel** · 06.04.2023, 10:56

Hi Leute,

was bedeutet denn diese Fehlermeldung? Und was muß getan werden, damit dieses Problem gelöst wird?

Problem 1
- Root composer.json requires contao/calendar-bundle 5.1.*, found contao/calendar-bundle[5.1.0, 5.1.1, 5.1.2] but the package is fixed to 4.13.18 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

composer.json schaut so aus:

PHP-Code:


{

    "type": "project",

    "require": {

        "php": "^8.1",

        "alnv/catalog-manager": "^1.32",

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

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

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

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

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

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

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

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

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

        "hypergalaktisch/contao-parallax": "^2.0",

        "jrgregory/m17-sticky-backend-footer": "^2.0",

        "mathcontao/be_piwikcharts": "^1.8",

        "numero2/contao-marketing-suite": "^1.0",

        "oveleon/contao-cookiebar": "^1.12",

        "symfony/framework-bundle": "^6.2",

        "terminal42/contao-changelanguage": "^3.3",

        "terminal42/contao-easy_themes": "^2.2",

        "terminal42/contao-mailusername": "^1.0",

        "terminal42/contao-rte_table": "^1.0",

        "terminal42/notification_center": "^1.7",

        "trilobit-gmbh/contao-headerfootercode-bundle": "^1.1"

    },

    "extra": {

        "contao-component-dir": "assets",

        "symfony": {

            "require": "^6.2"

        },

        "public-dir": "web"

    },

    "scripts": {

        "post-install-cmd": [

            "@php vendor/bin/contao-setup"

        ],

        "post-update-cmd": [

            "@php vendor/bin/contao-setup"

        ]

    }

}

**mlweb** · 06.04.2023, 11:27

Code:

but the package is fixed to 4.13.18 (lock file version) by a partial update

In Deinem Lockfile wird Contao 4.13.18 verlangt und Du hast wahrscheinlich kein komplettes Update durchgeführt.

Hast Du geschaut ob alle Erweiterungen mit Contao 5 kompatibel sind? Beim Catalog Manager dürfte das nicht der Fall sein.

**Schnippel** · 06.04.2023, 14:13

Ich bekomme es nicht hin.

Das hier ist im CM eingestellt:

Unbenannt-1.jpg

composer.json:

PHP-Code:


{

    "type": "project",

    "require": {

        "php": "^8.0",

        "alnv/catalog-manager": "^1.32",

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

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

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

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

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

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

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

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

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

        "hypergalaktisch/contao-parallax": "^2.0",

        "jrgregory/m17-sticky-backend-footer": "^2.0",

        "mathcontao/be_piwikcharts": "^1.8",

        "numero2/contao-marketing-suite": "^1.0",

        "oveleon/contao-cookiebar": "^1.12",

        "symfony/framework-bundle": "^6.1",

        "terminal42/contao-changelanguage": "^3.5",

        "terminal42/contao-easy_themes": "^2.2",

        "terminal42/contao-mailusername": "^1.0",

        "terminal42/contao-rte_table": "^1.0",

        "terminal42/notification_center": "^1.7",

        "trilobit-gmbh/contao-headerfootercode-bundle": "^1.1"

    },

    "extra": {

        "contao-component-dir": "assets",

        "symfony": {

            "require": "^4.2"

        },

        "public-dir": "web"

    },

    "scripts": {

        "post-install-cmd": [

            "@php vendor/bin/contao-setup"

        ],

        "post-update-cmd": [

            "@php vendor/bin/contao-setup"

        ]

    }

}

CM gibt diese Fehlermeldung aus:

Resolving dependencies using Composer Cloud v3.6.0
[7.2MiB/0.17s] Loading composer repositories with package information
[69.2MiB/7.31s] Updating dependencies
[133.8MiB/8.30s] Your requirements could not be resolved to an installable set of packages.
[133.8MiB/8.30s]
Problem 1
- contao/core-bundle 4.4.0 requires symfony/framework-bundle ^3.3 -> found symfony/framework-bundle[v3.3.0, ..., v3.4.47] but it conflicts with your root composer.json require (^6.1).
- contao/core-bundle[4.4.1, ..., 4.4.17] require php ^5.6|^7.0 -> your php version (8.1.13.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.1.13.0) does not satisfy that requirement.
- contao/core-bundle[4.5.0, ..., 4.8.8] require php ^7.1 -> your php version (8.1.13.0) does not satisfy that requirement.
- contao/core-bundle[4.9.0, ..., 4.10.4] require php ^7.2 -> your php version (8.1.13.0) does not satisfy that requirement.
- contao/core-bundle[4.9.10, ..., 4.10.7] require symfony/framework-bundle 4.4.* -> found symfony/framework-bundle[v4.4.0, ..., v4.4.49] but it conflicts with your root composer.json require (^6.1).
- contao/core-bundle[4.11.0, ..., 4.11.9] require symfony/framework-bundle 4.4.* || 5.2.* -> found symfony/framework-bundle[v4.4.0, ..., v4.4.49, v5.2.0, ..., v5.2.12] but it conflicts with your root composer.json require (^6.1).
- contao/core-bundle[4.12.0, ..., 4.12.7] require symfony/framework-bundle ^4.4 || ^5.2 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.49, v5.2.0, ..., v5.4.22] but it conflicts with your root composer.json require (^6.1).
- contao/core-bundle[4.13.0, ..., 4.13.19] require symfony/framework-bundle ^5.4 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.22] but it conflicts with your root composer.json require (^6.1).
- trilobit-gmbh/contao-headerfootercode-bundle 1.1.0 requires contao/core-bundle ~4.4 -> satisfiable by contao/core-bundle[4.4.0, ..., 4.13.19].
- Root composer.json requires trilobit-gmbh/contao-headerfootercode-bundle ^1.1 -> satisfiable by trilobit-gmbh/contao-headerfootercode-bundle[1.1.0].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[133.8MiB/8.30s] <warning>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.</warning>
[38.4MiB/8.36s] Memory usage: 38.42MB (peak: 180.29MB), time: 8.36s.
[38.4MiB/8.36s] Finished Composer Cloud resolving.
# Cloud Job ID ctWFT94Tk2wnAmk9wXbt4YsFOAM1LALPpqRShjNXBS63KNhu1e 6TrRx00S06qbQaUFJleieb1mECsPKzSrqvR0LDEiyIR failed
vendor/bin/contao-console contao:maintenance-mode enable
composer install --dry-run
vendor/bin/contao-console contao:maintenance-mode disable

**mlweb** · 06.04.2023, 16:19

Das wird auch nicht klappen, wenn Erweiterungen (noch) nicht mit Contao 5 kompatibel sind.
Der Catalog Manager ist m.E. nicht kompatibel mit Contao 5.

Für das trilobit-gmbh/contao-headerfootercode-bundle hat Dir weiter oben schon @minerwalwa geschrieben, dass Du Version 2 benötigst. Du requiererst aber Version 1 in Deiner composer.json.

Wenn die Erweiterungen, die man benötigt noch nicht mit Contao 5 kompatibel sind, dann kann man die Entwickler damit beauftragen die Erweiterung kompatibel zu machen oder man wartet halt noch ab.

**Schnippel** · 06.04.2023, 19:14

Habe alle Erweiterungen (war ne Menge) entfernt.
Trotzdem kommt immer noch diese Fehlermeldung, wo man PHP 7 haben will??? Soll da nicht auf PHP 8 umgestellt werden?

Resolving dependencies using Composer Cloud v3.6.0
[6.9MiB/0.19s] Loading composer repositories with package information
[68.5MiB/6.94s] Updating dependencies
[133.9MiB/7.69s] Your requirements could not be resolved to an installable set of packages.
[133.9MiB/7.70s]
Problem 1
- contao/core-bundle[4.9.0, ..., 4.10.4] require php ^7.2 -> your php version (8.1.13.0) does not satisfy that requirement.
- contao/core-bundle[4.9.10, ..., 4.10.7] require symfony/framework-bundle 4.4.* -> found symfony/framework-bundle[v4.4.0, ..., v4.4.49] but it conflicts with your root composer.json require (^5.4).
- contao/core-bundle[4.11.0, ..., 4.11.9] require symfony/framework-bundle 4.4.* || 5.2.* -> found symfony/framework-bundle[v4.4.0, ..., v4.4.49, v5.2.0, ..., v5.2.12] but it conflicts with your root composer.json require (^5.4).
- Root composer.json requires do-while/contao-backupdb-bundle ^1.5 -> satisfiable by do-while/contao-backupdb-bundle[1.5.0, 1.5.1, 1.5.2, 1.5.3].
- contao/newsletter-bundle 5.0.2 requires contao/core-bundle 5.0.2 -> satisfiable by contao/core-bundle[5.0.2].
- Conclusion: don't install contao/core-bundle 5.0.2 (conflict analysis result)
- contao/newsletter-bundle 5.0.3 requires contao/core-bundle 5.0.3 -> satisfiable by contao/core-bundle[5.0.3].
- Conclusion: don't install contao/core-bundle 5.0.3 (conflict analysis result)
- contao/newsletter-bundle 5.0.4 requires contao/core-bundle 5.0.4 -> satisfiable by contao/core-bundle[5.0.4].
- Conclusion: don't install contao/core-bundle 5.0.4 (conflict analysis result)
- contao/newsletter-bundle 5.0.5 requires contao/core-bundle 5.0.5 -> satisfiable by contao/core-bundle[5.0.5].
- Conclusion: don't install contao/core-bundle 5.0.5 (conflict analysis result)
- contao/newsletter-bundle 5.0.6 requires contao/core-bundle 5.0.6 -> satisfiable by contao/core-bundle[5.0.6].
- Conclusion: don't install contao/core-bundle 5.0.6 (conflict analysis result)
- contao/newsletter-bundle 5.0.7 requires contao/core-bundle 5.0.7 -> satisfiable by contao/core-bundle[5.0.7].
- Conclusion: don't install contao/core-bundle 5.0.7 (conflict analysis result)
- contao/newsletter-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> satisfiable by contao/core-bundle[5.0.8].
- Conclusion: don't install contao/core-bundle 5.0.8 (conflict analysis result)
- contao/newsletter-bundle 5.0.9 requires contao/core-bundle 5.0.9 -> satisfiable by contao/core-bundle[5.0.9].
- Conclusion: don't install contao/core-bundle 5.0.9 (conflict analysis result)
- contao/newsletter-bundle 5.0.10 requires contao/core-bundle 5.0.10 -> satisfiable by contao/core-bundle[5.0.10].
- Conclusion: don't install contao/core-bundle 5.0.10 (conflict analysis result)
- contao/newsletter-bundle 5.0.1 requires contao/core-bundle 5.0.1 -> satisfiable by contao/core-bundle[5.0.1].
- Conclusion: don't install contao/core-bundle 5.0.1 (conflict analysis result)
- do-while/contao-backupdb-bundle[1.5.0, ..., 1.5.3] require contao/core-bundle >=4.9.0,<5.0 -> satisfiable by contao/core-bundle[4.9.0, ..., 4.13.19].
- Only one of these can be installed: contao/core[2.11.0, ..., 2.11.17, 3.0.0, ..., 3.5.40], contao/core-bundle[4.0.0, ..., 4.13.19, 5.0.0, ..., 5.1.2]. contao/core replaces contao/core-bundle and thus cannot coexist with it.
- contao/newsletter-bundle 5.0.0 requires contao/core-bundle 5.0.0 -> satisfiable by contao/core-bundle[5.0.0].
- Root composer.json requires contao/newsletter-bundle 5.0.* -> satisfiable by contao/newsletter-bundle[5.0.0, ..., 5.0.10].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[133.9MiB/7.70s] <warning>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.</warning>
[38.0MiB/7.77s] Memory usage: 37.98MB (peak: 178.96MB), time: 7.78s.
[38.0MiB/7.77s] Finished Composer Cloud resolving.
# Cloud Job ID e0uydhOKKLk68XFplQRchSVP3LIPUTCJlhn3XxIVrL9CFx0SEg azCNwX4QSfSKFYBZZYoobHVJWB3hJDgml71NvcB6kpp failed

**mlweb** · 06.04.2023, 21:06

Zitat von Schnippel

- do-while/contao-backupdb-bundle[1.5.0, ..., 1.5.3] require contao/core-bundle >=4.9.0,<5.0

eine inkompatible Erweiterung ist lt. Fehlermeldung noch drin, nämlich backupdb

**Schnippel** · 07.04.2023, 23:39

Okay, danke. Habe alle Erweiterungen deinstalliert.

Jetzt kommt diese Fehlermeldung mit der composer install:
Unbenannt-6.jpg

Code:

$ /usr/local/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=Europe/Berlin /html/cto_5_1/public/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader
Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Package operations: 4 installs, 51 updates, 3 removals
  - Removing symfony/security-guard (v5.4.22)
  - Removing sensiolabs/ansi-to-html (v1.2.1)
  - Removing contao/installation-bundle (4.13.19)
  - Upgrading contao-components/tinymce4 (5.10.7 => 6.4.1): Extracting archive
  - Installing contao-components/tristen-tablesort (5.3.0): Extracting archive
  - Upgrading symfony/yaml (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/event-dispatcher (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/var-dumper (v5.4.22 => v6.2.8): Extracting archive
  - Downgrading psr/log (2.0.0 => 1.1.4): Extracting archive
  - Upgrading symfony/error-handler (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/dependency-injection (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/filesystem (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/config (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/http-client-contracts (v2.5.2 => v3.2.1): Extracting archive
  - Upgrading symfony/http-client (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/string (v5.4.22 => v6.2.8): Extracting archive
  - Installing twig/string-extra (v3.5.1): Extracting archive
  - Installing masterminds/html5 (2.7.6): Extracting archive
  - Upgrading symfony/dom-crawler (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/uid (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/twig-bridge (v5.4.22 => v6.1.11): Extracting archive
  - Upgrading symfony/twig-bundle (v5.4.21 => v6.1.11): Extracting archive
  - Upgrading symfony/translation (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/password-hasher (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/security-core (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/property-access (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/security-http (v5.4.22 => v6.0.20): Extracting archive
  - Upgrading symfony/security-csrf (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/security-bundle (v5.4.22 => v6.1.12): Extracting archive
  - Upgrading symfony/process (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/monolog-bridge (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/mime (v5.4.21 => v6.2.7): Extracting archive
  - Downgrading egulias/email-validator (4.0.1 => 3.2.5): Extracting archive
  - Upgrading symfony/mailer (v5.4.22 => v6.2.0): Extracting archive
  - Upgrading symfony/intl (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/finder (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/expression-language (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading doctrine/event-manager (1.2.0 => 2.0.0): Extracting archive
  - Upgrading symfony/doctrine-bridge (v5.4.22 => v6.1.11): Extracting archive
  - Upgrading symfony/console (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/asset (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading scheb/2fa-bundle (v5.13.2 => v6.8.0): Extracting archive
  - Upgrading scheb/2fa-trusted-device (v5.13.2 => v6.8.0): Extracting archive
  - Upgrading scheb/2fa-backup-code (v5.13.2 => v6.8.0): Extracting archive
  - Upgrading contao/core-bundle (4.13.19 => 5.0.10): Extracting archive
  - Upgrading contao/calendar-bundle (4.13.19 => 5.0.10): Extracting archive
  - Upgrading contao/comments-bundle (4.13.19 => 5.0.10): Extracting archive
  - Upgrading contao/faq-bundle (4.13.19 => 5.0.10): Extracting archive
  - Upgrading contao/listing-bundle (4.13.19 => 5.0.10): Extracting archive
  - Upgrading symfony/web-profiler-bundle (v5.4.21 => v6.0.19): Extracting archive
  - Upgrading symfony/stopwatch (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/proxy-manager-bridge (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading symfony/dotenv (v5.4.22 => v6.2.8): Extracting archive
  - Upgrading symfony/debug-bundle (v5.4.21 => v6.2.7): Extracting archive
  - Upgrading contao/manager-bundle (4.13.19 => 5.0.10): Extracting archive
  - Installing debril/feed-io (v6.0.2): Extracting archive
  - Upgrading contao/news-bundle (4.13.19 => 5.0.10): Extracting archive
  - Upgrading contao/newsletter-bundle (4.13.19 => 5.0.10): Extracting archive
Generating optimized autoload files
contao/manager-plugin: Dumping generated plugins file...
contao/manager-plugin: ...done dumping generated plugins file
Class Contao\ManagerPlugin\PluginLoader located in ./vendor/contao/manager-plugin/src/Resources/PluginLoader.php does not comply with psr-4 autoloading standard. Skipping.
104 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
> @php vendor/bin/contao-setup
In ArrayNode.php line 304:
                                                                               
  Unrecognized option "url_suffix" under "contao". Available options are "bac  
  kend", "backup", "crawl", "csrf_cookie_prefix", "csrf_token_name", "editabl  
  e_files", "error_level", "image", "insert_tags", "intl", "localconfig", "lo  
  cales", "mailer", "pretty_error_screens", "preview_script", "sanitizer", "s  
  earch", "security", "upload_path", "web_dir".                                
                                                                               
Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1
# Process terminated with exit code 1
# Result: General error

Meine composer.json:

Code:

{
    "type": "project",
    "require": {
        "php": "^8.1",
        "contao/calendar-bundle": "5.0.*",
        "contao/comments-bundle": "5.0.*",
        "contao/conflicts": "*@dev",
        "contao/faq-bundle": "5.0.*",
        "contao/listing-bundle": "5.0.*",
        "contao/manager-bundle": "5.0.*",
        "contao/news-bundle": "5.0.*",
        "contao/newsletter-bundle": "5.0.*",
        "symfony/framework-bundle": "^5.4",
        "trilobit-gmbh/contao-headerfootercode-bundle": "^2.0"
    },
    "extra": {
        "contao-component-dir": "assets",
        "symfony": {
            "require": "^4.2"
        },
        "public-dir": "public"
    },
    "scripts": {
        "post-install-cmd": [
            "@php vendor/bin/contao-setup"
        ],
        "post-update-cmd": [
            "@php vendor/bin/contao-setup"
        ]
    }
}

Wie muß man hier weiter verfahren?

**Seefahrer** · 08.04.2023, 06:03

Ich denke, das Symfony Framework Bundle ist auf 5 festgetackert, Contao 5 benötigt Symfony 6.
Die Zeile kann komplett raus, da Contao das in der richtigen Version ohnedies required.
Der Abschnitt in Extra mit Symfony ^4.2 ist auch überflüssig. Ohne diese Anweisungen sollte das Update klappen.

Ach ja, für die Contao Version würde ich ^5.0 eintragen, ansonsten gibt es nur 5.0.x anstatt 5.1 etc.

**Spooky** · 08.04.2023, 08:15

Du hast in deiner config.yml veraltete Einstellungen drin. Die musst du entfernen (siehe die Fehlermeldungen).

Und warum requirest du symfony/framework-bundle in deiner composer.json?

Und warum hast du Contao 5.0.* required? Contao 5.0 hat das Lebensende erreicht, aktualisiere auf Contao 5.1.

**Schnippel** · 12.04.2023, 08:37

Hallo,
vielen Dank für eure Hilfe.

@Spooky

Du hast in deiner config.yml veraltete Einstellungen drin. Die musst du entfernen (siehe die Fehlermeldungen).

Welche Einstellungen müssen da raus bzw. wie abgeändert werden? Die Contao url_suffix?

So schaut meine config.yml aus dem Verzeichnis config aus:

PHP-Code:




contao:

    url_suffix: ""

   

doctrine:

    dbal:

        connections:

            default:

                options:

                    # Depending on the DB driver, the option key is either 1002 (pdo_mysql) or 3 (mysqli)

                    1002: "SET SESSION sql_mode=(SELECT CONCAT(@@sql_mode, ',TRADITIONAL'))"

**lbableck** · 12.04.2023, 08:38

url_suffix muss raus, das kannst du jetzt direkt im Backend einstellen.

**Spooky** · 12.04.2023, 09:00

Die Doctrine Config kannst du ab Contao 4.13 auch entfernen.

**Schnippel** · 12.04.2023, 11:01

Vielen Dank, jetzt hat es geklappt.

Allerdings musste ich noch den Ordner "eigene_Templates" in "eigene-Tamplates" umbenennen, da gabs nochmal diese Fehlermeldung hier:

Code:

Generating optimized autoload files
contao/manager-plugin: Dumping generated plugins file...
contao/manager-plugin: ...done dumping generated plugins file
Class Contao\ManagerPlugin\PluginLoader located in ./vendor/contao/manager-plugin/src/Resources/PluginLoader.php does not comply with psr-4 autoloading standard. Skipping.
110 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
> @php vendor/bin/contao-setup
In ThemeNamespace.php line 52:
                                                                               
  The theme path "eigene_Templates" contains one or more invalid characters:   
  "_"                                                                          
                                                                               
Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1
# Process terminated with exit code 1
# Result: General error

Da es bei bisherigen Contao-Updates mit dem Unterstrich keine Probleme gab, hat mich das beim 5er Update etwas irritiert.

**mlweb** · 12.04.2023, 12:05

Das hängt mit der Namensbildung für die neuen Templates zusammen https://docs.contao.org/dev/framewor...aged-namespace

**Schnippel** · 12.04.2023, 13:44

Oje, jetzt raucht mit bissl der Kopf.

Ich habe "eigene_Templates" in "eigene-Templates" schon umbenannt, und bekomme im Frontend eine Fehlermeldung. In der Logdatei steht das hier drin:

Code:

[2023-04-12T13:33:29.227432+02:00] request.INFO: Matched route "tl_page.2.root". {"route":"tl_page.2.root","route_parameters":{"_token_check":true,"_controller":"Contao\\FrontendIndex::renderPage","_scope":"frontend","_locale":"de","_format":"html","_canonical_route":"tl_page.2","parameters":"","pageModel":{"Contao\\PageModel":[]},"_route":"tl_page.2.root","_route_object":{"Symfony\\Component\\Routing\\Route":[]}},"request_uri":"https://update.internet-projekt-service.de/preview.php/","method":"GET"} []
[2023-04-12T13:33:29.263053+02:00] request.CRITICAL: Uncaught PHP Exception Contao\CoreBundle\Exception\InvalidThemePathException: "The theme path "eigene_Templates" contains one or more invalid characters: "_"" at /html/cto_5_1/vendor/contao/core-bundle/src/Twig/Loader/ThemeNamespace.php line 52 {"exception":"[object] (Contao\\CoreBundle\\Exception\\InvalidThemePathException(code: 0): The theme path \"eigene_Templates\" contains one or more invalid characters: \"_\" at /html/cto_5_1/vendor/contao/core-bundle/src/Twig/Loader/ThemeNamespace.php:52)"} []
[2023-04-12T13:33:29.303974+02:00] messenger.INFO: Sending message Contao\CoreBundle\Messenger\Message\SearchIndexMessage with contao_prio_low sender using Contao\CoreBundle\Messenger\Transport\AutoFallbackTransport {"class":"Contao\\CoreBundle\\Messenger\\Message\\SearchIndexMessage","alias":"contao_prio_low","sender":"Contao\\CoreBundle\\Messenger\\Transport\\AutoFallbackTransport"} []
[2023-04-12T13:33:29.304205+02:00] messenger.INFO: Received message Contao\CoreBundle\Messenger\Message\SearchIndexMessage {"class":"Contao\\CoreBundle\\Messenger\\Message\\SearchIndexMessage"} []
[2023-04-12T13:33:29.306685+02:00] messenger.INFO: Message Contao\CoreBundle\Messenger\Message\SearchIndexMessage handled by Contao\CoreBundle\Messenger\MessageHandler\SearchIndexMessageHandler::__invoke {"class":"Contao\\CoreBundle\\Messenger\\Message\\SearchIndexMessage","handler":"Contao\\CoreBundle\\Messenger\\MessageHandler\\SearchIndexMessageHandler::__invoke"} []

Mein Verzeichnis auf dem Server lautet cto_5_1, also auch mit den Unterstrichen. Muß ich dieses Verzeichnis auch umchreiben in cto-5-1 ? Oder hat die Fehlermeldung damit nichts zu tun?

Die Datei ThemeNamespace.php, da steht in Zeile 52:

Unbenannt-1.jpg

PHP-Code:


<?php



declare(strict_types=1);



/*

 * This file is part of Contao.

 *

 * (c) Leo Feyer

 *

 * @license LGPL-3.0-or-later

 */



namespace Contao\CoreBundle\Twig\Loader;



use Contao\CoreBundle\Exception\InvalidThemePathException;

use Symfony\Component\Filesystem\Path;



class ThemeNamespace

{

    /**

     * Generates a theme slug from a relative path.

     *

     * @throws InvalidThemePathException if the path contains invalid characters

     */

    public function generateSlug(string $relativePath): string

    {

        if (!Path::isRelative($relativePath)) {

            throw new \InvalidArgumentException(sprintf('Path "%s" must be relative.', $relativePath));

        }



        $path = Path::normalize($relativePath);

        $invalidCharacters = [];



        $slug = implode('_', array_map(

            static function (string $chunk) use (&$invalidCharacters) {

                // Allow paths outside the template directory (see #3271)

                if ('..' === $chunk) {

                    return '';

                }



                // Check for invalid characters (see #3354)

                if (0 !== preg_match_all('%[^a-zA-Z0-9-]%', $chunk, $matches)) {

                    $invalidCharacters = array_merge($invalidCharacters, $matches[0]);

                }



                return $chunk;

            },

            explode('/', $path)

        ));



        if (!empty($invalidCharacters)) {

            throw new InvalidThemePathException($path, $invalidCharacters);

        }



        return $slug;

    }



    /**

     * Builds the namespace for a certain theme slug.

     */

    public function getFromSlug(string $slug): string

    {

        return "@Contao_Theme_$slug";

    }



    /**

     * Extracts a theme slug from a given logical name.

     *

     * @return string the theme slug or null if not a theme namespace

     */

    public function match(string $logicalName): string|null

    {

        if (1 === preg_match('%^@Contao_Theme_([a-zA-Z0-9_-]+)/%', $logicalName, $matches)) {

            return $matches[1];

        }



        return null;

    }

}

Im Templates sieht es so hier aus:

Unbenannt-2.jpg

Müssen die einzelnen Templates, wie fe_page.html5 ebenfalls umgeschrieben werden, in fe-page.html5 ?

**mlweb** · 12.04.2023, 14:02

Er meckert ja immer noch den Pfad eigene_Templates an, wenn ich das richtig sehe.
Hast Du den dem Theme zugeordneten Pfad auch entsprechend neu gesetzt?

**Seefahrer** · 12.04.2023, 15:43

Einmal den Symfony Cache leeren hilft bisweilen auch bei Änderungen hinsichtlich templates.

**Schnippel** · 12.04.2023, 19:37

Hast Du den dem Theme zugeordneten Pfad auch entsprechend neu gesetzt?

Ach ja, da war doch was... Danke, jetzt funktioniert es..

Danke für eure Hilfe..

**reindeer** · 04.03.2024, 15:48

Ich möchte Contao von 4.13.37 auf auf 5.3 updaten und habe schon alles Mögliche probiert und komme einfach nicht weiter.
Fehlermeldungen, die ausgegeben werden:

Code:

> Resolving dependencies using Composer Cloud v3.7.0
[7.3MiB/0.25s] Loading composer repositories with package information
[73.3MiB/15.21s] Updating dependencies
[107.0MiB/15.94s] Your requirements could not be resolved to an installable set of packages.
[107.0MiB/15.94s] 
  Problem 1
    - Root composer.json requires contao/calendar-bundle 5.3.* -> satisfiable by contao/calendar-bundle[5.3.0].
    - 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.
  Problem 2
    - Root composer.json requires contao/comments-bundle 5.3.* -> satisfiable by contao/comments-bundle[5.3.0].
    - contao/comments-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.
  Problem 3
    - Root composer.json requires contao/faq-bundle 5.3.* -> satisfiable by contao/faq-bundle[5.3.0].
    - contao/faq-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.
  Problem 4
    - Root composer.json requires contao/listing-bundle 5.3.* -> satisfiable by contao/listing-bundle[5.3.0].
    - contao/listing-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.
  Problem 5
    - Root composer.json requires contao/manager-bundle 5.3.* -> satisfiable by contao/manager-bundle[5.3.0].
    - contao/manager-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.
  Problem 6
    - Root composer.json requires contao/news-bundle 5.3.* -> satisfiable by contao/news-bundle[5.3.0].
    - contao/news-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.
  Problem 7
    - Root composer.json requires contao/newsletter-bundle 5.3.* -> satisfiable by contao/newsletter-bundle[5.3.0].
    - contao/newsletter-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.
[107.0MiB/15.95s] <warning>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.</warning>
[42.5MiB/16.04s] Memory usage: 42.53MB (peak: 197.74MB), time: 16.04s.
[42.5MiB/16.04s] Finished Composer Cloud resolving.

Kann mir da bitte jemand helfen?

**Spooky** · 04.03.2024, 15:49

Hast du alle Pakete zum Update markiert?

**reindeer** · 04.03.2024, 15:53

Ich habe bei Contao Open Source CMS in das Feld 5.3.* gesetzt.
Wie kann ich ALLE Pakete markieren?

**Spooky** · 04.03.2024, 16:01

Zitat von reindeer

Wie kann ich ALLE Pakete markieren?

Jedes Paket einzeln zur Aktualisierung markieren. Danach die Änderungen anwenden. Alternativ kannst du auch die composer.json manuell editieren und danach in der Systemwartung "Composer Update durchführen".

**reindeer** · 04.03.2024, 16:09

Danke, habe das jetzt so probiert, habe auch nicht gewusst, dass ich hierzu ALLE anklicken muss.
Allerdings gibt es neue Fehlermeldung:

Code:

> Resolving dependencies using Composer Cloud v3.7.0
[7.4MiB/0.35s] Loading composer repositories with package information
[95.9MiB/18.50s] Updating dependencies
[208.4MiB/20.11s] Your requirements could not be resolved to an installable set of packages.
[208.4MiB/20.11s] 
  Problem 1
    - symfony/yaml[v4.0.10, ..., v4.4.8] require php ^7.1.3 -> your php version (8.2.16.0) does not satisfy that requirement.
    - symfony/yaml[v5.0.0, ..., v5.0.8] require php ^7.2.5 -> your php version (8.2.16.0) does not satisfy that requirement.
    - contao/tcpdf-bundle[1.2.2, ..., 1.2.3] require symfony/yaml 3.4.* || ^4.1 || ^5.0 -> satisfiable by symfony/yaml[v3.4.0, ..., v3.4.47, v4.1.0, ..., v4.4.45, v5.0.0, ..., v5.4.35].
    - contao/tcpdf-bundle 1.2.1 requires symfony/yaml 3.4.* || ^4.1 -> satisfiable by symfony/yaml[v3.4.0, ..., v3.4.47, v4.1.0, ..., v4.4.45].
    - You can only install one version of a package, so only one of these can be installed: symfony/yaml[2.0.4, ..., v2.8.52, v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.45, v5.0.0, ..., v5.4.35, v6.0.0, ..., v6.4.3, v7.0.0, v7.0.3].
    - contao/calendar-bundle 5.3.0 requires symfony/yaml ^6.4 -> satisfiable by symfony/yaml[v6.4.0, v6.4.3].
    - contao/tcpdf-bundle 1.2.0 requires php ^7.1 -> your php version (8.2.16.0) does not satisfy that requirement.
    - Root composer.json requires contao/calendar-bundle 5.3.* -> satisfiable by contao/calendar-bundle[5.3.0].
    - Root composer.json requires contao/tcpdf-bundle ^1.2 -> satisfiable by contao/tcpdf-bundle[1.2.0, 1.2.1, 1.2.2, 1.2.3].
[208.4MiB/20.11s] <warning>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.</warning>
[60.0MiB/20.26s] Memory usage: 60.03MB (peak: 233.68MB), time: 20.27s.
[60.0MiB/20.26s] Finished Composer Cloud resolving.

Liegt wohl an der PHP-Version?

**Spooky** · 04.03.2024, 16:11

Nein, du hast das contao/tcpdf-bundle immer noch required - das gibt es in Contao 5 nicht mehr.

**reindeer** · 04.03.2024, 16:17

Habe es entfernt, jetzt diese Fehler:

Code:

> Resolving dependencies using Composer Cloud v3.7.0
[7.3MiB/0.42s] Loading composer repositories with package information
[95.7MiB/18.56s] Updating dependencies
[208.0MiB/20.48s] Your requirements could not be resolved to an installable set of packages.
[208.0MiB/20.49s] 
  Problem 1
    - symfony/http-foundation[v4.4.0, ..., v4.4.8] require php ^7.1.3 -> your php version (8.2.16.0) does not satisfy that requirement.
    - oveleon/contao-cookiebar[1.9.4, ..., 1.14.1] require symfony/http-foundation ^4.4 || ^5.2 -> satisfiable by symfony/http-foundation[v4.4.0, ..., v4.4.49, v5.2.0, ..., v5.4.35].
    - oveleon/contao-cookiebar[1.9.0, ..., 1.9.3] require symfony/http-foundation 4.4.* || 5.2.* -> satisfiable by symfony/http-foundation[v4.4.0, ..., v4.4.49, v5.2.0, ..., v5.2.14].
    - You can only install one version of a package, so only one of these can be installed: symfony/http-foundation[v2.1.0, ..., v2.8.52, v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.49, v5.0.0, ..., v5.4.35, v6.0.0, ..., v6.4.4, v7.0.0, v7.0.3, v7.0.4].
    - contao/calendar-bundle 5.3.0 requires symfony/http-foundation ^6.4 -> satisfiable by symfony/http-foundation[v6.4.0, v6.4.2, v6.4.3, v6.4.4].
    - Root composer.json requires contao/calendar-bundle 5.3.* -> satisfiable by contao/calendar-bundle[5.3.0].
    - Root composer.json requires oveleon/contao-cookiebar ^1.9 -> satisfiable by oveleon/contao-cookiebar[1.9.0, ..., 1.14.1].
[208.0MiB/20.49s] <warning>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.</warning>
[59.8MiB/20.60s] Memory usage: 59.84MB (peak: 233.34MB), time: 20.61s.
[59.8MiB/20.60s] Finished Composer Cloud resolving.

**Spooky** · 04.03.2024, 16:18

Du hast oveleon/contao-cookiebar in Version 1.x installiert, die ist nicht mit Contao 5 kompatibel. Du musst wenn dann ^2.0@RC requiren.

**reindeer** · 04.03.2024, 16:36

Ja, jetzt ist es durchgelaufen.
Allerdings habe ich noch ein Problem bei den Datenbank-Änderungen:

Code:

Feld tl_search.url ändern

VARCHAR(2048) CHARACTER SET ascii DEFAULT '' NOT NULL COLLATE `ascii_bin`
Feld tl_search.protected ändern

TINYINT(1) DEFAULT 0 NOT NULL

Das ist jetzt in einer Endlosschleife, das heißt der Befehl kommt immer wieder, wird aber nicht ausgeführt.

**Spooky** · 04.03.2024, 16:38

Welche MySQL/MariaDB Version? Hast du noch eine database_version bzw. server_version Parameter in deiner parameters.yml oder .env.local?

**reindeer** · 04.03.2024, 16:53

Datenbank:
Server-Version: 10.1.48-MariaDB-0ubuntu0.18.04.1 - Ubuntu 18.04

In der config.yml steht:

Code:

doctrine:
    dbal:
        connections:
            default:
                default_table_options:
                    engine: InnoDB
                    charset: utf8
                    collate: utf8_unicode_ci
                options:
                    1002: "SET SESSION sql_mode=(SELECT CONCAT(@@sql_mode, ',TRADITIONAL'))"