Automated Drupal 10 compatibility fixes

Created on 15 June 2022, over 2 years ago
Updated 10 August 2023, over 1 year 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

Fixed

Version

1.0

Component

Code

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

Comments & Activities

Not all content is available!

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

  • 🇳🇱Netherlands arantxio Dordrecht

    The patch applies perfectly and the code changes for the functionality of the module seem to be working fine. I've not yet tested the test files that it changed, if I get to that I will update the issue to RTBC. If I cannot find the time someone should test those first before we can "close" this issue.

  • 🇮🇳India abhinavk

    I checked the patch #3 and it works fine. I just some errors while running drupal-check which are not ignorable, so adding fixes for them in new patch.
    Also attaching drupal-check file.

  • Tested the patch #6 but found warning when applying patch. So applied it manually and checked the upgrade status.
    The module is compatible with D10 now.
    git apply --check geophp_d10-3287733-6.patch

    warning: geoPHP/tests/tests/20120702Test.php has type 100644, expected 100755
    warning: geoPHP/tests/tests/adaptersTest.php has type 100644, expected 100755
    warning: geoPHP/tests/tests/aliasesTest.php has type 100644, expected 100755
    warning: geoPHP/tests/tests/geosTest.php has type 100644, expected 100755
    warning: geoPHP/tests/tests/methodsTest.php has type 100644, expected 100755
    warning: geoPHP/tests/tests/placeholdersTest.php has type 100644, expected 100755
    warning: geophp.info.yml has type 100644, expected 100755
    warning: geophp.module has type 100644, expected 100755

  • Status changed to RTBC over 1 year ago
  • 🇮🇳India rahul1707

    Tested patch #6 on Drupal 10.0.8 and 9.5.7 and PHP 8.1. Patch works perfectly fine for me and making this module D10 compatible. Checked with upgrade status as well which is giving no error found.
    So, moving this to RTBC for D10 stable release.

  • 🇺🇦Ukraine i-trokhanenko Lutsk 🇺🇦

    patch #6 works well for me, thanks!

  • Status changed to Fixed over 1 year ago
  • 🇺🇦Ukraine i-trokhanenko Lutsk 🇺🇦
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024