Contrib.social

Automated Drupal 11 compatibility fixes for context

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

5.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 → , 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-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 9 months ago →
    project update bot

    This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.

    This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) 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.

    The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.

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

    Debug information

    Bot run #11-137198

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.1.0
    2. mglaman/phpstan-drupal: 1.2.10
    3. palantirnet/drupal-rector: 0.20.1
  • First commit to issue fork.
  • Merge request !59Resolve #3429553 "Automated drupal 11" → (Open) created by jrglasgow
  • Status changed to RTBC 5 months ago
  • Comment 5 months ago →
    🇺🇸United States BenStallings

    I am no expert in this module, but I was able to install and use it with MR!59.

  • Status changed to Needs work 5 months ago
  • Comment 5 months ago →
    🇺🇸United States BenStallings

    I spoke too soon... in addition to the things that have been fixed on this branch, Upgrade Status reports:

    web/modules/composer/context/modules/context_ui/src/Plugin/Block/ContextInspector.php 37 Calls to function kpr should not exist.

    web/modules/composer/context/src/Reaction/Blocks/Controller/ContextReactionBlocksController.php 188 The 'context_ui/admin' library is not defined because the defining extension is not installed. Cannot decide if it is deprecated or not.

    web/modules/composer/context/modules/context_ui/src/Controller/ContextUIController.php 183 The 'context_ui/admin' library is not defined because the defining extension is not installed. Cannot decide if it is deprecated or not.

    web/modules/composer/context/modules/context_ui/src/Controller/ContextUIController.php 259 The 'context_ui/admin' library is not defined because the defining extension is not installed. Cannot decide if it is deprecated or not.

  • Comment 4 months ago →
    🇩🇪Germany Anybody Porta Westfalica

    Seems like the module isn't very actively maintained anymore?

    Any maintainer plans now that D11 is out?

  • Comment 3 months ago →
    🇬🇧United Kingdom ice70

    There is a merge request to fix the " Calls to function kpr should not exist"

    https://www.drupal.org/project/context/issues/3357524 🐛 Calls to function kpr should not exist. Active

    I applied this via composer / patches:

    		"patches": {
			"drupal/context": {
			    "D11":"https://www.drupal.org/files/issues/2024-04-04/context.5.x-dev.rector.patch",
			    "Calls to KPR" :"https://git.drupalcode.org/project/context/-/merge_requests/35.patch"
			}
		},

    Using upgrade status 4.3.5, I did not get the remaining errors in https://www.drupal.org/project/context/issues/3429553#comment-15707676 📌 Automated Drupal 11 compatibility fixes for context Needs work instead I got notices that

    context/context.info.yml
    context/modules/context_ui/context_ui.info.yml

    did not have the latest version supported - to fix, I just updated both yml files:

    core_version_requirement: ^9.3 || ^10
    to
    core_version_requirement: ^9.3 || ^10 || ^11

    I tried to make a patch for this simple change, but my patch would not apply via composer. It applied fine by git against 5.x :(

  • Comment 3 months ago →
    🇬🇧United Kingdom ice70

    ok, have a working patch. Is it a bit of a multi-patch setup, but it does clear the upgrade status warnings. The url to this patch will need to change to the correct link once the file has uploaded ("URL-TO-THIS-PATH/d11-3429553-9.patch"):

    "drupal/context":{
    " https://www.drupal.org/project/context/issues/3357524 🐛 Calls to function kpr should not exist. Active Calls to KPR" :"https://git.drupalcode.org/project/context/-/merge_requests/35.patch",
    " https://www.drupal.org/project/context/issues/3429553 📌 Automated Drupal 11 compatibility fixes for context Needs work D11" : " https://www.drupal.org/files/issues/2024-04-04/context.5.x-dev.rector.patch → ",
    " https://www.drupal.org/project/context/issues/3429553 📌 Automated Drupal 11 compatibility fixes for context Needs work D11 #9" : "URL-TO-THIS-PATH/d11-3429553-9.patch"
    }

  • Comment 3 months ago →
    🇮🇳India bmahesh03121

    There is a different issue with MR ready for calls to kpr should not exist,

    no other warning is found in the upgrade status except for .info.yml file changes which are fixed in this patch


    moving this to RTBC

  • Status changed to RTBC 14 days ago
  • Comment 14 days ago →
    🇮🇳India peelas02

    verified MR59 in drupal 10 and Drupal 11, functionality is working fine after applying patch https://www.drupal.org/project/context/issues/3357524 🐛 Calls to function kpr should not exist. Active
    RTBC+1

  • Comment 13 days ago →
    🇮🇳India peelas02

    verified MR59 in drupal 10 and Drupal 11, functionality is working fine after applying patch https://www.drupal.org/project/context/issues/3357524 🐛 Calls to function kpr should not exist. Active
    RTBC+1

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024