Page 1 of 1

Querystring confuses URL rewriting

Posted: Fri Aug 10, 2012 5:11 pm
by sloDavid
We want to use Google Site Optimizer to perform some A/B testing. However, it sends users back to the page they pulled up, but with two additional querystring parameters. This QS param causes AC to incorrectly display the category page instead of the product page.

E.g. (using fake URLs; don't click them):
1. Start on the category page: http://site.com/Test-Cat-C23.aspx.
2. Click on a product's link: http://site.com/Test-Prod-P89C23.aspx.
3. Javascript on the product page redirects the user to Google, and then Google in turn immediately redirects the user to an ALTERNATE product page:
http://site.com/Alt-Prod-P91C23.aspx?ut ... t-C23.aspx
4. AbleCommerce incorrectly causes the Test Category page to display instead of the Alt Product page. Yikes!

Is there any way to make AC ignore the -C23.aspx in the querystring param like it ought to???
We're using 7.0.6 for the site, but I've confirmed this on Version 7.0.7 SR1, too.

Re: Querystring confuses URL rewriting

Posted: Fri Aug 10, 2012 6:13 pm
by Shopping Cart Admin
Hello David,

While it's unfortunate that it's behaving this way. You're using the query string on a page that isn't meant to accept in a manner like you're doing. AbleCommerce is doing exactly as the programmers have instructed and is doing nothing incorrectly. There ought to be some kind of work around, hopefully someone more technical than I can pipe in with some assistance.

Re: Querystring confuses URL rewriting

Posted: Fri Aug 17, 2012 12:40 pm
by sloDavid
I'm going to have to respectfully plead with you that AbleCommerce is definitely doing something incorrectly here.

When I link to Alt-Prod-P91C23.aspx, then it should pull up a product page, regardless of the querystring. Anything else is undocumented, unexpected unusual behavior, and that's why it's incorrect. We rewrite friendly URLs to build querystrings; we don't rewrite querystrings to build URLs.

I've submitted a priority support case for this, so that it can at least be in your bug tracking for a future version. I hope I can change your mind on this. Today we need to find an alternative to Google Site Optimizer, and tomorrow it might be something else.