Problem/Motivation
Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 10.
To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects
Periodically patches will be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted simply close this issue (any status besides Active, Needs review or Needs work) or remove the "ProjectUpdateBotD10" 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.
Proposed resolution
You have a few options for how to use this issue:
- Accept automated patches until this issue is closed
If this issue is left open (status of Active, Needs review or Needs work) and the "ProjectUpdateBotD10" tag is left on this issue, new patches will be posted periodically if new deprecation fixes are needed.
As the Drupal Rector project improves and is able to fix more deprecated API uses, the patches posted here will cover more of the deprecated API uses in the module.
- Leave open but stop new automated patches.
If you want to use this issue as a starting point to remove deprecated API uses but don't want new automated patches simply leave this issue open but remove the "ProjectUpdateBotD10" tag from the issue.
You can use Drupal Rector yourself to make these patches.
If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.
- Close it and don't use it
If the maintainers of this project don't find this issue useful, they can 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 10 compatibility it may be useful to other contributors to add those issues as "Related issues" when closing this issue.
Remaining tasks
Using the patches
- Apply the patch in the comment by Project Update Bot.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
Providing feedback
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 Drupal 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 |
|---|---|---|---|
| #2 | cookies.1.1.x-dev.rector.patch | 787 bytes | project update bot |
Issue fork cookies-3305264
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
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 10 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.13.1, cannot fix all Drupal 10 compatibility problems.
This patch does not update the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #3
anybodyDrupal 10 is close - the community should ensure 1.1.x works with Drupal 10.
With 2.x we'll drop old dependencies and propably use vue, but 1.1.x should be compatible.
Comment #4
anybody@Grevil could you please check 1.1.x for Drupal 10 compatibility, creating a MR from the given patch and implement other required changes please?
Comment #7
grevil commentedDone! I also fixed the php coding standard issues while I was at it :)
Comment #8
anybodyGreat work! I left some comments to resolve. The hardest part will be the conflicts, I guess due to the changed descriptions.
Please ensure nothing gets lost.
Afterwards this can be merged!
Comment #9
anybodyPS: Nice, tests are also passing! :party:
Comment #10
grevil commentedOK, all cleaned up now! Let's wait for the tests to pass.
Comment #11
grevil commentedAll green! We can safely commit this! :)
Comment #13
grevil commentedSince I don't think any more compability issues will arise, as the D10 release is pretty soon, I am going to close this issue.
Comment #14
grevil commentedFor some reason, I forgot to change the core_version_requirements for the submodules...
Comment #16
grevil commentedFixed again.
Comment #17
anybody@Grevil please set ^8 to ^8.9 to make this safer. So we still support the latest Drupal 8 version (which EOL since long time), but no more older versions.
Comment #19
grevil commentedsry, also added ^8.9
Comment #21
grevil commentedTests should be fixed again, sorry no more direct commits on dev...
Tests failed because of the still existing "core" key in the info ymls.