Contrib.social

Automated Drupal 10 compatibility fixes

Open on Drupal.org →
Created on 15 June 2022, over 2 years ago
Updated 21 July 2024, 5 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

2.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.
  • @julianvj opened merge request.
  • Comment over 1 year ago →
    🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

    Conclusion: The only thing needed for D10 compatibility is to update the .info.yml files.

    In most cases it is like this but we should definitely make sure that #4 first paragraph statement isn't mandatory no more?

    Moving to 2.0.x (semantic versioning) for Drupal 10.

    Yeah otherwise we won't make it. We need a version still working with 8.x and one working with ^9 || ^10. That's how I did it with most other projects I maintain here. WIth some exceptions rather splitted at ^8.9.

    It's not immediately clear to me if the other patches in this queue need to be applied.

    Did you have seen this in #4? The most recent patch affects two files. In one, the only change is using a use statement instead of inlining a Drupal core classname. The other affects a deprecated Drupal-8-only file. If this is still mandatory and not provided in the last patch we maybe need to sum it up in one to test before commting?

  • Comment over 1 year ago →
    🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

    Oh @agentrickard and it would be good to open up 2.0 dev branch on the project page for others to chime in and test on D10. And we could add a paragraph on the project page stating that future work on ^9 || ^10 compatibility will go into 2.0-dev while the 8.0 branch still supports ^8 and ^9. Let me know if I shall do it.

  • Comment over 1 year ago →
    🇳🇱Netherlands yustinTR

    @diqidoq the execute() function also needs te be changes to accessCheck->execute()

  • Status changed to Needs review over 1 year ago
  • Open on Drupal.org →
    Core: 10.1.x + Environment: PHP 8.1 & MySQL 5.7
    last update over 1 year ago
    Waiting for branch to pass
  • Comment over 1 year ago →
    🇳🇱Netherlands yustinTR
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.1.x + Environment: PHP 8.1 & MySQL 5.7
    last update over 1 year ago
    Patch Failed to Apply
  • First commit to issue fork.
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update over 1 year ago
    93 pass
  • Comment over 1 year ago →
    🇩🇪Germany SteffenR Germany

    Since we have a 2.x branch, the MR should be changed accordingly and use this as the new target branch.

  • Comment over 1 year ago →
    🇩🇪Germany SteffenR Germany
  • Comment over 1 year ago →
    🇩🇪Germany SteffenR Germany
  • Comment over 1 year ago →
    🇩🇪Germany SteffenR Germany
  • Status changed to Closed: outdated 5 months ago
  • Comment 5 months ago →
    davps

    This issue is outdated. All Drupal 10 compatibility fixes have been merged into the 2.0.x development branch.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024