Dependency "composer/installers" is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
I'm updating a Drupal application from 8.6.3 to 8.9.13. We have some customizations to the default.settings.php file in 8.6.3.
In order to update from 8.6.3 to 8.9.13 directly, what is the best way to check for changes to the default.settings.php file? Do I need to read the release notes of every Drupal minor/patch release between 8.6.3 and 8.9.13?
Also, if there are changes to the default.settings.php, should I recreate the settings.php file for our application from the latest 8.9.13 default.settings.php and add the customizations?
I'm trying to upgrade Drupal 8.9.13 to 9.0.11. I have upgraded all contributed and custom modules to supports Drupal 9. When I try to upgrade core, got below error
I've run into a mystery issue that got me scratching my head. I received a notification saying there is a new update for D7, the new 7.79 version. I performed the update to two of my sites, but immediately after, the "Available Updates" page takes forever to load, and when it does load, all the projects show "Failed to get available update data.", all grey.
I tried clearing the cache in the Drupal install but it didn't do much.
I'm a long time Drupal user (I think since about 4.x) and I've slowly upgraded my (personal blog) site over time to the latest versions.
I'm sitting on my Drupal 8 install and looking to go to 9, because I'm aware that D8 will become end of life oneday in the not so distant future.
Holy hell has everything changed! I don't keep up to date with Drupal on a day-to-day basis, so this whole Composer thing has sort of snuck up on me. I've seen mention of it now and then in modules I've used, but I didn't realise it was now part of Drupal's DNA.