-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
Does OpenMage LTS support Php 7.3.x? #716
Comments
I was doing some tests with PHP 7.3 (Debian Buster) on the original core (not LTS) and I didn't find any errors in our instance. Everything that I touched worked well. Still pending some more detailed tests. Looking at 7.3 backwords incompatibility docs and deprecation docs I think there will not be many problems; at least with core. |
We are running in problems with arrays in SOAP requests. Both when Magento is the SOAP client and when Magento is the SOAP server. Other than arrays, SOAP requests work fine. Unfortunately a large part of our APIs rely on arrays over SOAP. |
@iamniels I did not work much with this part yet, do you by chance have a small php example for the client, and an curl request for the server I can use as base to investigate this? |
maybe its not even directly related to soap, it could be one of them: maybe "Strict Interpretation of Integer String Keys on ArrayAccess" (just leaving this here as a note for myself) |
When I make a POST request with the following contents, Magento returns the Exception that the second argument of the Multicall function needs to be an array and it is an object. I made the request with the regular SoapClient with only the
|
This error pops up on PHP 7.3 and not on PHP 7.2. The suggested fix works. |
Fixed in #894 |
formal followup to #505
I just checked by installing Openmage for demo purposes on a 7.3 (and also a MySql 5.7)
You can check the demo out on http://www.openmage.cotya.org
I did once go through the Order Process and could finish the order without an error page shown.
But I could find a warning in magerun for some syntax issue.
The text was updated successfully, but these errors were encountered: