Process a Boku success redirect (bug 987841) #431
Conversation
| # the payment provider changed their URL parameters. | ||
| log.info('no transaction found for provider {p}; url: {u}' | ||
| .format(p=helper.provider.name, u=request.get_full_path())) | ||
| return HttpResponseNotFound() |
There was a problem hiding this comment.
can't remember, but the transaction is also in the session? if so, is it worth checking to ensure its the correct transaction?
There was a problem hiding this comment.
oh wait you do that in transaction status
There was a problem hiding this comment.
This doesn't do more than get the transaction ID from the Boku query string and expose it to the UI. I could require it to be in the session but it seems maybe overkill.
There was a problem hiding this comment.
Yeah, the JSON view that gets actual transaction data checks the session
|
r+wc |
|
I found a way to test this locally and it's not working! Let me dig in... |
|
This is working for me locally now but I can't get server notifications to my localhost so it may not be fully working. |
|
@muffinresearch I had to re-jigger the UI here, r for just the JavaScript bits? |
| @@ -493,6 +493,8 @@ | |||
| 'ajax_timeout': 45000, | |||
| # Wait timeout (Default 60s). | |||
| 'wait_timeout': 60000, | |||
| # Poll interval (milleseconds) while waiting for something to happen. | |||
The JS changes lgtm, but I think this is another one that's going to be easiest to test when on stage. |
Process a Boku success redirect (bug 987841)
No description provided.