![]() ![]() Installation request for drupal/core (locked at 9.0.9) -> satisfiable by drupal/core. drupal/commerce_migrate 2.0.0-rc1 requires drupal/core ^8.7 -> satisfiable by drupal/core. Conclusion: don't install drupal/core 9.0.9 Installation request for drupal/commerce_migrate -> satisfiable by drupal/commerce_migrate. Conclusion: don't install drupal/commerce_migrate 2.0.0-rc2 Conclusion: don't install drupal/commerce_migrate 2.0.0-rc3 For example, before commerce_migrate was compatible with Drupal 9 (update: it is now!), when I tried applying the necessary patch this way, composer just gave me an enormous and confusing error: Your requirements could not be resolved to an installable set of packages. ![]() So for contrib modules that haven't yet committed their patches, attempting to apply the patch in the usual way doesn't help. But the tool most of us use with composer to apply patches, cweagans/composer-patches, is a plugin that can only make its changes after composer reads a package's metadata about its compatibility (and dependencies). The vast majority of community-contributed Drupal 8 modules now have releases that are compatible with Drupal 9, but what can you do if you need to use a module that doesn’t? Well, you’re likely to find a compatibility patch in the project's issue queue. The rest of this article is still useful for understanding how patching fits into composer's workflow. See the documentation, which boils down to adding a new common entry under 'repositories' in your composer.json, above the usual one. Update! Since this article was written, a new 'lenient' composer endpoint has been created on to support using modules with Drupal 9 that haven't been marked as compatible with it yet. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |