Plugin Author
BitPay
(@bitpay)
Hello! We’ll take a look at this today. Please note that you do not need to use composer to install the plugin because we pre-package the vendor directory.
Hi, thanks. Its pre-packaged I known but plugin should support also 8.0 php version because many plugins and themes don’t support 8.1…
Plugin Author
BitPay
(@bitpay)
Hello,
PHP 8.0 is already only under security support, with 8.1 and 8.2 being actively supported. Being that our SDK and plugins deal with handling cryptocurrency, our new SDKs and plugins are going to follow officially supported language versions.
We are using PHPUnit 10 in our SDK, but we’ve confirmed that our tests will pass in PHPUnit 9. We’re updating our tests to run in both 9 and 10 in our workflow, and will rebuild our composer.lock file for PHP 8.0.
That said, if you just install the plugin, you should be OK on PHP 8.0 since there’s no need to run Composer unless you’re developing for the plugin.
We are working on making a few updates today in an effort to address the PHP 8.0 issue with Composer.
That said, please bear in mind that we will stop supporting PHP 8.0 on Nov 26, 2023 following its official EOL per https://www.php.net/supported-versions.php.
Thanks!
Plugin Author
BitPay
(@bitpay)
Hello again @risbo95 we just wanted to give you another quick update. We’ve updated the SDK and plugin repositories to address this specific issue and plan on releasing both either tomorrow or Monday.
Plugin Author
BitPay
(@bitpay)
@risbo95 this is deploying to the marketplace now. We’ve tested Composer with PHP 8.0, and tested the plugin. We have not run into any issues but definitely let us know if you come across anything. I’ll keep this open for a day or two.
Thanks, it seems that issue is fixed. I appreciate
Plugin Author
BitPay
(@bitpay)
Awesome! Thanks for spotting it – it was a huge help. We didn’t catch it because our GitHub Actions runners were using ubuntu-latest, which very recently switched to 22.04. The image for this version does not include PHP 8.0, and does not fail when it’s passed into a version matrix. This resulted in 8.1 being used to run composer install as well as tests on 8.0 and 8.2 in the SDK.
We were able to stick with ubuntu-20.04 and run 8.0, 8.1, and 8.2, and have since split our tests between PHPUnit 9 and 10.
This was immensely helpful, and we really appreciate you reporting it. It’s a case that shows how the WP community really does help.
Hello @bitpay, it seems this issue is once again present as of 9/14/2023. I’m setting up a fresh WooCommerce store and I’m met with Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0". same as the OP when I attempt to activate the plugin. Any ideas?
-
This reply was modified 1 year, 1 month ago by
ellisrl.
Plugin Author
BitPay
(@bitpay)
Hi @ellisrl we’re looking into this, as it’s a result of a sub-dependency update. There was an issue with another plugin using a very outdated version of Guzzle, which caused issues. The solution to that was to introduce php-scoper (similar to Yoast) to prefix all vendor packages with a custom namespace.
We’ll check this out on our end. In the mean time, you should be OK to use the previous version prior to the introduction of php-scoper.
Please note that we are only supporting PHP 8.0 until November 26th, 2023 when it will reach the end of its security updates.
