Automated Drupal 10 compatibility fixes

Created on 16 June 2022, over 2 years ago
Updated 3 September 2024, 2 months ago

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 โ†’ .

๐Ÿ“Œ Task
Status

Closed: outdated

Version

1.0

Component

Code

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Status changed to Needs work about 1 year ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States trobey

    There is a deprecated function that needs to be fixed for Drupal 10.

    Error: Call to undefined method Drupal\Core\Extension\ModuleHandler::getImplmentations() in recode_save() (line308 of modules/contrib/regcode.module).

    Here is the change record for this:

    https://www.drupal.org/node/3000490 โ†’

  • Status changed to Needs review about 1 year ago
  • Open on Drupal.org โ†’
    Core: 9.5.5 + Environment: PHP 7.3 & MySQL 5.7
    last update about 1 year ago
    Waiting for branch to pass
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia roshni27

    Please review the patch.

  • Status changed to Needs work about 1 year ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States tr Cascadia
  • Assigned to tcmktg
  • Status changed to RTBC about 1 year ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States tcmktg

    The Patch identified in #6 worked to resolve the issue reported in #5. Tested and working in Drupal 10, PHP 8.1.

  • Status changed to Needs work about 1 year ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States tr Cascadia

    Just because you don't get an error doesn't mean it works. It is clearly wrong if you just look at the patch.

    • The replacement code is identical for the two hooks, but it should not be because these are different hooks.
    • Likewise, the closure is passed the wrong variables in the first case.
    • Additionally, invokeAllWith() was introduced in Drupal 9.4, so there is no way this change is compatible with ^8.8.2 or with ^9. The dependency changes in the patch are wrong.

    My preference would be to add a simple test case to make sure the hook invocations work as designed - this test case should run in D9 and D10 and that will help to ensure the hook invocations were ported correctly. A test case would also reveal the problem with the dependencies.

  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia Nitesh Sethia

    Nitesh Sethia โ†’ made their first commit to this issueโ€™s fork.

  • Merge request !4Drupal 10 compatibility fixes โ†’ (Open) created by Nitesh Sethia
  • Open on Drupal.org โ†’
    Core: 9.5.5 + Environment: PHP 7.3 & MySQL 5.7
    last update about 1 year ago
    Waiting for branch to pass
  • Status changed to Needs review about 1 year ago
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia Nitesh Sethia

    Created a patch for version compatibility.

  • Pipeline finished with Success
    about 1 year ago
    Total: 196s
    #45488
  • Status changed to Needs work about 1 year ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States tr Cascadia

    @tcmktg: You assigned this to yourself - are you going to work on it?

  • ๐Ÿ‡ธ๐Ÿ‡ชSweden edward.peters

    As a non developer who is reliant on this module, I shall be very grateful for a D10-compatible release asap.

  • First commit to issue fork.
  • Open on Drupal.org โ†’
    Core: 9.5.5 + Environment: PHP 7.3 & MySQL 5.7
    last update 11 months ago
    Waiting for branch to pass
  • Pipeline finished with Success
    11 months ago
    Total: 135s
    #65634
  • Issue was unassigned.
  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น

    I am resetting the Assigned field, since the person to which the issue was assigned has not worked on it since October, 2023.

    I apologize for bumping this issue.

  • Open on Drupal.org โ†’
    Core: 9.5.5 + Environment: PHP 7.3 & MySQL 5.7
    last update 10 months ago
    Waiting for branch to pass
  • Pipeline finished with Success
    10 months ago
    #83990
  • Status changed to Needs review 10 months ago
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia Nitesh Sethia

    Updated the code and the patch was missing few changes.

  • Status changed to Needs work 10 months ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States tr Cascadia
  • ๐Ÿ‡ฌ๐Ÿ‡งUnited Kingdom lind101

    Hey Nitesh Sethia,

    It looks to me like you have bought the broken changes from #6 (Invalid hook arguments etc, see full list in #9) into the MR.

    The work I added to the MR was to address some of the issue raised (specifically arround hook parameteres) in #9. This work was intended as a replacement for the work done in #6. It looks like you've added the work from #6 back?

    (Sorry I should have made that clearer when I added the changes)

    Cheers!

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany stolzenhain

    Thanks to @lind101 for working out a solution to this!

    To use this on fresh installation and apply the working patch on #15, we had to

    1. refer to the lenient endpoint package โ†’ allowing to bypass version requirements
    2. add the regcode module as an exception
    3. successfully requiring the module, after which the
    4. the patch file of the drupacode merge could be applied to fix the behaviour

    (props to @morenstrat โ†’ for pointing to the lenient plugin)

  • ๐Ÿ‡ธ๐Ÿ‡ชSweden edward.peters

    Thank you Stolzenhain. Do you or anyone else know how/when this could be rolled into a release?

  • Status changed to Closed: outdated 2 months ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States tr Cascadia

    There is nothing here that is D10-specific except for the changes to regcode.info.yml. And those are done wrong.

    The supported core versions for this module have already been changed to ^9.4 | ^10 by commit a849b4b0

    The change to the hook invocations will be solved in ๐Ÿ“Œ [9.4] All hook invocation delegated to Module Handler service Fixed .
    I have opened up an MR in that issue and uploaded the patch by @lind101 from #15 above. That is the only valid patch that has been posted here.

    Closing this issue as "outdated" so that the project update bot will stop auto posting.

Production build 0.71.5 2024