- Issue created by @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-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
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-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- First commit to issue fork.
- Status changed to RTBC
5 months ago 1:45pm 16 August 2024 - šŗšøUnited States BenStallings
MR!50 installs with composer and can be enabled in Drupal 11. Since the release branch also fails testing, I'm going to consider the testing problem to be outside the scope of this ticket.
- š«š·France dqd London | N.Y.C | Paris | Hamburg | Berlin
RTBC from here as well. +1
- š¹š·Turkey basak.burcu
In my Drupal 10 project, I installed ECK. However, I couldn't install it in Drupal 11 yet because it's not supported.
As a solution, I copied the eck.git section from the composer.lock file in the Drupal 10 project.
json
Copy code
{
"name": "drupal/eck",
"version": "2.0.0",
"source": {
"type": "git",
"url": "https://git.drupalcode.org/project/eck.git",
"reference": "2.0.0"
},
"dist": {
"type": "zip",
"url": "https://ftp.drupal.org/files/projects/eck-2.0.0.zip",
"reference": "2.0.0",
"shasum": "e1969212f4ce209e84d500a45133f0fe1b093795"
},
"require": {
"drupal/core": "^9.4 || ^10"
},
"type": "drupal-module",
"extra": {
"drupal": {
"version": "2.0.0",
"datestamp": "1683908568",
"security-coverage": {
"status": "covered",
"message": "Covered by Drupal's security advisory policy"
}
}
},
"notification-url": "https://packages.drupal.org/8/downloads",
"license": [
"GPL-2.0-or-later"
],
"authors": [
{
"name": "See contributors",
"homepage": " https://www.drupal.org/node/1155832/committers ā "
},
{
"name": "akalata",
"homepage": " https://www.drupal.org/user/498926 ā "
},
{
"name": "amykhailova",
"homepage": " https://www.drupal.org/user/2892725 ā "
},
{
"name": "Arrow",
"homepage": " https://www.drupal.org/user/423969 ā "
},
{
"name": "DieterHolvoet",
"homepage": " https://www.drupal.org/user/3567222 ā "
},
{
"name": "dpopdan",
"homepage": " https://www.drupal.org/user/2759811 ā "
},
{
"name": "eric.napier",
"homepage": " https://www.drupal.org/user/501688 ā "
},
{
"name": "fmizzell",
"homepage": " https://www.drupal.org/user/1312210 ā "
},
{
"name": "kelly.m.jacobs",
"homepage": " https://www.drupal.org/user/3397374 ā "
},
{
"name": "legolasbo",
"homepage": " https://www.drupal.org/user/2480548 ā "
},
{
"name": "Matroskeen",
"homepage": " https://www.drupal.org/user/3426249 ā "
},
{
"name": "mducharme",
"homepage": " https://www.drupal.org/user/616996 ā "
},
{
"name": "mihai_brb",
"homepage": " https://www.drupal.org/user/2065978 ā "
},
{
"name": "pifagor",
"homepage": " https://www.drupal.org/user/2375692 ā "
},
{
"name": "RobLoach",
"homepage": " https://www.drupal.org/user/61114 ā "
},
{
"name": "wjaspers",
"homepage": " https://www.drupal.org/user/813890 ā "
}
],
"description": "ECK (Entity Construction Kit) allows users to create and administer entity types, bundles and entities from the UI.",
"homepage": " https://www.drupal.org/project/eck ā ",
"support": {
"source": "http://git.drupal.org/project/eck.git",
"issues": " https://www.drupal.org/project/issues/eck ā "
}
}
For my Drupal 11 project, I took this code and manually added it to the composer.lock file. I updated the "drupal/core": "^9.4 || ^10 || ^11" part. Then, I added "drupal/eck": "^2.0" to the require section of the composer.json file.I also added patches in the project under eck.patch. After running composer install via the terminal, ECK is now ready.
- First commit to issue fork.
Fixed issue in Merge request !50 which was raised by dqd . Kindly review the Merge request !53.
- š§šŖBelgium dieterholvoet Brussels
We should probably make sure automated tests are passing before committing/releasing this one: š Fix tests Active
- š§šŖBelgium dieterholvoet Brussels
dieterholvoet ā changed the visibility of the branch 3430042-automated-drupal-11 to hidden.
- š§šŖBelgium dieterholvoet Brussels
There doesn't seem to be a good reason to drop support for Drupal 9.4, so I'm adding that back.
-
dieterholvoet ā
committed 3d008fa8 on 2.x authored by
project update bot ā
Issue #3430042 by sarigaraghunath, project update bot, realityloop, dqd...
-
dieterholvoet ā
committed 3d008fa8 on 2.x authored by
project update bot ā
- š«š·France dqd London | N.Y.C | Paris | Hamburg | Berlin
#19 š Automated Drupal 11 compatibility fixes for eck Needs review : There doesn't seem to be a good reason to drop support for Drupal 9.4, so I'm adding that back.
Absolutely right. 200% Agreed. TBH, I was in conflict on this previously already twice, but it was based on a "trend" in many contrib regarding PHP version support in sync with Drupal core. I wondered why so many users wanted me to remove Drupal 9 support on projects I maintain and they convinced me at this time. But this surely affects not all contrib modules.
#13 š Automated Drupal 11 compatibility fixes for eck Needs review : Sorry, but to be clear for the logs, there haven't been raised any issue but only work has been continued on MR50 in line with update bot and previous contributors and it just got some minor basic adds/changes for ^11 compatibility as a starting point. And functional and procedual changes and updates in the code base should always be rather discussed carefully with the project maintainers anyways. Also, please do not assign update bot issues to yourself.
Thanks @dieterholvoet for finally updating/fixing and merging a carefully written out commit. Do you prefer any existing follow ups to work on with prio for an upcoming release?
- š§šŖBelgium dieterholvoet Brussels
I spent the bigger part of the day on ECK, merging issues, fixing the automated test suite and fixing all code style issues in the codebase. The only other issue I want to merge before creating a release is š EckEntityRouteProvider does not use link templates Needs review , but that one needs a rebase. After that, Iām going to do a last round of manual testing and create a new release.
Automatically closed - issue fixed for 2 weeks with no activity.