-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Null can not be used as a standalone type in Paypal Braintree Core #38775
Comments
Hi @GrimLink. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
I have the same issue too, after upgrading to 2.4.7 |
What version of PHP are you guys using? Is it 8.1? Because standalone type of I can confirm that the paypal/braintree module is using So this is a valid bug report, the people who maintain the paypal/braintree module should fix this. Quick fix would be to switch to PHP 8.2 or 8.3 |
I'm currently on PHP 8.1 I will try switching the PHP version. Thank you |
@hostep I am also using php 8.1, also why I am reporting this 😉 |
Hi @engcom-November. Thank you for working on this issue.
|
Hello @GrimLink, Thank you for the report and collaboration! Verified this on 2.4-develop branch.
Hence confirming the issue. Thank you. |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-12288 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-November. Thank you for verifying the issue. |
Why are you using PHP 8.1 with 2.4.7? |
Because you can, it's allowed by the Also, people really need to stop pointing to the system requirements, those aren't the real system requirements, but only a list of versions of software Adobe tests against. Yes, it's safer to stick to those versions, but if they allow other versions, then expect people to use other versions as well and report bugs about them. |
It's allowed in It sounds like more people need to pay closer attention to the system requirements, including you and the OP. What a silly take honestly. Good luck. |
Look, personally I always try to use the latest available PHP version that is compatible with Magento, we don't use PHP 8.1 for Magento 2.4.7 on any of our projects. I'm just saying that this bug report would have never existed if Adobe would have just removed the "so called" PHP 8.1 compatibility from their They do state on their release notes the following:
So yes, they claim "in words" that we should use at least PHP 8.2, but in technical terms they still allow for PHP 8.1. Also "for upgrade purposes only", what does that even mean? I don't see any good reason why you would want to use PHP 8.1 "during" an upgrade. Anybody who knows what this means? The only reason I'm complaining here, is that Adobe should make it so that their users can make fewer mistakes, defining the correct compatibility with PHP versions in the |
Preconditions and environment
Steps to reproduce
Run
bin/magento setup:di:compile
after a very short moment the following error is thrown:Expected result
No errors
Actual result
Additional information
No response
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: