Page Not Found on Checkout success_download
Permalink Browser Info Environment
For some reason I'm getting a page not found upon successful completion of Authorize.net AIM credit card payment. I checked the sitemap and the page is under the Checkout page where it should be. Any ideas why this might be happening?
Type: | Discussion |
---|---|
Status: | In Progress |
Bump. Does anyone have any response to this?
Can you tell me which URL's you're getting 404 for, and attach a screenshot of their location in the sitemap?
Thanks for your reply. Right now everything is setup with the default install. Like I said before, I can go to the page in the site map but when doing a checkout I get the page not found message. The URL of the page that comes up with the error ishttp://www.megagenius.com/index.php/checkout/success_download/.... This error only seems to happen with Authorize.net. Paypal works fine.
Can you private message me a set of new admin credentials that I can use to poke around? This page should be created and should exist at the path you provided, the fact that it isn't tells me either the page itself is misconfigured, or one of your overrides are doing something fancy.
Best wishes,
Korvin
Best wishes,
Korvin
After checking out your site, it appears your success page lives athttp://megagenius.com/index.php/checkout/success-download/... rather thanhttp://megagenius.com/index.php/checkout/success_download/....
I'm now sure how this could've happened through the standard concrete5 api, did you do anything funky to this page?
I'm now sure how this could've happened through the standard concrete5 api, did you do anything funky to this page?
Thanks for looking into it. We didn't change anything. I don't think you can even change a Single page URL like that one's name through C5. I believe it installed that way. Did you fix that or do I need to go in and change something? How would I go about changing the URL for that page?
The best way to do this would be to uninstall the package and verify that the single page has been removed, then reinstall and see if it gets added correctly.
I tested this out with the core version you used and everything went fine.
I tested this out with the core version you used and everything went fine.