Problem/Motivation
This patch provides Drupal 11 compatibility for the Schema.org Blueprints Commerce module and all its submodules by updating version requirements in the .info.yml files and composer.json.
Steps to reproduce
Try to install the Schema.org Blueprints Commerce module with Drupal 11
You'll notice the module will report incompatibility with Drupal 11
Proposed resolution
The attached patch updates:
The main module's composer.json to require drupal/core: ^10.3 || ^11.0
All .info.yml files (main module and submodules) to have core_version_requirement: ^10.3 || ^11.0
Actual behavior
Currently, the module reports as incompatible with Drupal 11.
Expected behavior
After applying this patch, the module will be recognized as compatible with both Drupal 10.3+ and Drupal 11.
Additional information
I've tested this patch with Drupal 11.1.8 and found no issues. The module's code already follows best practices (strict typing, proper type hints, etc.) and doesn't use any APIs removed in Drupal 11.
| Comment | File | Size | Author |
|---|---|---|---|
| drupal11-compatibility.patch | 5.36 KB | dan_metille |
Issue fork schemadotorg_commerce-3529240
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
nicolasgraphComment #3
anybodyCurrently the module isn't usable with Drupal 11 due to the composer dependencies.
I'm not sure if the given patch is enough and we should follow the steps described here: https://www.acquia.com/blog/upgrade-to-drupal-11 to make it fully D11 compatible.
Comment #8
anybody