Automated Drupal 11 compatibility fixes for webform

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

These packages were used to generate the fixes:

1. drupal/upgrade_status: 4.3.4
2. mglaman/phpstan-drupal: 1.2.11
3. palantirnet/drupal-rector: 0.20.3

Merge request merged.

Leaving open for more patches.

Sorry that it is only a patch file,
but the update bot missed the version requirement.

And of course php 8.3 is now the minimum.

This issue is only for automated patches.

I will not be adding Drupal 11 to core_version_requirement until tests pass on that version.

Even when this is compatible with Drupal 11, Webform itself will not require PHP 8.3 since people will still be running Webform on Drupal 10 with older PHP.

Yes, sorry about the php version change.

I was just doing some test on my module on Drupal 11 which uses Webform, and I thought I share the diff.

I did not encounter any issues in my short testing though which is good.

VladimirAus → changed the visibility of the branch 3464277-automated-drupal-11 to hidden.

Liam Morland → closed merge request !500

Not according to the other repositories but OK. 😂
You might as well know when support for Drupal 11 is out, because this is exactly what this merge issue should be. 🤷

This is confusing. How many compatibility fix issues do we have for webform now? Why we do not use one. How can users now know which they should apply for testing?

Even when this is compatible with Drupal 11, Webform itself will not require PHP 8.3 since people will still be running Webform on Drupal 10 with older PHP.

Is this causing the multiple core 11 fix issue confusion? That's what different release versions and branches are for. Why not creating another branch for webform PHP 8.3? It is strongly recommended for Drupal core 11 and higher and other contrib will follow.

Webform 6.3.x is to be compatible with Drupal 11 and PHP 8.3. It will not require PHP 8.3; it's minimum will be Drupal 10.3 and PHP 8.1.x. The current focus is getting tests to pass in 📌 Fix test failures Active .

compatible with Drupal 11 and PHP 8.3. It will not require PHP 8.3
Sure. Cross compatible php 8.2/8.3 to make users able to use 6.3 under Drupal 11 with php 8.3 → and Drupal 10 with php 8.3 or 8.2.

Webform 6.2.x (for Drupal 10.1.x+) is the same as Webform 6.1.x with deprecated code removed and only for Drupal 10.1.x+. PHP 8.1+ required. This branch will receive security support until the Drupal 10.2 EOL.

Jesus! Why I haven't seen that this issue 📌 Automated Drupal 11 compatibility fixes for webform Needs work is already closed since 2 weeks *facepalm*...

Sorry for the noise, Liam. Nightshift eye syndrom. That was it all about what I wanted to care for.

ankitv18 → changed the visibility of the branch 3464277-automated-drupal-11 to active.

This issue is only for automated patches.

It's been 2 months since last changes and D11 already rolled out. Also I'm not seeing any projectBot patches suggestion.
So it would be great if webform get's D11 compatible as it is widely used in the drupal world.

I agree. Work is underway in ✨ Drupal 11 compatibility fixes for webform Active .