Closed (fixed)
Project:
Webform
Version:
6.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Dec 2020 at 19:40 UTC
Updated:
20 Jun 2021 at 01:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jrockowitz commentedWe can use this ticket to gradually work on supporting PHP 8.
@see #3109885: [meta] Ensure compatibility of Drupal 9 with PHP 8.0 (as it evolves)
@see https://www.drupal.org/node/3180764
Comment #3
necalex commentedThe data in the forms are saved on the site, but do not go by email to admin
Drupal 9.1.0, PHP 8.0 , Webform 6.0.0
Comment #4
jrockowitz commentedComment #5
jrockowitz commentedI could not get php-compatibility check working but this could help confirm that Webform is compatible with PHP8.
Comment #6
jrockowitz commentedDrupal test bot now supports PHP 8. @see https://www.drupal.org/pift-ci-job/2000439
I think someone could create an issue forks, run the test bot to catch all the PHP 8 issues, and then fix them.
Let's see what happens with the current test run.
Comment #8
cilefen commented@jrockowitz A standalone PHP-Compatibility scan finds nothing on 6.x. That's not a guarantee of success, but it's something.
Comment #9
jrockowitz commented@cilefen Thanks for doing the scan. I did not know that PHP Code Sniffer supported this feature.
It seems helpful to add PHP version compatibility checking to RELEASE-NOTE.md.
Once I commit the attached patch we should close this ticket.
Comment #12
jrockowitz commentedComment #13
jrockowitz commentedComment #14
paulocsThis issue is not fixed yet.
If you run a drush command like
drush webform-exportwith PHP 8, the error bellow is displayed:Error: Unknown named parameter $webform in call_user_func_array()See: https://www.php.net/manual/en/function.call-user-func-array.php#125953
I'll open a follow-up issue to fix it.
Comment #15
paulocsBtw phpcs does only a static validation.
Comment #16
cilefen commented@paulocs Sounds good, thank you. The compatibility scanner is not comprehensive.
Comment #17
jrockowitz commentedMarking this fixed because the known PHP 8 issue was resolved in a new ticket