Contrib.social

Automated Drupal 10 compatibility fixes

Open on Drupal.org →
Created on 18 July 2022, almost 3 years ago
Updated 6 July 2023, almost 2 years 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 →

Periodically patches will be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted simply close this issue (any status besides Active, Needs review or Needs work) or remove the "ProjectUpdateBotD10" tag from the issue.

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 or Needs work) 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.

  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 don't want new automated patches simply leave this issue open but remove the "ProjectUpdateBotD10" tag from the issue.

    You can use Drupal Rector yourself to make these patches.

    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 or Needs work) 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 may be useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the patch in the comment by Project Update Bot → .
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.

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 Infrastructure project issue queue → using the component “Bot: Drupal Rector”.

📌 Task
Status

Active

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.

  • Comment almost 2 years ago →
    🇩🇪Germany Anybody Porta Westfalica

    Drupal 9 EOL is close :)

  • Comment almost 2 years ago →
    🇳🇴Norway gisle Norway

    Tagged release 8.x-1.1-alpha2 → is compatible with Drupal 10. I'm using the alpha release on some Drupal 10 production sites, and it works well enough for my clients (their use case is to be able to see README.md online by visiting the site).

    The Rector patch has already been applied. This issue stays "Active" to keep Rector monitoring the code.

    What remain before we're able to create a full release is a number of regressions, compared to all the features provided by the Drupal 7 version. Please see child issues of 🌱 [meta] Regressions vis-à-vis Drupal 7 Active . Those regressions have been there since the release of a Drupal 8 compatible version. We will need community support in the shape of patches/MRs and testing to get those regressions resolved, since my clients is served well enough by the alpha-release and is not willing to sponsor fixing those regressions.

    Resetting "Priority", since the version for Drupal 10 is not worse than the version for Drupal 8 and Drupal 9.

  • Comment almost 2 years ago →
    🇩🇪Germany Anybody Porta Westfalica

    Thanks @gisle, sorry I didn't see that!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024