Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › eStore Buy Now returning error 14 and error 404
- This topic has 6 replies, 2 voices, and was last updated 6 years, 9 months ago by admin.
-
AuthorPosts
-
February 3, 2018 at 6:22 am #14676kjodreyMember
I’m using WP eStore and have integrated it with Authorize.net. Created products and added them to a test page [http://knocard.com/buy-now-test]. When I test the Buy Now button I get 1 of 2 errors, depending on different settings I’ve tried.
Initially I was receiving the error (14) The referrer, relay response or receipt link URL is invalid. Checked forums and found that this can happen if eStore and Authorize have different return urls. I checked and found that both the Return URL setup in eStore and the Default Receipt URL and Default Relay Response URL in Authorize are all set to the same url. I also found that the Silent Post URL setting in Authorize was set to [http://knocard.com/authnetcallback.php]. This setting had been configured when I was using a different plugin. I changed the Silent Post URL to match the return URL specified in the previously mentioned settings and when I tested I received a 404 page not found error.
At this point I had not added the WP Cart for Digital Products in the widgets section, so I added into my test page. When I retested the error changed from 404 back to the error 14.
I’ve already spoken to Authorize support, and confirmed that there are no problems with my setup on their end.
The page that contains my test Buy Now buttons is [http://knocard.com/buy-now-test]. Thanks so much for your help!
February 3, 2018 at 7:11 am #77225kjodreyMemberI’m also using WP Affiliate Platform and thought maybe my problem was that I was clicking Buy Now without using a referral link. Went in and grabbed an affiliate link and used it to access the payment page. When I clicked Buy Now the error, which had been error 14, had switched back to 404. The affiliate link is [http://knocard.com/pricing-2/?ap_id=375719] and directs to our pricing page rather than to the test page mentioned above.
February 4, 2018 at 12:10 am #77226adminKeymasterFixing the 404 error is easy. Take the URL in question and enter it in the browser’s address bar to verify that the URL actually loads. If it doesn’t then you know that there is a typo somewhere in the URL.
Looks like you have a mixture of “www” and “non-www” URLs that you setup in the plugin’s configuration. This will cause you some headache. Please read the following page and then update all the URLs in the settings to use only one version (the one you prefer):
Also, you should do the following test:
https://support.tipsandtricks-hq.com/forums/topic/test-to-identy-a-conflicting-theme-or-plugin
February 5, 2018 at 5:37 pm #77227kjodreyMemberThanks for your reply, but I’m still getting the error 14 when I try to check out. I have checked all of the plugin and Authorize links that are used to process the transaction and send the user back to the desired page. All settings display it the same.
I have also deactivated all of the plugins except the estore plugin, and have reset my theme to the default theme. Neither of these techniques made a difference.
Page that includes the Add to Cart button is [http://knocard.com/buy-now-test]
Please help!!
February 6, 2018 at 1:18 am #77228adminKeymasterThis one is an issue with the account setup.
What happens if you delete the default URL values that you set in your auth.net account?
The following post is a good read for this topic:
https://support.tipsandtricks-hq.com/forums/topic/return-url-not-working-w-authorizenet
February 6, 2018 at 6:07 pm #77229kjodreyMemberThank you…. that solved the problem! May I suggest that info such as this be added to the user documentation? This took me 4 days to get resolved (because of the weekend), and would have been clear to me if it had been included. Thanks again for your help!
February 6, 2018 at 11:30 pm #77230adminKeymasterThe thing is that there doesn’t seem to be any magic formula for this auth.net account setup issue. For most of our users auth.net we see that the default account setup just works. For a few users (maybe the ones who tweaked the settings some) auth.net seem to do this. So we can only point out what that error actually means and what are the things to try.
-
AuthorPosts
- You must be logged in to reply to this topic.