We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi there,
we had an address validation error (which is correct as the address was not correct) but the response from Payone lead to a PHP notice in the module.
In https://github.com/PAYONE-GmbH/magento-2/blob/master/Model/Api/Request/Consumerscore.php#L118 it is expected that the response has the score field, but in a case of a wrong address the response looks like:
score
[04-Jul-2017 07:29:34 UTC] array ( 'status' => 'INVALID', 'errorcode' => '4041', 'secstatus' => '30', 'errormessage' => 'Address not found', 'customermessage' => 'Address not found. Please verify your data.', )
That is the reasons why line 118 throws a notice and nothing happens in the frontend (no message).
Thanks for your help :-)
The text was updated successfully, but these errors were encountered:
We'll look into it (MAG2-33).
Sorry, something went wrong.
What is the current status of this? We are still experiencing the issue :-)
We ( @FATCHIP-GmbH ) are still working on that. We'll inform you immediately when this issue is solved. Thank you for your patience!
MAG2-33 - Fixed the php notice message
d882296
Fixes PAYONE-GmbH#83
No branches or pull requests
Hi there,
we had an address validation error (which is correct as the address was not correct) but the response from Payone lead to a PHP notice in the module.
In https://github.com/PAYONE-GmbH/magento-2/blob/master/Model/Api/Request/Consumerscore.php#L118 it is expected that the response has the
score
field, but in a case of a wrong address the response looks like:That is the reasons why line 118 throws a notice and nothing happens in the frontend (no message).
Thanks for your help :-)
The text was updated successfully, but these errors were encountered: