Skip to content
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

Upgrade to Magento 2.4.7-p3 error in PaymentServicesPaypal module #39442

Open
1 of 5 tasks
d-kochnov-optimus opened this issue Dec 5, 2024 · 1 comment
Open
1 of 5 tasks
Labels
Issue: ready for confirmation Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.

Comments

@d-kochnov-optimus
Copy link

Preconditions and environment

Magento version: 2.4.7-p3
After upgrading from Magento 2.4.7 to 2.4.7-p3 and from PaymentServicesPaypal module 2.4.3 to 2.9.0

Steps to reproduce

Place order using the REST API /V1/guest-carts/:cartId/order.

Expected result

Order successfully placed.

Actual result

Error:

str_starts_with(): Argument #1 ($haystack) must be of type string, null given
/home/budsies/website/vendor/magento/module-payment-services-paypal/Plugin/OrderUpdate.php

Additional information

The plugin tries to get a quote payment method ($quote->getPayment()->getMethod()) while the payment is not set for the quote yet because it sent in the CartManagementInterface::placeOrder second paymentMethod argument.

Compared with placing an order from the Magento Frontend, the GuestPaymentInformationManagement::savePaymentInformationAndPlaceOrder method is used, which saves the payment into the quote before the CartManagementInterface::placeOrder method is called (without the second paymentMethod argument).

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”.
Copy link

m2-assistant bot commented Dec 5, 2024

Hi @d-kochnov-optimus. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: ready for confirmation Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.
Projects
Status: Ready for Confirmation
Development

No branches or pull requests

2 participants