Randomly our checkout has started failing & re...
# support
j
Randomly our checkout has started failing & redirected to the cart path -- it looks like due to
params.key?(:checkout)
in the
update
method in the
order_controller
on the frontend. It's truly strange though cause it happened in production while no code deploy happened -- and i don't see checkout added as a param in the base frontend code either. Is there possible something change in the browser? 0.o quite confused by this one..
e
IIRC the “checkout” param comes from the submit button name attribute, you sure nothing changed on that side?
j
thanks for the reply! Yeah the name value is still there -- however i'm not seeing it in the params of the request anymore (this is in safari)
i've also just based back the original frontend code and the issue is persisting
looks like it's in chrome too -- super confusing!
e
🤔 I was about to ask for a different browser, and to check any browser extension…
j
yeah it seems to just have started not sending that params totally randomly about 8-9 hours ago
e
with safari is pretty easy to disable JS, can you try doing that if possible, and inspecting the network requests to see if the param is there?
j
aha! that fixed it!
but -- I have no idea why 😅
I'm using turbo let me try disabling that
e
so, JS is some how preventing the button name attribute from being sent with the form… I would look ಠ_ಠ at any 3rd party script that could have been updated by the vendor… GTM/Segment/tracking stuff… etc
j
must be one of those...
yikes!!!
thanks so much for the tip how the heck did you think of that!
e
LOL, we once had a heart attack because the production home page suddenly was pitch black, we thought of hackers and a 1000 other things… turns out the ad-blocker we had on our machines was removing any element with “marketing” in its CSS class 🤷‍♂️
j
yep totally right -- i have an environment variable to turn off analytics locally and switching it off resolves it -- i'm using facebook, analytics G4, & mixpanel
LOL
omg -- yeah some things you just need to get burned on... I'll figure out what tracker it is maybe there's a setting -- it took some tweaks to get g4 to play nicely with rails in some cases
Yeah it's something new in G4 tracking head
e
there! 😅
j
alright -- well i wasn't able to figure out why this happened with g4, but atleast disabling it for now till i can figure out a better solution works! thanks so much @elia -- that was a life saver
e
no problem, I think you should try to tell them their latest release has this issue, them fixing it would be the best outcome
j
definitely -- they're so hard to get in touch with though 😅
👆 1