Contrib.social

Automated Drupal 10 compatibility fixes

Open on Drupal.org →
Created on 24 June 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 →

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

Needs review

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

  • Issue created by @project update bot
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.5 + Environment: PHP 7.3 & MySQL 5.7
    last update almost 2 years ago
    27 pass
  • Comment almost 2 years ago →
    project update bot

    This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.

    It is important that any automated tests available are run with this patch and that you manually test this patch.

    Drupal 10 Compatibility

    According to the Upgrade Status module → , even with this patch, this module is not yet compatible with Drupal 10.

    Currently Drupal Rector, version 0.15.1, cannot fix all Drupal 10 compatibility problems.

    Therefore this patch does not update the info.yml file for Drupal 10 compatibility.

    Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.

    Debug info

    Bot run #12554

    This patch was created using these packages:

    1. mglaman/phpstan-drupal: 1.1.35
    2. palantirnet/drupal-rector: 0.15.1
  • Status changed to Closed: won't fix almost 2 years ago
  • Comment almost 2 years ago →
    🇺🇸United States tr Cascadia
  • Comment 4 months ago →
    🇨🇦Canada joseph.olstad

    Hello @TR, investigated this without knowing too much about the implications, there's approximately 29,387 D8/D9/D10 installs of this project, what's the reasoning and justification behind "won't fix"? If this has already been discussed many times perhaps we should include a hyperlink to the discussion or roadmap.

    I am guessing that upgrading this to D11 is far easier and less effort than for 29,000 x refactoring builds using another solution.

    Would you be open to adding co-maintainer(s) to this project in order to achieve this?

    Recently I unblocked over 50000 upgrades for bootstrap 3, they are now able to upgrade smoothly to Drupal 11. Wondering if we can achieve this with mimemail since there's a significant number of installs (29,000+).

  • Comment 4 months ago →
    🇨🇦Canada joseph.olstad
  • Comment 4 months ago →
    🇺🇸United States tr Cascadia

    This module has had a D10 release since before the bot posted this issue.

    "Won't fix" is because this is an automated post from a bot, and the only way to keep it from continuing to make posts like this is to close the issue. As it says in the issue summary:

    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.

    And to be clear, I have never found any of these bot patches useful.

    The offered patch does not make this module work any better on D10 than it does now, and there is already an existing issue and discussion and contributions for the one change that the patch proposes. So call it "duplicate" if you want - I call it "won't fix" because I'm not going to commit the patch. But I don't need the bot offering "fixes" that don't actually fix anything, then having this "compatibility" issue become a dumping ground for any issue people have with this module - and my experience has taught me that's what always happens.

  • Comment 4 months ago →
    🇨🇦Canada joseph.olstad

    Hi tr, sorry I was confused, I meant to post my question here:

    📌 Automated Drupal 11 compatibility fixes for mimemail Needs review

    It is the Drupal 11 compatibility we're inquiring about as we already use this module with Drupal 10.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024