Automated Drupal 10 compatibility fixes

Created on 24 December 2022, over 1 year ago
Updated 27 October 2023, 8 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

Fixed

Version

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

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada phjou Vancouver/Paris ๐Ÿ‡จ๐Ÿ‡ฆ ๐Ÿ‡ช๐Ÿ‡บ

    Hello, can this be merged? This is pretty blocking for new websites using Drupal 10.

  • ๐Ÿ‡ฏ๐Ÿ‡ตJapan jorgemare

    Howdy,

    I was able to install the patched module in Drupal 10.0.8, and can confirm that it works as expected.

    It would be nice to have a new release so that it can be installed properly using composer. ;)

  • Status changed to RTBC about 1 year ago
  • ๐Ÿ‡จ๐Ÿ‡ฆCanada phjou Vancouver/Paris ๐Ÿ‡จ๐Ÿ‡ฆ ๐Ÿ‡ช๐Ÿ‡บ
  • ๐Ÿ‡ธ๐Ÿ‡ชSweden edward.peters

    Very grateful if a release is available soon....

  • ๐Ÿ‡ฌ๐Ÿ‡งUnited Kingdom mlpoulter

    Very grateful to see progress on this. For my installation with dozens of modules, this is the last one in the Upgrade Status report showing as incompatible with Drupal 10. I'm not going to install on a production service a version that's marked as development-only, so a proper release for a D10-compatible version of this module would be much appreciated. Thanks to the maintainers,

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada nicoleannevella

    composer failed to apply this patch for me. this is the last module blocking my upgrade.

  • Status changed to Needs work about 1 year ago
  • ๐Ÿ‡น๐Ÿ‡ญThailand AlfTheCat

    Patch failed to apply:

     sudo -u www-data patch -p1 < insert_view.3.0.x-dev.rector.patch
    patching file insert_view.info.yml
    Hunk #1 FAILED at 4.
    1 out of 1 hunk FAILED -- saving rejects to file insert_view.info.yml.rej
  • First commit to issue fork.
  • @sakthi_dev opened merge request.
  • Status changed to Needs review about 1 year ago
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia sakthi_dev

    Please review.

  • Status changed to RTBC about 1 year ago
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia Bushra Shaikh

    I have reviewed and checked MR !5 this works for drupal 9.5 and drupal 10.0. and 10.0.1
    Screenshots of the compatibility on 9.5 have been attached for reference:

    Can be moved to RTBC+1

  • Status changed to Needs work about 1 year ago
  • ๐Ÿ‡จ๐Ÿ‡ฆCanada nicoleannevella

    This patch fails to apply on 9.5.9

    Please do not post screenshots of it passing the Upgrade Module status. It does not help.

    It's a very simply patch. I'm not sure why it's not applying.

  • @nicoleannevella - If the Merge Request is confirmed to work (by @bushra-shaikh) isn't that good enough, ie no need for the patch?

    On my system the patch failed because the file has additional packaging info lines as described in this blog post and core issue 3036459 ๐Ÿ› Packaging info from .info.yml often creates conflicts when patching Active , ie these lines:

    # Information added by Drupal.org packaging script on 2022-09-29
    version: '2.0.1'
    project: 'insert_view'
    datestamp: 1664469525
    

    So the patch could be fixed to account for that, but the MR does the same thing so accepting that should do the job.

  • Status changed to RTBC 11 months ago
  • ๐Ÿ‡ฌ๐Ÿ‡งUnited Kingdom 3li U.K. ๐Ÿ‡ฌ๐Ÿ‡ง

    #2 applies fine to 3.0.x-dev
    and resolves the issue.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States lebachai

    Will this be released soon for D10? Thank you for everyone's hard work on this.

  • ๐Ÿ‡ต๐Ÿ‡ญPhilippines monph

    Echoing on @lebachai's comment. Hope this can be released soon.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States amanire

    Thank you for linking to that Chromatic post @gaddman! I was able to apply the patch in #2 against the stable 2.0.1 version using

            "preferred-install": {
                "drupal/insert_view": "source"

    since I strongly prefer not to install a dev version on production. Hopefully a maintainer will merge this MR and release a stable Drupal 10 compatible version soon.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States joshuasosa

    Also hoping to get this merged soon to have a Drupal 10 version.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States davedg629

    It doesnโ€™t seem like the maintainers of this project are going to step in and release this patch. Does anyone know if there is a process or someone to contact about this to see if we can get a new, or even just temporary, maintainer in place to perform the release?

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada RobLoach Earth

    I'm offering to help co-maintain this module to get this release out: https://www.drupal.org/project/insert_view/issues/3394696 ๐Ÿ’ฌ Offer to help Maintain Active

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States joshuasosa

    RobLoach is now a maintainer. Looking forward to seeing the update come through!

    • RobLoach โ†’ committed cdb6b9bc on 3.0.x
      Issue #3329314 by Project Update Bot: Automated Drupal 10 compatibility...
    • RobLoach โ†’ committed cdb6b9bc on 2.0.x
      Issue #3329314 by Project Update Bot: Automated Drupal 10 compatibility...
  • Status changed to Fixed 8 months ago
  • ๐Ÿ‡จ๐Ÿ‡ฆCanada RobLoach Earth

    Thanks so much! Since the `3.0.x` and `2.0.x` code was the same, I applied the change to both branches, and made the release as 2.1.0 โ†’ . Thanks for all the help and testing, all!

  • ๐Ÿ‡น๐Ÿ‡ญThailand AlfTheCat

    @RobLoach thanks for getting this released!

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

Production build 0.69.0 2024