- Issue created by @project update bot
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
about 1 year 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-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
- Status changed to Needs review
about 1 year ago 7:32pm 4 April 2024 - Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
about 1 year ago Waiting for branch to pass - Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 8
42:33 42:33 Queueing 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
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 8
42:20 42:20 Queueing - First commit to issue fork.
- π¬π§United Kingdom malcomio
Having applied this patch and the patch from π Deprecated FormElement Active , upgrade status reports the following:
drush us-a phone_number ================================================================================ Phone Number, 2.0.0-alpha7 Scanned on Mon, 9 Dec 2024 - 17:09 FILE: modules/contrib/phone_number/modules/sms_phone_number/src/Element/SmsPhoneNumber .php STATUS LINE MESSAGE -------------------------------------------------------------------------------- Check manually 103 The 'sms_phone_number/element' library is not defined because the defining extension is not installed. Cannot decide if it is deprecated or not. --------------------------------------------------------------------------------
- Status changed to Needs work
13 days ago 7:51am 24 March 2025 - πΉπ·Turkey orkut murat yΔ±lmaz Istanbul
This is my upgrade status output, after applying the latest MR as a patch:
ddev drush us-a phone_number ================================================================================ Phone Number, 2.0.0-alpha7 Scanned on Mon, 03/24/2025 - 10:50 FILE: web/modules/contrib/phone_number/src/Element/PhoneNumber.php STATUS LINE MESSAGE -------------------------------------------------------------------------------- Ignore 36 Class Drupal\phone_number\Element\PhoneNumber 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. -------------------------------------------------------------------------------- FILE: web/modules/contrib/phone_number/modules/sms_phone_number/src/Element/SmsPhoneNu mber.php STATUS LINE MESSAGE -------------------------------------------------------------------------------- Check manually 103 The 'sms_phone_number/element' library is not defined because the defining extension is not installed. Cannot decide if it is deprecated or not. --------------------------------------------------------------------------------
- First commit to issue fork.
- πΊπΈUnited States chrisolof
Thanks everyone! MR 21 has been merged into 2.0.x and tests are now passing in a Drupal 11 environment.
- π§π·Brazil edsoncarlos
Hi, if the tag 2.0.0-alpha8 uses the FormElementBase, then this new tag is incompatible with drupal/core versions lower than 10.3.0-beta1, which is when this new class was implemented.
- πΊπΈUnited States chrisolof
Thanks edsoncarlos! Looks like we missed that over in π Deprecated FormElement Active . Issue filed: π Bump up minimum Drupal version to 10.3 Active