LOL, article is hidden when uBlock is active. Way to go!
Ad block shouldn't break your checkout
31–40 of 204 posts
Re: Ad block shouldn't break your checkout
#32Re: Ad block shouldn't break your checkout
#33(I did not bother trying to explain this to a human on the phone, because of the aforementioned alternate solution. That just sounds a supersized order of pain.)
Re: Ad block shouldn't break your checkout
#34TBH I don't see this as a TeeSpring problem - the code on their page guards against a realistic scenario (the GA script fails to load), but the "break" is caused by uBlock's changes. The article's title is correct: ad block shouldn't break checkout. Injecting a bogus value into a global breaks checkout, so ad block shouldn't do that.
A shopping site breaking checkout when there's a google analytics problem is madness, IMO. uBlock Origin is hugely popular. With 10M (claimed) active users, you should probably be testing against uBlock Origin for your e-commerce site.
As an aside, buying from TeeSpring was a little... interesting. You add the items to your cart and pay like at any other site. Instead of being charged for the total, I got invoiced separately for each (including separate confirmation emails), along with 5 or 6 duplicate shipping notices for one of the items. My credit card was also charged separately for each item. I get that there are probably reasons for this purchase flow, but it's not implemented well.
I got my stuff and all is good, but the whole buying experience was janky.
Re: Ad block shouldn't break your checkout
#35Low quality JavaScript shouldn't break your checkout. This is the type of issue that could have been caught by aggressive type checking.
Re: Ad block shouldn't break your checkout
#36Re: Ad block shouldn't break your checkout
#37I remember trying to order from a pizza place that talked to a third party delivery site, I hit "Order" and the browser didn't do anything. DevTools told me it tried to talk to the 3rd party using HTTP although the page was in HTTPS, and the browser blocked it (this was years ago when browsers started blocking HTTP content on HTTPS sites). Modifying the submit URL to https solved the problem. I found it pretty funny…
> Yes, can I take your other?
> No, you don't get it, I'd like to file a bug report, but your website clearly has no feature to create issues so, when the field city has the value...
> Sir, I cannot fix the website. If you do not wish to make an order please hang up.
> Uhoh ok, sure, I'd like an anchovies pizza but instead of anchovies I'd like you to make sure that when the field city is set to Boston...
> Sir, I really cannot fix the website
> Couldn't you just make a note and leave it in the front door? So that if other customers have the same problem they can upvote the most common issues and then you can prioritize fixes and get a reasonable budget for each one?
> I obviously can't do that, do you want your anch...
> Of course you can't! That would be reinventing the wheel! Let me point you to the github...
Re: Ad block shouldn't break your checkout
#38I am an author of a photo editor https://www.Photopea.com . Whenever someone reports a bug to me, I ask them if they use any site-modifying extensions. If they do, I ignore them completely, even if they wrote a long, detailed report. Web authors make websites for standard web browsers. I do not consider a browser with site-modifying extensions to be a standard web browser, and it is not my job to test my website with…
> I ask them if they use any site-modifying extensions. If they do, I ignore them completely, even if they wrote a long, detailed report. Note to self, don't use Photopea due to poor customer support. You would think the customer support would at least tell them to remove/disable the add-ons instead of ignoring them.
Re: Ad block shouldn't break your checkout
#39Re: Ad block shouldn't break your checkout
#40I remember trying to order from a pizza place that talked to a third party delivery site, I hit "Order" and the browser didn't do anything. DevTools told me it tried to talk to the 3rd party using HTTP although the page was in HTTPS, and the browser blocked it (this was years ago when browsers started blocking HTTP content on HTTPS sites). Modifying the submit URL to https solved the problem. I found it pretty funny…