- 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 → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.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.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-181965These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- 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 → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.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-185727These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- 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 → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.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-188138These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
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 theinfo.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-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
- 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
Not addressed yet but maybe a good hint for follow ups:
Deprecated API use for APIs removed in future Drupal major versions is not required to fix yet.
web/modules/contrib/duration_field/src/Element/DurationElement.php 41 Class Drupal\duration_field\Element\DurationElement extends deprecated class Drupal\Core\Render\Element\FormElement. Deprecated in drupal:10.3.0 and is removed from drupal:12.0.0. use Drupal\Core\Render\Element\FormElementBase instead.
web/modules/contrib/duration_field/src/Element/GranularityElement.php 20 Class Drupal\duration_field\Element\GranularityElement extends deprecated class Drupal\Core\Render\Element\FormElement. Deprecated in drupal:10.3.0 and is removed from drupal:12.0.0. use Drupal\Core\Render\Element\FormElementBase instead.
- First commit to issue fork.
- First commit to issue fork.
- heddn Nicaragua
MR20 is now green. LGTM as it blocks https://www.drupal.org/project/datetime_extras → . All I did to this MR was review and make one minor fix to a test to get it green. I think that means I can still mark this RTBC.
- 🇮🇳India manishvaity
MR!20 Makes this module compatible with Drupal 11. Functionality is working as expected.
RTBC +1
- heddn Nicaragua
With force pushes and a series of confusing commits, I'm not sure what has happened since #12 when I last RTBCed this thing. It looks like my changes even disappeared. And we've regressed from green passing tests to failures. This is not RTBC ready.
- 🇪🇸Spain Francisco Sierra Madrid
Hi, folks. Thanks for maintaining this very useful module.
Are there any plans for releasing a D11 compatible version shortly?
Thanks! - ðŸ‡ðŸ‡ºHungary nagy.balint
I tried to reach out to the maintainers via their contact form, but received no response so far.
@heddn, Hi! Do you have your version from #12 somewhere so we could restart from there?
- 🇺🇸United States weekbeforenext Asheville, NC
If anyone needs a patch that can apply to 2.1.0 you can use this file. The MR patches don't apply because the packaging info is in the duration_field.info.yml file. This is a bandaid fix.
- First commit to issue fork.
- Status changed to Needs work
about 2 months ago 3:16pm 16 February 2025 - 🇺🇸United States bluegeek9
bluegeek9 → changed the visibility of the branch 8.x-2.x to hidden.
- 🇺🇸United States bluegeek9
bluegeek9 → changed the visibility of the branch 3429986-automated-drupal-11 to hidden.
- 🇩🇪Germany Anybody Porta Westfalica
Drupal 11 is out for some time and the module still isn't D11 compatible while widely used. Any further plans, at least for the dev version?
Thanks! :) - 🇷🇴Romania claudiu.cristea Arad 🇷🇴
Two issues here:
- It would be good to address also #8 📌 Automated Drupal 11 compatibility fixes for duration_field Needs review because is listed by upgrade_status as an issue
- To make sure everything works, we need to add a
.gitlab-ci.yml
that ensures testing for both, Drupal 10 and 11.
- 🇳🇱Netherlands Martijn de Wit 🇳🇱 The Netherlands
Is the plan to go D11 at 2.x and 3.x or only 3.x ?
- 🇺🇸United States bluegeek9
Testing is expanded to D10 and D11 here: 📌 Set up initial CI/CD automation Active