Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 9.
To read more about this effort by the Drupal Association, please read: Accelerating Drupal 9 module and theme readiness with automated patches
Periodically patches will be added to this issue that remove Drupal 9 deprecations. To stop further patches from being posted simply close this issue(any status besides Active, Needs Review or Needs work) or remove the "ProjectUpdateBotD9" tag from the issue.
The patches will be posted by the Project Update Bot official user account. This account will not receive any issue credit contributions for itself or any company.
You have a few options for how to use this issue:
If this issue is left open(status of Active, Needs Review or Needs work) and the "ProjectUpdateBotD9" tag is left on this issue, new patches will be posted periodically if new deprecations are needed.
As the Drupal Rector project improves and is able to fix more deprecations the patches posted here will cover more of the deprecations in the module.
If you want to use this issue as a starting point to remove deprecations but don't want new automated patches simply leave this issue open but remove the "ProjectUpdateBotD9" from the issue.
You can use Drupal Rector yourself to make these patches.
If you want to receive automated patches again simply add back the "ProjectUpdateBotD9" tag.
If the maintainers of this project don't find this issue useful they can simply close this issue(any status besides Active, Needs Review or Needs work) and no more automated patches will be posted here.
If the issue is reopened then new automated patches will be posted.
If you are using another issue(s) to work on Drupal 9 compatibility it may be useful to other contributors to add those issues as "Related issues" when closing this issue.
Using the patches
If there are problems with one of the patches posted by the Project Update Bot, such as it does not correctly replace a deprecation, you can file an issue in the Rector issue queue. For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Infrastructure project issue queue using the component “Bot: Drupal Rector”.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 3146791-commerce-license-d9-readiness-5.patch | 5.95 KB | mrweiner |
| #2 | commerce_license.2.x-dev.rector.patch | 5.52 KB | project update bot |
Comments
Comment #2
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 9 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 9.
Currently Drupal-Rector, version 0.5.5, cannot fix all Drupal 9 compatibility problems.
This patch does not update the
info.ymlfile for Drupal 9 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 9 compatibility fixes as they become available in Drupal-Rector.
Debug info
This patch was created using these packages:
Comment #3
devoleksiy commentedHow to fix this patch, I want to use on the new drupal 9?
Comment #4
mrweiner commentedThe generated patch pretty much just replaces instances of drupal_set_message() with \Drupal::messenger() so it shouldn't cause any problems at all. Still applying fine on my end. It is not responsible for the failed test as the current dev branch is also registering the same failures.
Comment #5
mrweiner commentedUpdated patch to also handle the .info.yml file.
Comment #8
jsacksick commentedSince the patch was committed, I guess we can mark this issue as "fixed".