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
Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.
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, Needs work or Reviewed and tested by the community) 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.
Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.
- Leave open but stop new automated patches.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). 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, Needs work and Reviewed and tested by the community) 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 would be very useful to other contributors to add those issues as "Related issues" when closing this issue.
Remaining tasks
Using the patches
- Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
- Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.
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 Project analysis issue queue.
| Comment | File | Size | Author |
|---|---|---|---|
| #27 | 3288770-27.patch | 1.16 KB | bobooon |
| #26 | 3288770-26.patch | 1.07 KB | bobooon |
| #25 | 3288770-25.patch | 1.07 KB | bobooon |
| #18 | 3288770-18.patch | 1.17 KB | bobooon |
| #17 | node_access_rebuild_progressive_d10.patch | 1.59 KB | energee |
Issue fork node_access_rebuild_progressive-3288770
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 this patch makes this module compatible with Drupal 10! 🎉
This patch updates 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
project update bot commentedUpdating bot issue summary.See #3313904: Update project bot templates for RTBC status support and human interaction tips
Comment #4
prudloff commentedModuleHandlerInterface::getImplementations()is deprecated.Comment #5
eelkeblokIt's probably a good idea to set the core_version requirement to ^9.4 || ^10 since getImplementations was only deprecated in 9.4.
Comment #6
eelkeblokHere is a version of the patch without the changes to info.yml, so you can apply it using composer-patches. Running the patched module on D10 should e possible with https://www.drupal.org/project/backward_compatibility. Note that this is not intended to be the actual patch to resolve this issue.
Comment #7
nishavaghela commentedI have applied and tested the patch in comment #4 , it is getting applied successfully.
There are no drupal check and upgrade status errors found , also the module in compatible to D10 .
Thus moving the issue to RTBC.
Comment #8
bob.hinrichs commentedA release with d10 compatibility would be welcome!
Comment #9
gaëlgComment #5 has not be addressed.
Comment #10
sourabhjainI have addressed the point mentioned in #5. Please review.
Comment #11
gaëlgThank you.
There's a problem in latest patch.
To explain what eelkeblock said: with the code change from prudloff, we now call
hasImplementations(). But this method does not exist before Drupal 9.4.So yes, we must require 9.4+ or 10+, but we cannot accept 8 anymore or we will face this kind of issue: #3295521: Call to undefined method Drupal\Core\Extension\ModuleHandler::hasImplementations() for Drupal 9 < 9.4
Comment #12
sourabhjainApologies for the misreading.
let me create the new patch.
Comment #13
sourabhjainUpdated it now. Please review.
Comment #14
gaëlgThanks! :)
Comment #15
selwynpolit commentedI couldn't get this patch to apply so I rolled a local version and stuck it in a file.
Here are the contents of the file in case it helps someone:
I added it as node_access_rebuild_progressive_d10.patch in my patches folder
Here are the relevant lines in composer.json:
Comment #16
alphex commented@selwynpolit - solved it for me.
Thanks
Comment #17
energee commentedComment #18
bobooon commentedRe-rolled using relative paths in the diffs.
Comment #19
justcaldwellWith any luck #3388337: Offer to co-maintain Node Access Rebuild Progressive will be resolved in another week or so, and we can hope for some movement on this. 🤞
Comment #20
dioni commentedAdded @shelane as mantainer
Comment #22
shelaneThanks. I've rolled this into the 2.x branch. There are a couple of minor updates I would like to apply before a new release. That should happen next week.
Comment #23
oakulm commentedNot really sure about this fix..
count expects to get array|Countable parameter and \Drupal::moduleHandler()->hasImplementations returns bool.
See https://www.php.net/manual/en/function.count.php & https://www.drupal.org/node/3000490
So the correct way would be to:
if (!\Drupal::moduleHandler()->hasImplementations('node_grants')) {So anyone tested the command drush node-access-rebuild-progressive and it runs without errors...?
Also node_access_rebuild_progressive_finished() returns void so the next line:
return node_access_rebuild_progressive_finished();is at best misleading.Comment #24
bobooon commented@oakulm is correct. Patch in #17 and thus the re-rolled #18 is incorrect. Resulting in the
[error] TypeError: count(): Argument #1 ($value) must be of type Countable|array, bool givenfatal. Patch #13 is implemented correctly but needs re-rolled.Comment #25
bobooon commentedHere's the re-rolled patch #13.
Comment #26
bobooon commentedAnd again because last one didn't apply cleanly.
Comment #27
bobooon commentedAnd again...
Comment #29
shelaneThank you. Yes, good catch.
Comment #31
gooddenis commentedLook like we pushed the wrong fix :(
should be
if (!\Drupal::moduleHandler()->hasImplementations('node_grants')) {but we pushed
if (\Drupal::moduleHandler()->hasImplementations('node_grants')) {Comment #32
prudloff commentedThis will be fixed by #3415406: All entries in the node_access table get deleted when running node-access-rebuild-progressive.
Comment #33
gooddenis commentedthx