stevejonk

I managed to fix it! I looked at another post on his forum with a similar question, where the advise was to add the following to my theme:
add_filter( 'yith_wcwl_remove_hidden_products_via_query', '__return_false' );

I am curious though. Why did this work?

I have found something in my log that might help!
But I am afraid a change in the plugin is needed for this:

[09-Oct-2024 13:34:26 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') ORDER BY position ASC, ID DESC' at line 1 for query SELECT i.* FROM gb_yith_wcwl as i INNER JOIN gb_posts as p on i.prod_id = p.ID WHERE wishlist_id = 1 AND p.post_type IN ( 'product', 'product_variation' ) AND p.post_status = 'publish' AND prod_id NOT IN ( ) ORDER BY position ASC, ID DESC made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/gobritain/page.php'), the_content, apply_filters('the_content'), WP_Hook->apply_filters, do_shortcode, preg_replace_callback, do_shortcode_tag, YITH_WCWL_Shortcode::wishlist, YITH_WCWL_Wishlist->count_items, YITH_WCWL_Wishlist->get_items, WC_Data_Store->__call, YITH_WCWL_Wishlist_Data_Store->read_items

Thanks a lot for informing! ??

Can imagine that it would be quite hard to change the entire process. Can also imagine that the variation ID is a less error-prone way to use than the SKU.

Think indeed the best solution is to update the ID! We’ll fix it in that way.

Enjoy your day!

Hi!

Of course. We are using a plugin for SW Retail (created by a company called Mull2Media). It’s a specific plugin for an inventory management application, thus it is not in the App Store.

I looked a bit further into it and it seems like (for variabel products) the plugin works in a way that a variation is deleted and created again, whenever the inventory changes. Which cause the Product ID to change.

Im currently also in touch with the builders of the plugin about adding a SKU per variation, because currently that is not set. I hope that could help in solving the issue.

Maybe to verify already:
Would you plugin work correctly in the situation that the existing variation is removed, but directly after a new one is created with the same SKU?

Terribly sorry, it is fixed now. It was due to another background process which got stuck!

Another piece of information is that the product that is in stock again, does not show in the list of subscribers. It shows empty.
Like so:

• This reply was modified 2 months, 2 weeks ago by stevejonk.

@ckadenge Thank you for your quick response!
Forgive me for my impatience, I got some questions from clients, so I thought I’d ask about the status!
Thanks again ??

Hi @carolm29
Thanks for replying and adding the GH report.
I see that the status in GitHub is merged, but with WooCommerce 9.1.4 I still see this issue?

When do you expect to relese 9.2.0?

Hi @femiyb ,

I have read that error message as well.
The provided information is all there, in all different cases. For some it was an existing customer (with the correct information stored in customer object) and for others it was an anonymous order, with the information filled in properly.

As you can see in the attached log (maybe scroll down a bit in it), no customer information is sent at all. Normally – for other orders – the logs also contain the personal information.

@Middelkoop.cc, nice! Thanks for your reply!

• This reply was modified 10 months ago by stevejonk.

Thank you very much!
This clarified a lot.
What also helped was something I read in another forum post, about the Yoast SEO plugin purging the cache.
See this link:
https://github.com/Yoast/wordpress-seo/issues/20554

Hi Denis,

Thanks! Directly created a ticket.

Hi Juan,

Thanks for your quick reply!
I added it in exactly that way (with another jquery selector, because my element is a little different).

The problem hier is that (when looking at the network tab) the yith_wcwl_update_wishlist_count action responds with a count that is 1 to high, when removing an item. So the actual data seems cached.

@rockfire Thanks a lot for this fast and helpful response!
Will implement this! ??

Hi Juan,

Thanks for your fast response. I added all varieties of the exclusions to my ignored groups and the result is still the same. I get old values back.

Weird thing is, this only happens when removing from the wishlist, when adding all is fine.

For example: I have 2 items in my wishlist. I add another one and it directly changes to 3 items (which is good). Then I delete an item from the wishlist. After that the number is still 3 (which is not good).