Just an FYI:
There seems to be a bug in the Pattern shopping cart that once you go over 75 items, you'll get the "Oh dear. There seems to be an error with one of your listings" error.
The very bad part of this is that even if you remove EVERYTHING from your cart, then add one item, the error remains. I had to clear my cache to get rid of it.
I was lucky enough to have a customer tell me about it. I wonder how many people have gone through the trouble of adding 75 items and then got the error and left?
I know many of you don't sell the types of items where people will be purchasing 75+ of them at one time. I sell supplies, and that's rare for me, too! But I wanted to get it documented here, in case someone else did run into it. I did email Etsy Support, for what that is worth.
Thanks for the heads up. I would love to hear their response.
@funkydreamsmosaics, I wish someone would purchase 75 items from me at one time...Well, one can only dream.
Thanx for the update. I hope you get an answer from etsy.
For those of you following along:
The first response I received from Support was the template response of "we have a very high call volume" (AKA "we're understaffed"), with links to Pattern Help, which, of course, were useless. So I emailed back and told them, no, I don't need Help. I found a bug.
Second response came today. It was very polite and nicely worded. But it basically said we would need to know which 75 items were in your cart to reproduce (no, you don't) and that needing to clear the cache is common (no, it isn't).
@stufforama , I hope you don't mind, but I used your site to reproduce it again. You sell multiple of some of your items, so it was easier to work with. (So if you see a spike in traffic, that might have been me.) And lo and behold, after my cart reached 76 items, I got the error.
So I have replied BACK to the "Pattern Support Team" that it's a bug that is easily reproduced and they need to try harder.
I don't mind at all. The spike may be handy to see if their stats really work because I'm hearing conflicting opinions on it over at Reddit, so win-win! I don't know where you guys are even finding an active phone number because all I've ever gotten was an answering machine message that stated I needed to contact in writing via the Etsy website. So freaking frustrating. I doubt they even have a call center anymore.
I hope you get some resolution, keep us updated. This is just nonsense.
Well, after all of that, Support can't recreate this error. But I will give the support rep credit, she explained what she did and even sent me screen shots. And I know if she can't recreate it, there's not much to be done. If you see it, please report it. Otherwise, I think it just is what it is. My customer saw it and I saw it, which means it is out there. But if she can't see it, hopefully most people won't.
Also, FWIW, I just added 89 items from your site into the cart and had no issues.
Did she ask which browser you were using or which browser was she using? It might be a Flash issue as most browsers don't support Flash sites now unless you authorize the site to do so. I use Safari, I've allowed Etsy to use the Flash plug-in and was able to add 80 products with no issue. I wonder if that's what is causing your issue as well. You can usually change permissions in your browsers Preferences folder, under plug-ins.
Safari: Preferences>Websites>(bottom far left column)Adobe Flash
She said she tried a few browsers, and so did I. So I don't think it's a browser issue. But you're right, it could be a setting. But if I have that setting, and my customer had that setting, then how many people have that setting?
Did you just add 80 products, or did you follow through as if you were checking out? I could get to the payment method screen, and then the error happened when I tried to proceed from there.
But I appreciate you trying to recreate it, too.
@funkydreamsmosaics I made it through all the way to the payment page, and the shipping information page, all the way to the confirmation before purchase. Hopefully they fixed whatever glitch was causing this issue.