I have updated to Suitecommerce Advanced 2023.1.2 ...
# suitecommercem
Michelle Beutler
08/09/2023, 4:32 PMI have updated to Suitecommerce Advanced 2023.1.2 and am getting a redirect loop on some pages. It seems to detect a matching item page fragment and appends ?quantity=1, which then sends it into a 301 redirect loop. This is an old link with a subfolder in the url that does not work in SCA, but it still out there indexed in google or bookmarked, etc. Just wondering if anyone has encountered this issue? I do have a support case open, but not getting anywhere yet. Looking in the code it appears to have something to do with SCIS, although we don't use that.
s
Steve Goldberg
08/09/2023, 4:42 PMI’m looking at your case. How have you set up the redirect URL because it looks like you set up a redirect that points to itself?
m
Michelle Beutler
08/09/2023, 4:48 PMHello, if we remove ALL redirects the page works correctly, or if we are logged in so the SEO page generator doesn't fire, it also works correctly. But otherwise we get this loop with the ?quantity=1 appended. However, there's no exact match in the redirects that I can see that would loop, unless there's some hidden matching on /en for language? I removed everything I could find in the redirects that might be an issue.
s
Steve Goldberg
08/09/2023, 5:09 PMWell, the redirect is happening in the SEO page generator. I think the appending of quantity=1 is a red herring - it’s standard functionality. I’ve never seen “Redirected from SEO generator.” as a redirect reason before
Steve Goldberg
08/09/2023, 5:09 PMIf it was a redirect that you had created then it would say “user-defined redirect”
m
Michelle Beutler
08/09/2023, 5:14 PMI only get that "SEO Generator" SEODebug message if I am detected as logged in. If you need a web user login to test with I can provide one on the case, just let me know.
s
Steve Goldberg
08/09/2023, 5:19 PMI get it while logged out
Steve Goldberg
08/09/2023, 5:19 PMIn the response headers
m
Michelle Beutler
08/09/2023, 5:20 PMOK, thank you for looking into it.
s
Steve Goldberg
08/09/2023, 5:30 PMIt’s EOD for but it is certainly very curious. The only thing that stands out is this content block, which is referencing the local version of your shopping domain. It seems like an odd thing, recreating it with a correct path?
Steve Goldberg
08/09/2023, 5:31 PMI’m actually surprised it works at all
Steve Goldberg
08/09/2023, 5:32 PMIt certainly looks like a problem in the page generator somewhere. If you swap out the problematic URL into the DOM and just click a fake link to the URL, it redirects correctly
Steve Goldberg
08/09/2023, 5:32 PMSo IDK, it’s like there’s some script running at page generation that makes it get stuck in a loop
m
Michelle Beutler
08/09/2023, 5:32 PMYes that's pointing at an old touchpoint. Hmm.
Michelle Beutler
08/09/2023, 5:34 PMThat's on production or the support copy?
s
Steve Goldberg
08/09/2023, 5:35 PMproduction
Steve Goldberg
08/09/2023, 5:35 PMAlso it’s not the specific product URL per se that’s the problem, it’s the evaluation of the structure
Steve Goldberg
08/09/2023, 5:36 PMAs long as you use the path for any valid product you can put crap before it and cause the error
Steve Goldberg
08/09/2023, 5:36 PMeg /weifweiofjwioefjiow/matrikx-chloraguard-4-25-x-9-75-36-450-10-green will cause an error
Steve Goldberg
08/09/2023, 5:36 PMThe routing system is trying to strip out the garbage at the front but then, for some reason, going to that url and starting again
Steve Goldberg
08/09/2023, 5:38 PMAnd I can replicate this problem on any site: https://suitecommerce.stevegoldberg.co.uk/fwefwefwefwef/Rishi-Jacket for eg
m
Michelle Beutler
08/09/2023, 5:42 PMOK, good, so we know it's not just us then.
m
Michelle Beutler
08/09/2023, 6:30 PMI did see something about redirects fixed in backbone 1.4.1 routes, but not sure if that applies to this situation. Let me know if you need any more info from me. Thank you!
3 Views