Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
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.
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 "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.
- Leave open but stop new automated patches.
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.
- Close it and don't use it
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.
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 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 |
|---|---|---|---|
| #10 | 14269188-add-theme-10.patch | 512 bytes | energee |
| #2 | sitemap.2.x-dev.rector.patch | 1.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.6, 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 #4
akalata commentedComment #5
bramdriesenShould be set to fixed?
Comment #6
bramdriesenI'm sorry to be a bit negative, but this issue queue is a mess, so many issues that are being fixed without patches being provided, no reviews and so many cross references. It's difficult to see the forrest between all the trees (dutch saying).
#3036687 was closed over a year ago, yet the errors are there.
Comment #7
bramdriesenReferencing issue. This is a major critical issue in order to move to Drupal 9.
Comment #8
akalata commentedHi Bram. This issue is specifically for the Automated compatibility fixes provided by the Drupal Rector tool as noted in the Issue Summary and comment #1. It was left Active since there may be additional patched provided by the bot, and we want to have a consistent place to be open for them.
In response to your feedback on the issue queue, I'm the only one working on this module, so if I waited for reviews I'd be waiting awhile. The high majority of activity from others has been fishing for commit credits by patching code style issues. Closed issues should at least have commits referenced.
If you could open a new issue for this, I'm happy to work on it with you. How did you generate the report that you included?
Comment #9
energee commentedThere is a D9 compatibility issue, present in 2.x and 2.0-beta2.
A default theme must be present in unit tests:
Comment #10
energee commentedComment #11
kristen polThis may be duplicate as the module is already D9 compatible but I haven't looked at the details.
Comment #12
kristen polComment #14
akalata commentedThanks @energee!