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.

CommentFileSizeAuthor
#39 3428552-39.patch1 KBkeshavv
#37 3428552-update-drupal-11-config-override-warn-37.patch3.32 KBusingsession
#22 config_override_warn.1.x-dev.rector.patch1.3 KBproject update bot
#22 interdiff-last-bot.7033744.txt339 bytesproject update bot
#17 config_override_warn.1.x-dev.upgrade_status.post_rector.txt3.37 KBproject update bot
#17 config_override_warn.1.x-dev.rector.patch899 bytesproject update bot
#7 config_override_warn-drupal-11-compatibility-fixes-3428552-7.patch1.77 KBv.dovhaliuk
#6 config_override_warn.1.x-dev.rector.patch1.3 KBproject update bot
#6 interdiff-last-bot.6922500.txt1.07 KBproject update bot
#5 config_override_warn.1.x-dev.rector.patch438 bytesproject update bot
#5 interdiff-last-bot.6911335.txt1019 bytesproject update bot
#4 config_override_warn.8.x-1.4.rector.patch1.11 KBproject update bot
#4 interdiff-last-bot.6910086.txt339 bytesproject update bot
#2 config_override_warn.8.x-1.4.rector.patch707 bytesproject update bot

Issue fork config_override_warn-3428552

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

project update bot commented
Status: Active » Needs review
StatusFileSize
new config_override_warn.8.x-1.4.rector.patch707 bytes

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

Project Update Bot opened merge request !2

project update bot’s picture

project update bot commented
StatusFileSize
new interdiff-last-bot.6910086.txt339 bytes
new config_override_warn.8.x-1.4.rector.patch1.11 KB

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
project update bot’s picture

project update bot commented
Version: 8.x-1.4 » 8.x-1.x-dev
StatusFileSize
new interdiff-last-bot.6911335.txt1019 bytes
new config_override_warn.1.x-dev.rector.patch438 bytes

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 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 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
project update bot’s picture

project update bot commented
StatusFileSize
new interdiff-last-bot.6922500.txt1.07 KB
new config_override_warn.1.x-dev.rector.patch1.3 KB

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 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 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-199781

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.3.2
  2. mglaman/phpstan-drupal: 1.2.11
  3. palantirnet/drupal-rector: 0.20.3
v.dovhaliuk’s picture

v.dovhaliuk commented
Issue summary: View changes
StatusFileSize
new config_override_warn-drupal-11-compatibility-fixes-3428552-7.patch1.77 KB
jamesoakley’s picture

jamesoakley
Primary language English
Location North Yorkshire, UK
commented
Related issues: +#3462541: Difference with what is now in core?

Maybe there's a prior question of whether this module is still needed? #3462541: Difference with what is now in core?

deimos changed the visibility of the branch project-update-bot-only to hidden.

deimos changed the visibility of the branch project-update-bot-only to active.

deimos opened merge request !4

deimos’s picture

deimos commented

Greetings,

I merged bot's changes and added corrections to get tests green. They were failed due to changes done in #3395913: Correct spelling in Config tests, specifically this changes.
Also I checked test on D11 and added fixes to get them working as well.
Changes were pushed into 3428552-automated-drupal-11

deimos’s picture

deimos commented

Issue reported by Update Status module can be ignored till Drupal 12 release.

================================================================================
Config Override Warn, --
Scanned on Tue, 03/04/2025 - 20:32

FILE: web/modules/contrib/config_override_warn/config_override_warn.module

STATUS         LINE                           MESSAGE                           
--------------------------------------------------------------------------------
Ignore         32   Call to deprecated method renderPlain() of class            
                    Drupal\Core\Render\Renderer. Deprecated in drupal:10.3.0 and
                    is removed from drupal:12.0.0. Use                          
                    Drupal\Core\Render\RendererInterface::renderInIsolation()   
                    instead.                                                    
--------------------------------------------------------------------------------
prudloff’s picture

prudloff commented
Status: Needs review » Reviewed & tested by the community

Tests on the MR look OK.
I also did some manual testing and it seems to work correctly: the warning is displayed only when it is not already handled by core.

prudloff’s picture

prudloff commented

Hiding patches to focus on the MR.

roderik’s picture

roderik
Primary language Dutch
Location Amsterdam,NL / Budapest,HU
commented

Maybe there's a prior question of whether this module is still needed?

Just for the people only reading this issue:

Yes, it's been established that this is still needed, in #3462541-4: Difference with what is now in core? and further.

So a merge + release is appreciated.

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Reviewed & tested by the community » Needs review
StatusFileSize
new config_override_warn.1.x-dev.rector.patch899 bytes
new config_override_warn.1.x-dev.upgrade_status.post_rector.txt3.37 KB

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.3, 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-466239

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.3.6
  2. mglaman/phpstan-drupal: 1.3.5
  3. palantirnet/drupal-rector: 0.20.3

anairamzap made their first commit to this issue’s fork.

anairamzap opened merge request !6

anairamzap’s picture

anairamzap
she/her
Primary language Spanish
Location 🇦🇷 ✌🏽 Buenos Aires
commented
Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

Hi, I've tested the automated update bot changes + the changes made by @deimos in PR4 #3428552-13: Automated Drupal 11 compatibility fixes for config_override_warn and everything looks ok.

I had to create a new branch for the latest stable 8.x-1.4 release since we need D11 compatibility for a project.

Can we please have a new release created with these changes?

Thanks!

Mariana

bserem’s picture

bserem commented

MR !6 doesn't apply properly (patching via composer). MR !4 does

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Reviewed & tested by the community » Needs review
StatusFileSize
new interdiff-last-bot.7033744.txt339 bytes
new config_override_warn.1.x-dev.rector.patch1.3 KB

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 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 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-510914

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.3.7
  2. mglaman/phpstan-drupal: 1.3.9
  3. palantirnet/drupal-rector: 0.21.0

usingsession made their first commit to this issue’s fork.

usingsession opened merge request !7

usingsession’s picture

usingsession commented
Issue summary: View changes

In PR4 Issue #3428552: Drupal 11 compatibility fixes for config_override_warn everything looks ok (for 8.x-1.x-dev).
But I created new PR based on it, because in my opinion, I see no reason to wait for Drupal 12 to remove Renderer::renderPlain().

usingsession opened merge request !8

usingsession changed the visibility of the branch 3428552-drupal-compatibility-fixes-stable-1.4 to hidden.

usingsession’s picture

usingsession commented

About 3428552-drupal-compatibility-fixes-stable-1.4 - I tried to create a patch for module1.4, but composer.json always fails.
!MR6 - also fails

usingsession closed merge request !8

prudloff’s picture

prudloff commented

We now have 4 MRs on this issue, which one should be reviewed?

usingsession changed the visibility of the branch 3428552-drupal-compatibility-fixes to hidden.

usingsession’s picture

usingsession commented

@prudloff, I believe the correct one to review is MR !4

prudloff changed the visibility of the branch project-update-bot-only to hidden.

prudloff changed the visibility of the branch 3428552-automated-update-d11-stable-1.4 to hidden.

prudloff’s picture

prudloff commented

usingsession changed the visibility of the branch 3428552-drupal-compatibility-fixes to hidden.

usingsession’s picture

usingsession commented
StatusFileSize
new 3428552-update-drupal-11-config-override-warn-37.patch3.32 KB

As @anairamzap mentioned above, if you need a patch for the stable version 8.x-1.4, you can use the attached one.

usingsession changed the visibility of the branch 3428552-drupal-compatibility-fixes to hidden.

keshavv’s picture

keshavv commented
StatusFileSize
new 3428552-39.patch1 KB

Patch for https://www.drupal.org/project/config_override_warn/releases/8.x-1.x-dev

nala-he’s picture

nala-he commented
Status: Needs review » Reviewed & tested by the community

Hi, I’ve tested 3428552-39.patch (for 8.x-1.x-dev), MR !4, and MR !7 on Drupal 11.2.3.

I was able to composer install these patches using the mglaman/composer-drupal-lenient composer plugin with ddev composer require 'drupal/config_override_warn:1.x-dev@dev'.

The three tested patches deliver identical warning behavior. For a D11 compatibility upgrade ticket, 3428552-39.patch probably follows better practices with minimal changes (e.g. no changes on test wording). The removal of deprecated renderPlain() also provides forward compatibility for D12. (MR!7 is the combination of MR !4 and 3428552-39.patch)

prudloff’s picture

prudloff commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

  • prudloff committed bd686a07 on 8.x-1.x authored by deimos 
    Issue #3428552: Drupal 11 compatibility fixes for config_override_warn[#...

prudloff closed merge request !2

prudloff closed merge request !6

prudloff closed merge request !7

Status: Fixed » Closed (fixed)

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