- Issue created by @project update bot
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.1 & MySQL 5.7last update
9 months ago Waiting for branch to pass 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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.1 & MySQL 5.7last update
9 months ago Waiting for branch to pass -
joseph.olstad →
committed c28de669 on 2.0.x
Issue #3435372 by Project Update Bot: Automated Drupal 11 compatibility...
-
joseph.olstad →
committed c28de669 on 2.0.x
- First commit to issue fork.
-
Rajeshreeputra →
committed 246ae2df on 2.0.x
Issue #3435372 by Rajeshreeputra, joseph.olstad: Automated Drupal 11...
-
Rajeshreeputra →
committed 246ae2df on 2.0.x
- 🇨🇦Canada joseph.olstad
@Rajeshreeputra, 9.3 should be removed
#3446051: ^9.3 || ^10 possibly fouls up the rector AND got a patch with open issues → -
joseph.olstad →
committed 1e74c02f on 2.0.x
Issue #3435372 by joseph.olstad, Rajeshreeputra: Automated Drupal 11...
-
joseph.olstad →
committed 1e74c02f on 2.0.x
- 🇨🇦Canada joseph.olstad
joseph.olstad → changed the visibility of the branch 2.0.x to hidden.
- 🇮🇳India rajeshreeputra Pune
@joseph.olstad given that we are utilizing the deprecation handler introduced in version 10.1, I would suggest that we consider discontinuing support for version 10.0 as well.
Also fixed the tablePrexif → deprecation.
- Status changed to RTBC
3 months ago 8:38pm 2 October 2024 - 🇨🇦Canada joseph.olstad
Latest tagged release "should" work with D11. The Automated script didn't catch the deprecation issue related.
🐛 Error: Call to undefined method Drupal\mysql\Driver\Database\mysql\Connection::tablePrefix() Active
- 🇫🇷France johnatas
Hello @joseph.olstad,
I confirm that the latest tagged release work with D11.
But its installation must be done with Lenient because the composer.json doesn't accept ^11 core.
Can we make this change in this issue?I suggest aligning the composer.json with the .info file of 2.0.7.
I attached a patch with this modification.
- 🇫🇷France johnatas
Note that the use of
DeprecationHelper::backwardsCompatibleCall
is no longer necessary if the minimum version defined is 10.1 ;) -
joseph.olstad →
committed 63e589a9 on 2.0.x
Issue #3435372 by johnatas: Automated Drupal 11 compatibility fixes for...
-
joseph.olstad →
committed 63e589a9 on 2.0.x
Automatically closed - issue fixed for 2 weeks with no activity.