-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Coupon and Gateway errors are displayed in flash_messages #4034
Comments
Hi Scott, which version of Spree is this on? On Sat, Nov 30, 2013 at 7:09 AM, Scott notifications@github.com wrote:
|
Hey @radar, sorry I forgot to add that I am using: `gem 'spree', '~> 2.1.2'``` |
Thanks! I'll take a look at this next week when I get a chance. Seems pretty straightforward. On Sat, Nov 30, 2013 at 9:31 AM, Scott notifications@github.com wrote:
|
Hi again @sc0ttman, I have got a fix in for the coupon problem in 2-1-stable and 2-0-stable -- in master we use the API to apply a coupon, so this patch is not needed there. I wasn't able to get a gateway error to display... do you have some steps to reproduce that kind of problem that I could try? |
Awesome @radar thanks! I seemed to have tracked the error message
I would imagine your flash.now fix would work here as well? |
Hrm, I tried applying your fix as a decorator in my app, and it still seems to be flashing the old way.
I even tried removing the error flash to make sure it was coming from that line, and it still displayed the error. Any ideas? |
Turns out the coupon code is being applied in the orders controller. Using your flash.now fix here does the trick! |
Thanks @sc0ttman! I've now got a couple of commits pending for 2-0-stable, 2-1-stable and master which will fix the gateway messages and coupon errors appearing more than they should. Thank you for pointing out where the |
…ller Otherwise this will carry over to the next request, which is not fun. Fixes #4034
…ller Otherwise this will carry over to the next request, which is not fun. Fixes #4034
The problem with this is that if you are in the checkout process, they take 2 page reloads to disappear. I think this is due to checkout pages being rendered instead of redirected and therefore the errors linger around for an extra page request.
Should these types of errors not be rendered in the checkout errors partial:
spree/shared/error_messages
?The text was updated successfully, but these errors were encountered: