Posted by jrperry on November 4, 2012 at 4:25am
I have an issue with a site that I'm working on right now with Ubercart. When somebody is logged in as some form of authenticated user, any attempt to go to an e-commerce related page (product pages, shopping cart, checkout, etc.) gets a redirect to a page called invalid_purchase# I haven't the foggiest idea of why this is, but I need to fix it. I'm using D7. As always, any suggestions are greatly appreciated.

Comments
is it any ecommerce page or
is it any ecommerce page or any https://page
Any e-commerce page, any
Any e-commerce page, any logged in user.
Did you check the error logs
Did you check the error logs for anymore info? Never seen an issue like this before. Whats the path to the invalid_purchase# page
Sounds like you may have
Sounds like you may have inherited a site from somebody else ... invalid_purchase is not something implemented by Ubercart, so it's probably something set up by whoever built your site.
Also check your installed modules, .htaccess file.
For clues, check your installed module directory, contributed and custom and one of those may give you an idea of why the redirect is happening.
http://drupal.org/project/redirect
http://drupal.org/project/globalredirect
etc.
Also the .htaccess file may have an actual redirect, not sure why, but could easily be causing a redirection.
http://drupal.org/node/38960
Drupal StackExchange
More questions...
Update
Thanks for everybody's input and thoughts. So here is the situation. I checked the .htaccess file for any redirects. There are none. I installed the redirect modules to show any possible redirections. There are none. The error log only shows an error when the invalid_purchase page has an attempted access, and not an error from trying to access an e-commerce page in the first place. There are no protocol switches, all same server, etc.
This site was originally set up by me and I had it properly working at one time. My client has made some modifications and while he claims that he only modified the actual product pages, I can't put it past him that he may have inadvertently modified some other setting without knowing it.
may not be related, but what
may not be related, but what server are you running? Apache, Nginx?
I ran into an issue on Nginx that the file type on the server level was being blocked. Just made a small change to a config file and it started working just fine.
PHP Filter enabled?
If your client has access to the PHP filter, they might have put some drupal_goto() commands in a node or block body somewhere.
If you can answer some of the questions above that should help narrow down the problem!