windmeile

thanks again for your reply. I checked and all files in the klarna plugin folder have been updated with the latest plugin update. Also all php caches have been cleared. The content of the file class-kp-requests.php is identical to the content of the file in the link you have provided.

Any other idea?

I have to mention, this error is not appearing in my php error log. it is appearing using a wp cli command namely wp varnish purge. I use this from time to time to clear my server side varnish cache. It then triggers this error, and when I deactivate the klarna plugin, its gone and I can successfully clear my cache.

Hi,

thanks for getting back. I double checked and we have the most recent version 3.8.3 and woocommerce 9.3.3. The error still appears.

Thanks for diving in.

the problem is solved after doing some maintenance (plugin/wordpress updates)

how can this be explained then?

wait, the problem is, that the klarna plugin is apparently not able to recognize that an order is being set to status ?completed“ (via api) and – even worse – that an order is already captured (or shown as captured and it is not). That is a huge flaw.

I don’t need to ask them because you gave the answer yourself: a status change via api skips hooks and filters and apparently your plugin relies on them. I did all the debugging work and the bug should be clear, now I just need you to fix it.

I am not a developer but it should be fairly easy to fix it….

sure, under Woocommerce > Settings > Advanced > REST API. There we have created a key, which we set in the settings of the ERP.

I cannot say for sure what call they are using to change the status because its closed source but I guess it will be standard call from the woo developer documentation.

Let me know if you need more details. Happy to help.

Thank you very much for getting back, Anton. I was able to make it work by activating a setting in my theme:

Dynamic Srcset: <small>The Dynamic Srcset system creates a list of different responsive images so that browser can pick the most appropriate version based on the actual device’s resolution.</small>

Thanks for giving me the hint, but it resulted in many admin-ajax.php calls that made my site slow. So I guess its just not compatible with my theme/site or I am just not able to make it work properly. However, I think its a great plugin idea and as mentioned everything else worked flawlessly.

Last question: I am not able to delete the plugin after deactivation, any idea why? Its just being stuck in “Deleting…” mode on plugin page. Thanks.

it‘s a bit disappointing that no one ever got back to me even after providing thorough debugging information. however, I got it solved by hiring a developer that fixed it for me. Hope this helps anyone having the same problem or ideally gets implemented in the next version update.

So basically the counter function that is being triggered with every add or remove from wishlist actiob checks if the counter value is in the object cache, and if it is, take it from there and if its not recalculate it. To me that makes absolutely no sense, if you add a product you should have the cached value plus one or if you remove it minus one. We fixed it by just always recalculating this value.

Here is how to implement this workaround:

Open yith-woocommerce-wishlist/includes/class-yith-wcwl.php

Change this code:

$count = wp_cache_get( 'wishlist-count-' . $wishlist->get_token(), 'wishlists' );

into

$count = $wishlist->count_items();
 wp_cache_set( 'wishlist-count-' . $wishlist->get_token(), $count, 'wishlists' );

do that for logged in user function and non-logged in user function. thats it.

maybe a developer can comment as to why the code was written that way.

UPDATE: I did some further debugging and I found, the problem is not related to the frontend, meaning it is updating the counter just fine, but with the wrong counter.

I checked the KEYS stored in my redis object cache and found the following YITH wishlist related KEYS:

1) “wishlists:wishlist-token-“
2) “wishlists:wishlist-default-912”
3) “wishlist-items:item-307”
4) “wishlists:wishlist-user-total-count-912”
5) “wishlist-items:item-304”
6) “wishlists:wishlist-default-44486be4f1fa529b0f30f088b5b0f003”
7) “wishlists:wishlist-user-total-count-44486be4f1fa529b0f30f088b5b0f003”
8) “wishlists:wishlist-id-0”
9) “wishlist-items:item-306”
10) “wishlists:wc_wishlists_cache_prefix”
11) “wishlists:wishlist-id-158”
12) “wishlists:wishlist-items-158”
13) “wishlist-items:item-305”

If I check the value of the wishlists:wishlist-user-total-count* KEY I get:

127.0.0.1:6379> GET wishlists:wishlist-user-total-count-44486be4f1fa529b0f30f088b5b0f003
“1”

It always gives back “1” no matter how many items are in wishlist.

TLDR, the problem lays in populating the object cache, it seems it gets stored in object cache with the first item being added to wishlist and after that never again.

Would ne great if a developer could look into this. Thanks.

ok I hope they will not send me over here.

Hi Daan,

sorry for late reply. I was not able to reproduce it until now – which is good news. Maybe it was a caching issue, I have a pretty strong caching on server side.

I was able to reproduce it once, giving me the following error in the console, but unfortunately I cannot tell which setting I tried out when it happend, so you might as well ignore it. Thanks alot, my customers are all happy again ??

Hi Daan,

really happy that this is resolved now. Just wanted to let you know, as soon as I use the preload option of a font its back to the old light font style. This is just meant as an information for you, I can happily live without that preload feature. ??

Best regards, Michael

it seems to be working :-))))) thank you sooo much man, you’re the best.

Had to clear the cache in the OMGF plugin though.

Now when I remove the code snippet from function.php it is still showing the fonts correctly? is it expected behaviour? or was something misconfigured that got fixed through the plugins cache clearing….

Thanks again, so happy this is fixed now. ??

Hi Daan,

is this what you need?

User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0

Thanks let’s hope that will do the trick ??

maybe he had a bad day ??

thanks so much for looking into it, I really appreciate it. ?? So I did as per your request and it’s woff2. See screenshot.