Contrib.social

Automated Drupal 11 compatibility fixes for breadcrumb_extra_field

Open on Drupal.org →
Created on 15 March 2024, over 1 year 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

2.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 over 1 year 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 → , even with these changes, this module is not yet compatible with Drupal 11.

    Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.

    Therefore these changes did not 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-120024

    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
  • Merge request !9Automated Project Update Bot fixes → (Merged) created by project update bot
  • Comment over 1 year 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
  • First commit to issue fork.
  • Comment about 1 year ago →
    🇺🇦Ukraine AstonVictor
  • Comment 7 months ago →
    🇮🇹Italy trickfun

    I can't apply path on 3.0.0-alpha1
    Thank you

  • Comment 4 months ago →
    🇮🇹Italy trickfun

    Any news here?
    Thank you

  • Comment 4 months ago →
    🇺🇦Ukraine AstonVictor

    Hi @trickfun,

    you should use the dev version for now - composer require 'drupal/breadcrumb_extra_field:3.0.x-dev@dev'
    thanks

  • Comment 4 months ago →
    🇮🇹Italy trickfun

    Thank you

  • Comment 10 days ago →
    🇪🇸Spain albeorte

    There are more changes related to the upgrade to Drupal 11.

    When going to the Settings form, on a Drupal 11 site, the following error is reported:

    ArgumentCountError: Too few arguments to function Drupal\Core\Form\ConfigFormBase::__construct(), 1 passed in /var/www/html/web/modules/contrib/breadcrumb_extra_field/src/Form/BreadcrumbExtraFieldSettingsForm.php on line 43 and exactly 2 expected in Drupal\Core\Form\ConfigFormBase->__construct() (line 44 of core/lib/Drupal/Core/Form/ConfigFormBase.php).

    This error is a consequence of the explanation in the following Core issue. -> https://www.drupal.org/node/3404140 →

    I have created the following patch, which will serve as a solution for those who have installed the development version "3.0.x-dev@dev".

    The roadmap will be as follows:

    • Stop supporting the 2.x branch.
    • Release stable version for branch 3.x (3.0.0), which will be compatible with Drupal 9 and 10.
    • Release new branch 4.x, and version (4.0.0), which will be compatible with Drupal 10 and 11.
  • Comment 9 days ago →
    🇪🇸Spain albeorte

    Steps to check the correct operation:

    1. Install version “4.0.0-rc1” on a Drupal 11 site 2: composer require 'drupal/breadcrumb_extra_field:^4.0@RC'
    2. Check the module functionalities
  • Comment 8 days ago →
    🇪🇸Spain antonio.nunez Spain

    I have tested version 4.0.0-rc1 of the module on environments running Drupal 11 as well as post-10 versions, such as Drupal 10.5, and everything works as expected.

    Configuration, export functionality, and visualizations behave correctly with no issues or warnings detected.
    I believe the module is ready for a stable release. Great work!

  • Comment 8 days ago →
    🇪🇸Spain albeorte
  • Comment 8 days ago →
    🇪🇸Spain albeorte

    New version stable released: 4.0.0

    Thank you!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024