mgatten

That looks promising. Thanks for posting it. If I run into this problem again I’ll try it. (We moved forward without variations on that cart and so aren’t experiencing the problem due to that workaround.)

Does this plugin still work with WP 4.5?

I used it a number of times a few months ago without any problems. I don’t know what version we a were on at that time. But now I’m on 4.5 and I get the error described in this post. I have reduced Max Page Size all the way down to the minimum, and I increased the memory limit as per your suggestion in your reply above, but I’m still getting the same error.

Any ideas?
Marshall

Thanks for the pointer but, sadly, I’d already found and tried that. My skus really didn’t exist already, anywhere in the database. (I even tried using a tool that let me search through every field of every table in the entire database for the skus, just in case some auxiliary table with unknown field names was somehow getting involved. The skus didn’t exist anywhere.

No. We have been forced to abandon the whole variants feature. Which is really unfortunate. I would very much like to find a fix. (I take it you’re experiencing the same?)

Thank you for the suggestions. Sadly, none of them apply. My trash is empty, the items were entered without duplicating old ones, and we aren’t caching.

I’ve found a workaround, though. This particular site is being used as a backend translator – I’m importing orders from another source and then exporting them to yet another source. Because both sources can talk to WooCommerce, but they can’t talk to each other. As a result, I don’t care what the store looks like. So I created every variant as a simply product with no attributes and no variants. And now everything works.

It doesn’t solve the problem for the next person to find this thread via Google, but I’m happy to put it behind me for now.

Thanks again for taking the time to make some suggestions.

I’m having the same problem. I’ve checked post_meta and the sku does not exist there at all. (748252302748) I’ve done a database optimization, but wasn’t as lucky – it didn’t fix it.

We have 183 variants total in 19 products, every variant has a unique 12 digit sku (our UPC barcode number). But there are about twenty of them that give this error, and I can’t figure out why.

Has anybody else seen this, where it wasn’t fixed with a db optimization?

I should mention that we have a second WordPress installation on the same server, in a different directory with a different database table prefix, also running WC. All the skus are fine in that one, and the 160 or so skus that are working fine on THIS install also exist in that install. So I don’t think it’s relevant that it’s there, but thought I should mention it.

Thank you. They updated it, which is good regardless, but the problem continued.

Eventually I tracked it down to a problem with the WP Fastest Cache plugin. I created an alias in my .bash-profile file of “wp=wp –skip-plugin wp-fastest-cache”.

And now it works. Thanks for your help – the upgrade was important regardless of if it fixed this particular issue.

Marshall

(Actually, I found a workaround that will allow me to keep using WPFC. I added a line to my .bash-profile:
wp –skip-plugin=wp_fastest_cache

It still reports the undefined indices in wpFastestCache.php for some reason, but then works and doesn’t output the homepage sourcecode.

Marshall

Got it fixed!

Looking in the Widget Admin area, I noticed it was listed in both the WooCommerce Sidebar and the Main Sidebar. But no changes I made to the one in Main Sidebar seemed to have any effect. So I figured it must be conflicting. So I deleted it from the Main Sidebar area. That when something surprising happened: It popped back up in the Main Sidebar area of the Widget Admin page after being deleted, but this time with a blank Title field. I filled in the Title field and voila!

It had apparently somehow gotten put on twice but was only showing once on the page. To make it more confusing, the Admin area also only showed one – but it showed the OTHER one!

Sheesh. I’m goin’ to bed. ??

Thank you SO MUCH for your help. I owe you a cookie and a beer.

Marshall

If you look at any product page, though, the title appears. So it’s not removed altogether – it’s just not generating on non-Woo pages. I’ve looked in the admin area for any display options for the title, and none are apparent.

We’re using “WP Fastest Cache” which minimizes css and js and creates caches of just about everything. So the files shown in the inspector aren’t the actual sources of the css. What I’ve been doing is deleting the cache and then immediately grepping for class names before anybody has a chance to load a page and regenerate the caches.

Thank you! You’re a rockstar. In addition to the obviously useful part of your answer, it also made me realize some troubleshooting techniques that should have been obvious to me that I was totally overlooking. You helped solve this problem and surely lots of future ones with that.

One outstanding problem with the same widget, though, is that while it now displays perfectly on all product pages and some other pages, the title doesn’t display on the home page or a few other pages like the store locator page. (I’m guessing that it’s displaying within pages generated by WooCommerce but not on pages that are not part of WooCommerce.)

On the pages where it displays, its class is “widget-title”. I was hoping to find someplace in the css showing a “display: none” for that class, but it doesn’t appear to exist anywhere like that.

Any ideas?

My apologies for the duplicate post. I’m clearly a newb on these forums. I thought I’d found a subforum dedicated to WooCommerce and so closed out my other post and reposted in the correct place, but apparently it’s just a categorization thing. I did read the rules, and I really am not just trying to “bump” this. Just trying to play nice.

I just discovered that WooCommerce has its own subforum. Sorry for putting this here in the wrong place. I’d move it, but don’t see a way to do that. I’d delete, but don’t see a way to do that either. So I’ll resolve it and repost it there.

Wow! That’s awesome! I’ll really look forward to it.

Thanks!

Thanks. I hope you’re right because that’ll make it disappear as soon as I get our theme created.