-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix initial php 8.4 compatibility #2714
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2714 +/- ##
============================================
+ Coverage 63.4% 66.2% +2.8%
- Complexity 0 4691 +4691
============================================
Files 340 479 +139
Lines 5210 19608 +14398
Branches 1275 0 -1275
============================================
+ Hits 3305 12983 +9678
- Misses 1730 6625 +4895
+ Partials 175 0 -175
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This would also supersede #2663 |
Why not include this as the rest of the scripts like prefix-vendor-namespace.php? |
The first time you run this. It works. But if you run it another time It will result in: '??string $template = null' |
Is that consistently reproducible? I'm not seeing that happen here on any PHP version. Can you confirm if you run just the individual test on a specific PHP version if you get it to fail: Based on the results it means that it won't create a 20x20 thumbnail image. I wonder if there is a PHP image module that is different between versions of PHP. Can you also run: Just to see if there is a difference in PHP modules.
This means we are patching upstream libraries manually, it is an option, but instead we've asked them for compatible versions. Once we get the updated versions we won't need a script like that anymore. Considering that they are deprecation notices (shouldn't in theory be shown on production sites), I thought the better way was to wait till we get updated packages.
Yes, I should have mentioned that, it's a quick search/replace script so only intended for running once. |
@mikkamp Re Image test It does fail when running the test isolatedly. Find also the output for
Update: @mikkamp I was doing some debugging and found the error in
Update 2: Solved installing php8.4-imagick (as one of the editors) |
This is my php-v output btw
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mikkamp I solved the problem with the test. See ( #2714 (comment) )
So no more blockers left.
Thanks for clarifying. Either the Going to merge this, now that it's running fine. |
Changes proposed in this Pull Request:
This PR is the initial start for resolving the issues that are in #2647
There are still a few dependent packages we are waiting for provide full compatibility:
Resolved in this PR
Detailed test instructions:
rm -rf vendor && composer install
bin/fix-packages.php
php bin/fix-packages.php
bin/install-wp-tests.sh <db> <db_user> <db_pass>
/tmp/woocommerce-9.4.3/plugins/woocommerce
with the contents of the zip file provided belowwoocommerce-9.4.3-patched-for-php-8-4.zip
/usr/bin/php8.4 vendor/bin/phpunit
Additional details:
peeuvX-1Zh-p2
Changelog entry