-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Open
Assignees
@JMLucas96
Description
Preconditions and environment
- Magento version 2.4.8-p3
- Use of
$order = $this->checkoutSession->getLastRealOrder();
and then$order->getPayment()
shows different payment method every time, but un backoffice payment method still correct.
Steps to reproduce
- Make sure to have more than one payment methods to finish purchase.
- Debug
prepareBlockData()
function onvendor/magento/module-checkout/Block/Onepage/Success.php
- See how
$order->getPayment()->getMethod()
from$order = $this->checkoutSession->getLastRealOrder()
showing another method_code each time.
Expected result
Payment method is the selected on last checkout step.
Actual result
Payment method is randomly modified
Additional information
It seems that error comes from the last checkout step, when placing order I get the following error on savePaymentInformationAndPlaceOrder
method from vendor/magento/module-checkout/Model/PaymentInformationManagement.php
:
Since web-token/jwt-library 3.3.0: The parameter "$contentEncryptionAlgorithmManager" is deprecated and will be removed in 4.0.0. Please set all algorithms in the first argument and set "null" instead.
Release note
No response
Triage and priority
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, "quality" or "usability".
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Needs Update