Update 4.13.43 auf 5.0.10 ... wie funktioniert das?

[d003232]

Ich möchte endlich von Version 4 auf Version 5 Updaten. Wobei ich noch unsicher bin, ob das überhaupt schon notwendig ist oder Sinn macht? Da ist immer die Befürchtung dabei, etwas zu zerhauen.

Trotzdem habe ich es nun gewagt. Alles vorher gesichtert. Laut Migrationsdoku die Versionsanforderung von 4.13.* auf 5.0.* umgestellt. Einmal in der composer.json, dann auch direkt im Contao Manager. In beiden Fällen funktioniert der Update nicht. Ich bekomme auf der Console die Fehlermeldung:

$ /opt/RZphp81/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=CET /mnt/web121/a2/00/51140000/htdocs/scheuermatthof_de/contao-prod/public/contao-manager.phar.php composer require contao/manager-bundle=5.0.* --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction

/mnt/web121/a2/00/51140000/htdocs/scheuermatthof_de/contao-prod/composer.json has been updated

# Process terminated with exit code 0
# Result: OK


> Resolving dependencies using Composer Cloud v3.7.0

[6.7MiB/0.25s] Loading composer repositories with package information
[88.7MiB/11.11s] Updating dependencies
[149.1MiB/11.71s] Your requirements could not be resolved to an installable set of packages.
[149.1MiB/11.71s] 
  Problem 1
    - contao/manager-bundle 5.0.0 requires contao/core-bundle 5.0.0 -> found contao/core-bundle[5.0.0] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.1 requires contao/core-bundle 5.0.1 -> found contao/core-bundle[5.0.1] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.2 requires contao/core-bundle 5.0.2 -> found contao/core-bundle[5.0.2] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.3 requires contao/core-bundle 5.0.3 -> found contao/core-bundle[5.0.3] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.4 requires contao/core-bundle 5.0.4 -> found contao/core-bundle[5.0.4] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.5 requires contao/core-bundle 5.0.5 -> found contao/core-bundle[5.0.5] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.6 requires contao/core-bundle 5.0.6 -> found contao/core-bundle[5.0.6] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.7 requires contao/core-bundle 5.0.7 -> found contao/core-bundle[5.0.7] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.9 requires contao/core-bundle 5.0.9 -> found contao/core-bundle[5.0.9] but these were not loaded, likely because it conflicts with another require.
    - contao/manager-bundle 5.0.10 requires contao/core-bundle 5.0.10 -> found contao/core-bundle[5.0.10] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires contao/manager-bundle 5.0.* -> satisfiable by contao/manager-bundle[5.0.0, ..., 5.0.10].

[149.1MiB/11.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.
[54.4MiB/11.79s] Memory usage: 54.39MB (peak: 218.52MB), time: 11.8s.
[54.4MiB/11.79s] Finished Composer Cloud resolving.


# Cloud Job ID 4a2m4trRtEvJ4UuREf2kuc6ksBUhDbJQs5Lyp5NJ0emKCJgA2slPaYutgNuzr3h0k3DYpUI7aogLWXRrQZ14evoYnDvNYDmwG7a4LpjPAcd11Lj04zXm1kisLMo5V failed

Was mache ich falsch? Ich habe drei Erweiterungen aktiv:
-mmenu - Mobile Navigation für Contao
- RockSolid Slider
- Contao Cookiebar

Für alle Erweiterungen gibt es wohl auch Versionen für Contao 5. Muss ich die Erweiterungen erst einmal deaktvieren und nach dem Update auf Contao 5 auch updaten? Fall ja wie das, ohne dass Daten & Einstellungen verlorgen gehen?

Wer kann mir einen Tipp geben?

[zoglo]

Poste den Inhalt deiner composer.json.
Zusätzlich ist Contao 5.0.10 veraltet, du musst auf Contao 5.3 aktualisieren.

[neelix]

Deaktivieren must du die Erweiterungen nicht. Nur sicherstellen, dass Composer eine kompatible Version installieren darf. Und dann nicht nur einfach "Änderungen anwenden", sondern "Alle Pakete aktuallisieren", damit Composer alle Abhängigkeiten neu auflöst.

[d003232]

OK. Mein Hauptfehler war wohl, dass ich nur "Änderungen anwenden" statt "Alle Pakete aktualisieren" ausgewählt habe.

Wenn ich nun "Alle Pakete aktualisieren" auswähle laufe ich in einen neuen Composer Fehler. Ich habe im Composer die Bedingungen wie folgt eingestellt:
- Core: 5.3.*
- mmenu - Mobile Navigation für Contao: ^4.1
- Contao Cookiebar: ^2.0

Danach zerhaut es mir offenbar den Composer:

$ /opt/RZphp81/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=CET /mnt/web121/a2/00/51140000/htdocs/scheuermatthof_de/contao-prod/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.
Nothing to install, update or remove
Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
Generating optimized autoload files
Class Contao\ManagerPlugin\PluginLoader located in ./vendor/contao/manager-plugin/src/Resources/PluginLoader.php does not comply with psr-4 autoloading standard. Skipping.
contao/manager-plugin: Dumping generated plugins file...
contao/manager-plugin: ...done dumping generated plugins file
105 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 327:
                                                                               
  Unrecognized option "legacy_routing" under "contao". Available options are   
  "backend", "backup", "console_path", "crawl", "cron", "csp", "csrf_cookie_p  
  refix", "csrf_token_name", "editable_files", "error_level", "image", "inser  
  t_tags", "intl", "localconfig", "locales", "mailer", "messenger", "pretty_e  
  rror_screens", "preview_script", "sanitizer", "search", "security", "upload  
  _path".                                                                      
                                                                               
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

und beim Wiederherstellen im 1. Versuch nochmal:

In ArrayNode.php line 327:
                                                                               
  Unrecognized option "legacy_routing" under "contao". Available options are   
  "backend", "backup", "console_path", "crawl", "cron", "csp", "csrf_cookie_p  
  refix", "csrf_token_name", "editable_files", "error_level", "image", "inser  
  t_tags", "intl", "localconfig", "locales", "mailer", "messenger", "pretty_e  
  rror_screens", "preview_script", "sanitizer", "search", "security", "upload  
  _path".

erst danach läuft gottseidank wieder alles. Aber natürlich weiterhin Version 4.3.*

[lbableck]

Du musst die legacy_routing Einstellung aus deiner config.yml entfernen, die gibts in Contao 5 nicht mehr da das Legacy Routing komplett entfernt wurde.

[d003232]

Du musst die legacy_routing Einstellung aus deiner config.yml entfernen, die gibts in Contao 5 nicht mehr da das Legacy Routing komplett entfernt wurde.

Das war es. Nun ging der Update komplett durch.

Vielen Dank!