-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
addRecurring missing required variables #7808
Comments
Also noticed that the |
In system/library/cart/cart.php file, find:
add right below:
See if that solves the issue. Also found on the master branch. |
Whilst I have resolved the issue by creating a modification, it is still unfortunately a bug.
As you can see from my fix above, it is only passing the recurring profile to the |
This solution has now been added on the pre-release version. |
Thank you very much! |
What version of OpenCart are you reporting this for?
3.0.3.2
Describe the bug
Errors below are thrown when confirming an order with recurring products:
<b>Notice</b>: Undefined index: product_id in <b>/redacted/public/store/catalog/model/checkout/recurring.php</b> on line <b>4</b><b>Notice</b>: Undefined index: quantity in <b>/redacted/public/store/catalog/model/checkout/recurring.php</b> on line <b>4</b>
To Reproduce
Steps to reproduce the behavior:
order_recurring
table ifproduct_id
andproduct_quantity
have been populated.Expected behavior
Expected the product id and quantity to be provided to
addRecurring
to allow it to be associated with the recurring order.Screenshots / Screen recordings
Server / Test environment (please complete the following information):
Additional context
Looking at all uses of
addRecurring
, it appears only the recurring profile is passed, which does not include the quantity or product id. This is confirmed by carrying out a number of tests using different payment gateways with the same issue.The SagePay Server payment gateway fails to redirect to SagePay due to the errors being included in the JSON response.
The text was updated successfully, but these errors were encountered: