Skip to content

Use notifyUrl not returnUrl for callback #7

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

Merged

Conversation

eileenmcnaughton
Copy link
Contributor

Omnipay supports a notifyUrl for callbacks and a returnUrl for the browser. This patch causes the notifyUrl to be used for callbacks by securePay

Omnipay supports a notifyUrl for callbacks and a returnUrl for the browser. This patch causes the notifyUrl to be used for callbacks by securePay
@delatbabel
Copy link
Contributor

Oops, I just saw this when I went to merge something else.

Can you please make this backwards compatible for existing users? Something similar got done for Authorize.Net -- use the notifyUrl if it's set but use the returnUrl if the notifyUrl is not set.

@eileenmcnaughton
Copy link
Contributor Author

I can't even remember doing this one - I think it was never put into use. But, I copied the code from a.net and actually learnt something - I didn't know you could have a blank in the ternery operator like that

@delatbabel delatbabel merged commit a7b1b55 into thephpleague:master Apr 12, 2016
@delatbabel
Copy link
Contributor

Once again if someone can test that this works in production I wiil tag.

@eileenmcnaughton eileenmcnaughton deleted the eileenmcnaughton-patch-1 branch November 19, 2016 03:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants