|
Colin Stearman
|
August 11, 2012 at 11:23 am
If you set this to YES then the payment selection screen briefly appears and then automatically relocates to the authorize.net payment screen. Not so bad, although a little off-putting to the user. It should relocate without displaying the intermediate page.
However, the real problem seems to occur with the Relay Response (Thank You) page. This is supposed to display the results of the transaction, good or bad. But (at least on the bad) it displays briefly again and the goes back to the authorize.net payment page. There’s certainly not enough time for the user to see what went wrong. So he seems to be in a loop with no explanation. Not good.
IMHO, the relocation should not take place, regardless of the setting, when the Relay Response page is being displayed.
An obvious work-around is to set the setting to NO.
-
This topic was modified 11 years, 9 months ago by
 Seth Shoultes. Reason: Moving to correct forum
|
|
Sidney Harrell
|
August 12, 2012 at 4:02 pm
Hey Colin,
That’s a very good point about the redirect on the thankyou page, I haven’t heard it brought up before, or I would have done something about it. It makes sense, because if the payment is not marked as complete, the thank you page attempts to display the payment buttons again, which causes the redirect to the thankyou page.
The problem with the redirect on the payment page is that it is running off the shortcode on the registration page, which doesn’t get run until it tries to display the page content, which is after the template header have already been displayed. We’ll have to put in some code in that gets run before the html headers are sent that will look at the request to see if we are on the payment page, and if so do an action. And put the redirect into a function hooked to that action.
Give me a couple minutes and I’ll put together some code for you (and our next update)
|
|
vchatham
|
August 16, 2012 at 12:24 pm
Does this redirect short code not work in some browsers?
|
|
Richard Stearman
|
August 16, 2012 at 1:45 pm
As short codes are replace by PHP I can’t imagine that they are browser-sensitive, but I defer to Sidney.
|
|
Josh
|
August 16, 2012 at 1:49 pm
It’s not a known issue where the redirect feature doesn’t redirect. The major issue originally brought up in the post is this: if the payment does not go through, it loops back again to auth.net.
For now, I’d recommend disabling this feature if you have issues with some of the payments not going through the first time.
|
