![]() Your requirements could not be resolved to an installable set of packages. When you run composer install, you might get an error like the following: Updating to composer 2 may result in errors depending on the packages that you are using. ![]() In our lando.yml, we can explicitly specify the composer version as follows: services: In our case, we are using Lando, so let’s refer to the documentation on how to choose a composer version in Lando. If you have the composer version specified in your docker container, you might need to set it up there. First we update composer itself: composer selfupdate -2 One fundamental step was to update to Composer 2. You can access your upgrade report at v/admin/reports/upgrade-status. Index individual projects: drush us-a project_a project_b ![]() Run a full index from the command line: drush us-a -all It takes a while to scan all modules, but the UI is really helpful in identifying what is left for you to do. To get started, I used Upgrade Status to analyse and keep track of the Drupal 9 readiness of the site. Keep track of Drupal 9 compatibility using Upgrade Status Most contributed modules are Drupal 9 ready and only a few exotic modules required me to work on a reroll of a Drupal 9 compatibility patch. As you might expect, updating from Drupal 8 to Drupal 9 involves very little steps on the application layer. In this blog post I would like to share some of the learnings I had while completing the upgrade. Recently, I had the opportunity to upgrade one of our projects from Drupal 8 to Drupal 9. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |