-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Content staging does not update coupon codes when related Rule's coupon setting is "Auto" (Magento_Reminder) #39588
Comments
Hi @TheBadong. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Bravo. Thank you for working on this issue.
|
Hi @TheBadong, Thanks for your reporting and collaboration. We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshots. ![]() ![]() We are not able to see the any errors in the log files. While scheduleing a new update there is no field to update the expiration date for the coupons.Could you please let us know if we are missing anything. Thanks. |
Hi @TheBadong, This issue is being closed since it has not been updated in a long time.Please feel free to reopen or raise a new ticket if the issue still exists. Thanks. |
Preconditions and environment
Steps to reproduce
Expected result
The generated coupons should see their expiration_date field updated in the database, and no error logs should be generated.
Actual result
The coupons are not updated and an error pops up in var/log/debug.log : "An error occurred during processing; coupon with id expiration date wasn't updated. The error message was Specified rule does not allow auto generated coupons".
Additional information
I'm not sure why the Auto option for the coupon settings is added by the Magento_Reminder module. See \Magento\Reminder\Observer\GetCouponTypesObserver. Maybe this should be mentioned in the module's README.
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: