Upgrading to drupal 98/2/2023 ![]() This approach is also an option if you want to completely refresh your old content and start from scratch. This may save time and money if the time it takes to manually re-create the content in the upgrade site is less than the time it would take a developer to configure the migration scripts to map fields from the old site to the new site. If you want to install modules that are not yet compatible with Drupal 9 but there are patches available to make them compatible, then you can use Drupal's Lenient Composer endpoint.If the website you’re re-building is fairly small and has a small amount of content, you may want to do a manual migration. ![]() But that's probably not such a good idea. Composer 2 backward compatibilityĬomposer 2 is backward compatible with Composer 1, so in theory, you can use Composer 2 on your machine while your teammates and/or CI/CD tools still use version 1. Swift Mailer library is no longer maintained, so if you are using the Swift Mailer module that depends on it, you should stop using it and switch to the Symfony Mailer module. Issue #7 - swiftmailer/swiftmailer Package "swiftmailer/swiftmailer" is abandoned, you should avoid using it. If for some reason you need it, you may continue to use it, just update to version 2.x. This plugin was deprecated in Drupal 8.8.0 and removed in Drupal 9. Issue #6 - wikimedia/composer-merge-plugin The "wikimedia/composer-merge-plugin" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). Just ignore it, and wait for Drush maintainers to fix it. The package is abandoned because it's been merged into the Symfony Filesystem package, so it's not maintained anymore.ĭrush requires it, so there's nothing you can do to fix this warning. Issue #5 - webmozart/path-util Package "webmozart/path-util" is abandoned, you should avoid using it. The doctrine/reflection package is abandoned and is no longer maintained, and that's why Drupal core is no longer using it. The package will stay in Drupal 9 and will be removed before Drupal 10 is released. The code from the package has been copied to Drupal core per this change record. Issue #4 - doctrine/reflection Package "doctrine/reflection" is abandoned, you should avoid using it. To get Composer 2 support, you have to update the plugin to at least version 8.9.x. Versions 8.8.x and older of this plugin support only Composer 1. You may need to run composer update with the "-no-plugins" option. To fix the issue update the plugin to version 1.2.0 which supports Composer 2, or even better since it actually doesn't do anything just remove it from your project by running: composer remove zaporylie/composer-drupal-optimizations Issue #3 - drupal/core-composer-scaffold The "drupal/core-composer-scaffold" plugin was skipped because it requires a Plugin API version ("^1.0.0") that does not match your Composer installation ("2.1.0"). Composer's speed is no longer an issue in version 2, so using this plugin is not needed. And this composer plugin speeds things up at least a bit. You may need to run composer update with the "-no-plugins" option.Ĭomposer 1 is slow when used in big projects with a lot of dependencies. Issue #2 - zaporylie/composer-drupal-optimizations The "zaporylie/composer-drupal-optimizations" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.1.0"). Versions 1.6.7 and older support only Composer 1, so before you upgrade Composer to version 2, you have to upgrade cweagans/composer-patches package to version 1.7.0 or newer. If you upgrade Composer from version 1 to version 2 and you get this error message while running composer update or composer require commands, that means that you have an old version of cweagans/composer-patches package. ![]() ![]() Issue #1 - cweagans/composer-patches The "cweagans/composer-patches" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.1.0"). I didn't want to update that article with these specific issues as it is already quite long. I've written a detailed article on how to upgrade Drupal 8 to 9, so you can check that if you want to get a general overview of the upgrade process. This article will explain how to deal with some specific and concrete issues you might encounter during the upgrade to Drupal 9 and Composer 2.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |