@stantinv sadly your assumption that it is a “parent product (without selected options) into Wishlist from a product listing page” appears to be incorrect.
I’ve tested this, and this is not a YITH issue, nor are these ‘parent products’ that generate that message.
I myself am using WooCommerce Wishlist with single sale items. They have no additional product options, either. Now, there is one element here that nobody else may have noticed: this error message (for me, at least) appears ONLY when I try to add a product to the cart that is already IN the cart. It doesn’t appear at any other time. I select ‘add selected to cart’ for a product that is already in the cart, and that is when this message appears — right under the message telling me that I can’t add another of the same product to cart (which is a message that needs to be there)……
And please note: I’ve been trying to do dumb things to test the site, to see how plugins would react and what error messages they’d throw up. I have done this same test before in previous editions of WooCommerce Wishlist, and that message has never appeared.
Fwiw I’ve used a plugin to find where this code is located, and it’s in your plugin…not in other plugins, and not in WooCommerce. So it’s generated from inside your plugin.
The version of the message I get: Product “Favorites” could not be added to cart because some options are not specified. Please, select some product options before adding the products to your cart.
If anyone else wants to find this string, search from the word “could” and beyond — you can’t copy the words before that because they are going to change based on the thing it is that it is telling the viewer. Strangely it is not saying the EXACT product name — it’s calling my product “Favorites”….which means to me that it’s telling itself that itself cannot add an Favorites list item….again, it’s a bug within the WooCommerce Favorites plugin side. That behaviour of the error message calling my product “Favorites” (and not its single product name) tells me that its conditional logic is screwy. And not due to a plugin conflict.
