Automated Drupal 11 compatibility fixes for commerce_stock

This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.

It is important that any automated tests available are run and that you manually test the changes.

Drupal 11 Compatibility

According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.

Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.

Therefore these changes did not update the info.yml file for Drupal 11 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

Debug info

This patch was created using these packages:

1. drupal/upgrade_status: 4.1.0
2. mglaman/phpstan-drupal: 1.2.7
3. palantirnet/drupal-rector: 0.20.1

This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.

This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

It is important that any automated tests available are run and that you manually test the changes.

Drupal 11 Compatibility

According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.

Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.

Therefore, these changes did not update the info.yml file for Drupal 11 compatibility.

The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.

Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

Debug information

These packages were used to generate the fixes:

1. drupal/upgrade_status: 4.1.0
2. mglaman/phpstan-drupal: 1.2.10
3. palantirnet/drupal-rector: 0.20.1

Can we get this merged to dev release?

will give it a test and commit

This is an important commerce module. It would be great if you could create a D11 compatible release with Commerce 3.0.x support (see the second issue). Thanks!

I have created a new MR !30 and moved here (hopefully) all required changes (this includes the changes from project update bot, 🐛 The spaceless tag was removed in Twig Active , EntityReferenceTestTrait deprecation and toRenderArray deprecation). Given the EntityReferenceTestTrait deprecation, I had to remove compatibility for Drupal 10.1 and lower (unless we want to add some exceptions/special checks), so I think that this probably should go to a new branch, instead of 8.x-1.x.

vipin.j → made their first commit to this issue’s fork.

4b4f933a does not apply cleanly
ae993fcb is not required in this issue, it should be moved to a separate one

By adding the following to the config section in composer.json the original patch by poker10 applies cleanly and Upgrade Status says the module is compatible:

  "preferred-install": {
      "drupal/commerce_stock": "source",
      "*": "auto"
  },

intrafusion → changed the visibility of the branch project-update-bot-only to hidden.

intrafusion → changed the visibility of the branch 3428501-automated-drupal-11 to hidden.

Enable module of this branch in Drupal 11 occurs error: Route "commerce_stock.admin_settings" does not exist.

Big thank you @poker10 @kent @vipinj @intrafusion @valic for the amazing work on this.
Tested and so far found not a single issue :)
pushed as 3.0.0-beta1 will test on some production projects and if no issues are reported in the next few weeks we can go 3.0.

Automatically closed - issue fixed for 2 weeks with no activity.