- Issue created by @project update bot
- last update
about 1 year ago 16 pass 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-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- last update
about 1 year ago 16 pass - last update
about 1 year ago 16 pass 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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- last update
about 1 year ago 16 pass - Status changed to RTBC
7 months ago 2:09pm 27 August 2024 - First commit to issue fork.
- 🇮🇳India sheshsharma
MR!10 Makes this module compatible with Drupal 11. Functionality is working as expected.
RTBC +1 - First commit to issue fork.
- 🇩🇪Germany geek-merlin Freiburg, Germany
Adding stable patch for composer patching, please ignore for all other purposes.
- 🇨🇦Canada joseph.olstad
I have used the contact form in an attempt to reach the maintainer. Here is an extract of my message:
Hello Manuel, your great module needs Drupal 11 compatibility.
The code is ready, it needs you or a designated maintainer to take care of reviewing/merging/tagging and releasing.
I have been running Drupal 11 for a few months now, it's available for approximately 9 months. The time is now to release a compatible module.
https://www.drupal.org/project/fixed_block_content/issues/3430612 📌 Automated Drupal 11 compatibility fixes for fixed_block_content Needs review
Thank you,
Joseph Olstad
(phone number)
(email address) -
manuel.adan →
committed 93a7daa1 on 8.x-1.x authored by
project update bot →
Issue #3430612 by sheshsharma, geek-merlin, sanket1007, manuel.adan:...
-
manuel.adan →
committed 93a7daa1 on 8.x-1.x authored by
project update bot →
- 🇪🇸Spain manuel.adan 🌌
Tests are being affected by Drupal core issue 🐛 Undefined array key "view_mode" in block_content_theme_suggestions_block_alter Active , they pass in D9 (PHP 8.1), D10 (PHP 8.1, 8.2, 8.3 & 8.4) and D11 (PHP 8.3 & 8.4) patching core.