Contrib.social

Automated Drupal 11 compatibility fixes for back_to_top

Open on Drupal.org →
Created on 16 March 2024, 9 months ago

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes 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 "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes 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 changes 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 "ProjectUpdateBotD11" tag is left on this issue, new changes 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 changes 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 changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated changes.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" 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 changes will be posted here.

    If the issue is reopened, then new automated changes will be posted.

    If you are using another issue(s) to work on Drupal 11 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.

Using the merge request

  1. Review the merge request and test it.
  2. Thoroughly test the changes. These changes 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 merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes 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

3.0

Component

Code

Created by

project update bot

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @project update bot
  • Comment 9 months ago →
    project update bot

    This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.

    It is important that any automated tests available are run and that you manually test the changes.

    Drupal 11 Compatibility

    According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
    Therefore these changes update the info.yml file for Drupal 11 compatibility.

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

    Debug info

    Bot run #11-120835

    This patch was created using these packages:

    1. drupal/upgrade_status: 4.1.0
    2. mglaman/phpstan-drupal: 1.2.7
    3. palantirnet/drupal-rector: 0.20.1
  • Comment 4 months ago →
    🇺🇸United States sikofitt

    I have applied the patch in #2 and it seems to be working fine. Is it possible to get a new release for Drupal 11?

  • Merge request !15Automated Project Update Bot fixes from run 11-120835. → (Merged) created by hswong3i
  • Comment 4 months ago →
    🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

    Well I can merge it to 2.x which seems to be the active dev branch at the moment. Which may confuse users regarding the lower version number in comparison to the last 3.0 release. But the 2.x dev branch → is more up-to-date and has commits from the time after the 3.0 release, so I can only suggest to test 2.x dev if it works for you. Please beware that there are changes that other code changes can become required for full 11 support since 11 only supports PHP version 8.3 and higher. This can cause some deprecation issues or new requirements in code which are not added yet.

    I will keep this issue active for the bot, since the bot sometimes adds more to the fix later and even tries to re-roll in case we are ahead.

  • Pipeline finished with Skipped
    4 months ago
    #270445
  • Status changed to Active 4 months ago
  • Comment 4 months ago →
    System Message
  • Comment 3 months ago →
    ivnish Kazakhstan

    @dqd I think we need to create new 3.x branch from 2.x and continue 3.0+ release versioning

  • Comment 2 months ago →
    System Message
    • acke → committed 558cf621 on 3.0.x 
      Issue #3428936 by acke, ivnish, dqd, sikofitt, hswong3i: Automated...
  • Comment 2 months ago →
    🇭🇰Hong Kong hswong3i
  • Comment 2 months ago →
    🇸🇪Sweden acke
  • Comment 2 months ago →
    🇸🇪Sweden acke

    Fixed in 3.0.x-dev and going into 3.0.1.

  • Comment 2 months ago →
    🇺🇸United States sikofitt

    Sorry, this got lost in my email. I'm running the 2.x dev branch and everything is working. I'll upgrade to the 3.0 branch when it is released.

  • Status changed to Fixed about 2 months ago
  • Comment about 2 months ago →
    System Message

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

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024