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:

  1. 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.

  2. 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.

  3. 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

  1. Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. 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.

Command icon 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

    Project Update Bot created an issue. See original summary.

    project update bot’s picture

    Status: Active » Needs review
    StatusFileSize
    new510 bytes

    This 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.yml file 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

    Bot run #127

    This patch was created using these packages:

    1. mglaman/phpstan-drupal: 1.1.9
    2. palantirnet/drupal-rector: 0.12.0
    project update bot’s picture

    prudloff’s picture

    Issue summary: View changes
    StatusFileSize
    new1.08 KB

    ModuleHandlerInterface::getImplementations() is deprecated.

    eelkeblok’s picture

    Status: Needs review » Needs work

    It's probably a good idea to set the core_version requirement to ^9.4 || ^10 since getImplementations was only deprecated in 9.4.

    eelkeblok’s picture

    Here 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.

    nishavaghela’s picture

    Status: Needs work » Reviewed & tested by the community
    Issue tags: +Novice

    I 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.

    bob.hinrichs’s picture

    A release with d10 compatibility would be welcome!

    gaëlg’s picture

    Status: Reviewed & tested by the community » Needs work

    Comment #5 has not be addressed.

    sourabhjain’s picture

    Status: Needs work » Needs review
    StatusFileSize
    new1.08 KB
    new400 bytes

    I have addressed the point mentioned in #5. Please review.

    gaëlg’s picture

    Status: Needs review » Needs work

    Thank 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

    sourabhjain’s picture

    Assigned: Unassigned » sourabhjain

    Apologies for the misreading.
    let me create the new patch.

    sourabhjain’s picture

    StatusFileSize
    new1.07 KB
    new396 bytes

    Updated it now. Please review.

    gaëlg’s picture

    Assigned: sourabhjain » Unassigned
    Status: Needs work » Reviewed & tested by the community

    Thanks! :)

    selwynpolit’s picture

    I 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:

    diff --git docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.info.yml docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.info.yml
    index 1a0e13eec..f322ff847 100644
    --- docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.info.yml
    +++ docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.info.yml
    @@ -1,7 +1,7 @@
     name: 'Node Access Rebuild Progressive'
     description: 'Rebuild node access grants in chunks'
     type: module
    -core_version_requirement: ^8 || ^9
    +core_version_requirement: ^9.4 || ^10
     
     # Information added by Drupal.org packaging script on 2020-06-23
     version: '2.0.0'
    diff --git docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.module docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.module
    index 45f7c8a41..d2fc50637 100644
    --- docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.module
    +++ docroot/modules/contrib/node_access_rebuild_progressive/node_access_rebuild_progressive.module
    @@ -36,7 +36,7 @@ function node_access_rebuild_progressive_trigger() {
       node_access_needs_rebuild(FALSE);
       // Add default grants in the unlikely case
       // no modules implement node_grants anymore.
    -  if (!count(\Drupal::moduleHandler()->getImplementations('node_grants'))) {
    +  if (!count(\Drupal::moduleHandler()->hasImplementations('node_grants'))) {
         node_access_rebuild_progressive_set_default();
         return node_access_rebuild_progressive_finished();
       }
    
    

    I added it as node_access_rebuild_progressive_d10.patch in my patches folder

    Here are the relevant lines in composer.json:

            "patches": {
                "drupal/node_access_rebuild_progressive": {
                    "Automated Drupal 10 compatibility fixes - 3288770": "patches/node_access_rebuild_progressive_d10.patch"
                }
    
    alphex’s picture

    @selwynpolit - solved it for me.

    Thanks

    energee’s picture

    StatusFileSize
    new1.59 KB
    bobooon’s picture

    StatusFileSize
    new1.17 KB

    Re-rolled using relative paths in the diffs.

    justcaldwell’s picture

    With 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. 🤞

    dioni’s picture

    Added @shelane as mantainer

    • shelane committed 2e9296aa on 2.x
      Issue #3288770: Automated Drupal 10 compatibility fixes
      
    shelane’s picture

    Status: Reviewed & tested by the community » Fixed

    Thanks. 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.

    oakulm’s picture

    Not 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.

    bobooon’s picture

    Status: Fixed » Needs work

    @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 given fatal. Patch #13 is implemented correctly but needs re-rolled.

    bobooon’s picture

    Status: Needs work » Needs review
    StatusFileSize
    new1.07 KB

    Here's the re-rolled patch #13.

    bobooon’s picture

    StatusFileSize
    new1.07 KB

    And again because last one didn't apply cleanly.

    bobooon’s picture

    StatusFileSize
    new1.16 KB

    And again...

    • shelane committed 26ef8a23 on 2.x authored by oakulm
      Issue #3288770 by robphillips, oakulm: Automated Drupal 10 compatibility...
    shelane’s picture

    Status: Needs review » Fixed

    Thank you. Yes, good catch.

    Status: Fixed » Closed (fixed)

    Automatically closed - issue fixed for 2 weeks with no activity.

    gooddenis’s picture

    Look like we pushed the wrong fix :(

    should be
    if (!\Drupal::moduleHandler()->hasImplementations('node_grants')) {
    but we pushed
    if (\Drupal::moduleHandler()->hasImplementations('node_grants')) {

    gooddenis’s picture

    thx