-
Notifications
You must be signed in to change notification settings - Fork 19
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
Discount code rule not working? #9
Comments
I also think it's a bit confusing, when you had a manual code and how many times it can be used you see: Discount codes: 1 The text file contains 1 code, but you can't see how many times the code was set to be used.. and how many times left it can be used. The same when the codes are generated - they are added, but the "Max uses" needs to be more clear afterwards. |
Hi Bjarne |
Have you tried to use MS SQL and see if that works. Just to be sure if it is the SQL CE that make problems. |
Hi Anders I think it was a bit confusing because you can add discount codes, but you can't edit them (and see them without downloading the txt file). And I think I got the error, when adding an empty code and click on download (or just download before codes were added). I think I got the error when using SQL CE - I'll check it later or in this weekend. |
When I SQL CE locally in Umbraco 7 and click generate for a discount code rule, I get this error:
Response from server:
I think it a SQL CE thing, when generating the discount codes. |
It is a similar issue first time you add a discount code rule before you have added any discount codes. Response from server:
but I am not sure you want to support SQL CE? .. I mostly use it only for test purposes and easy setup, but in that case it seems to have some issues when using SQL CE. |
How is the "discount code rule" intended to work?
Both Manual and Generate doesn't seem to add content to "Discount codes:" and "Unused discount codes:" .. and the download link returns:
.. maybe because the discount code is null?
I should mention i have tested with SQL CE.
The text was updated successfully, but these errors were encountered: