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 |
|---|---|---|---|
| #9 | Screenshot from 2022-08-08 13-27-52.png | 179.73 KB | sharayurajput |
| #2 | boldy.2.x-dev.rector.patch | 2.05 KB | project update bot |
Issue fork boldy-3296666
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.0, 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 #4
sharayurajput commentedI will review this patch
Comment #5
sharayurajput commentedThis module seems compatible for drupal 10 when we see its code
But when we try to enable this module its not visible in the extend tab
so moving status to needs work
Comment #6
the_g_bomb commentedThanks for checking. Please try again, but realise this is a theme. It can be enabled and set as default at: /admin/appearance
or by using the following drush commands:
Comment #7
sharayurajput commentedOk @the_g_bomb I will try it
Comment #8
sharayurajput commentedComment #9
sharayurajput commentedYes This theme is compatible with drupal 10 and working properly also provided screenshot LGTM
Comment #10
sharayurajput commentedSo moving status to RTBC
Comment #11
the_g_bomb commentedMoving back to an open status so that new patches will be posted periodically if new deprecation fixes are needed.
Comment #13
shivam_tiwari commentedTheme is already compatible with D10. I checked with branch 8.x-2.x with upgrade status. Please check and let me know if any issue.
Comment #14
Bushra Shaikh commentedComment #15
Bushra Shaikh commentedVerified patch #2 on Drupal 9.4.x and Checked using Upgrade Status.
I found 1 error in the code while checking deprecated code
Comment #17
the_g_bomb commentedThanks for highlighting Bushra Shaikh. I have fixed the typo.
The patch provided by drupal rector has been merged to the 8.x-2.x branch.
No more testing is required on this ticket until Drupal Rector provides more updates.
This ticker is remaining open to allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Comment #18
the_g_bomb commentedI have created a new release tag which will mean composer will install the latest D10 supported verison now with all the changes made here.
No more testing is required on this ticket until Drupal Rector provides more updates.
This ticket will remaining open to allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Comment #19
the_g_bomb commentedNot sure there will be any more Update Bot additions