-
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
Allmethods config source model does not always report the full list of payment methods #13460
Comments
@moehrenzahn, thank you for your report. |
@moehrenzahn The issue is already fixed in |
@magento-engcom-team What are the commits for this issue? |
I want to note that this issue is definitively still reproducible on 2.2.4. @magento-engcom-team, can you please check this. |
@magento-engcom-team A quick fix would be to only set the value if it doesn't already exist (fixed in src/vendor/magento/module-payment/Helper/Data.php lines 296-298)
|
Fixes Issue magento#13460, keeps changes from pull request magento#12284
Hi @moehrenzahn. Thank you for your report. The fix will be available with the upcoming 2.2.5 release. |
Fixes Issue magento#13460, keeps changes from pull request magento#12284
Hi @moehrenzahn. Thank you for your report. The fix will be available with the upcoming 2.3.0 release. |
FYI it will be released in 2.2.6 we see that the PR is merged only in this version |
The
Magento\Payment\Model\Config\Source\Allmethods
config source model does not display every available payment method.Preconditions
Steps to reproduce
Expected result
Actual result
Comments
I have tracked the source of the issue down to the
app/code/Magento/Payment/Helper/Data.php::getPaymentMethodList()
method, which does not report the full list of payment methods when$asLabelValue = true
and$withGroups = true
.The issue was apparently introduced with this commit, which does not consider that a group's $labelValues[$code]['value'] might already hold payment method information:
This is the issue for that pull request:
And this is the issue that prompted the problematic pull request:
The text was updated successfully, but these errors were encountered: