![]() ![]() I also look at this list and think, I'm not using Configuration Installer, so I should remove that. Simple OAuth is also very important so I should update to the latest version of that and run these checks again. In my case the Group module is super important to what I'm doing, so I'll start by seeing what if anything I can do to contribute to getting that module Drupal 9 ready first. Once my custom code is ready to go I can pretty quickly see that state of the different contributed projects I'm using, and which ones are most likely to benefit from my helping out. I think the biggest win for me using Upgrade Status is that it helps illustrate where I should be spending my time. Because the module caches the results of each scan you can use Drush to run a scan and still view the detailed report via the module's UI. Or use one of the included Drush commands. This can be done either by navigating to the report page at Reports > Upgrade status then checking the box for each project you want to scan and pressing Scan selected at the bottom of the page. You need to tell Upgrade Status to scan your project(s) before it can provide detailed reports. Note: After installing have Drupal run its Update status checks again ( Reports > Update status). Upgrade Status uses this to determine what version of the module you're currently using.Īnyway, if you use Composer to manage your project adding Composer Deploy won't make things any worse and may make them better: composer require drupal/composer_deploy The reason you need these is because modules installed via either Composer (in some cases) or via Git don't contain the version key in their *.info.yml files that gets added automatically by. "drupal/migrate_source_directory": "1.x-dev" or projects that have been added by cloning their Git repository, then you can install the respective optional helper module to ensure Upgrade Status can find the information it needs for those projects. If you've got projects installed via Composer where the required version is a -dev version (e.g. The project page mentions the optional Composer deploy, and Git deploy, modules. ![]() Install it (I recommend you do so on a development environment) using Composer: composer require 'drupal/upgrade_status:^2.0' Some modules, like for example Recurly in the example above, provide detailed Drupal 9 roadmaps (Note: maintainers, you can add this via your project page!), that help indicate where things are at."Consumers >= 8.x-1.11 is compatible with Drupal 9.": There's a newer version of the module than the one I have installed and it is Drupal 9 ready.If not, you can trigger one manually at Reports > Update status. Note that if this column lists N/A for everything make sure you've got the Update Manager enabled and that it's run a status check recently. If there's a version number this means you're currently using an out-of-date version of the project and should upgrade. The Available update column will show either Up-to-date or a version number.This list provides the same link to see a detailed report as above, and a bunch of additional information as well. Note that Upgrade Status only scans enabled projects. This is followed by a report on all the contributed projects you have enabled. ![]() Then it pulls this all into a nice visual report like the example below, complete with links to both issues and documentation to help you best resolve the issues it finds.
0 Comments
Leave a Reply. |