Contrib.social

Automated Drupal 10 compatibility fixes

Open on Drupal.org →
Created on 16 June 2022, over 2 years ago
Updated 6 December 2023, about 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

Created by

project update bot

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.

  • First commit to issue fork.
  • First commit to issue fork.
  • @j_edery opened merge request.
  • Comment about 1 year ago →
    🇬🇧United Kingdom j_edery

    Patch failed I have issued a merge request with a patch that applies cleanly.

  • Comment about 1 year ago →
    🇬🇧United Kingdom tce

    This module is the only thing blocking me upgrading to Drupal 10.

    How can bypass the composer "Your requirements could not be resolved" error just to install and then patch the module?

  • Comment about 1 year ago →
    🇬🇧United Kingdom j_edery

    @tce in order to make use of the patch you need to install a composer plugin called "lenient"

    Instructions:

    setup the composer plugin:

    composer require mglaman/composer-drupal-lenient

    And add an exception for the vimeo_embed_field module:

    composer config --merge --json extra.drupal-lenient.allowed-list '[ "vimeo_embed_field"]'

    Add the patch to you'r composer files:

    "drupal/vimeo_embed_field": {
    "Issue #3290566: Drupal 10 compatibility fixes": "https://git.drupalcode.org/project/vimeo_embed_field/-/merge_requests/2...."
    }

    *Ensure you'r composer file is ssetup correctly to use patches.

  • Status changed to RTBC about 1 year ago
  • Comment about 1 year ago →
    🇩🇪Germany spuky

    patch ist working with drupal-lenient but would be nice to get a release

  • Status changed to Fixed about 1 year ago
  • Comment about 1 year ago →
    🇩🇪Germany spuky

    Was fixed in:

    https://www.drupal.org/project/vimeo_embed_field/issues/3379270 📌 Drupal 10 compatibility fixes RTBC

  • Status changed to Fixed about 1 year ago
  • Comment about 1 year ago →
    🇮🇳India ydbalaji

    its clone of https://www.drupal.org/project/vimeo_embed_field/issues/3379270 📌 Drupal 10 compatibility fixes RTBC and fixed this issue.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024