Epicode

We had exactly the same problem. If Redis cache is activated, the number will not be displayed properly. We didn’t want to edit the plugin as suggested by Windmeile to ensure our changes would not be overwritten by a plugin update? Here is the fix we used, hopefully this will help more people for fixing this problem:

add_action( 'wp_ajax_yith_wcwl_update_wishlist_count', 'epicode_overwrite_yith_wcwl_ajax_update_count', 99 );
add_action( 'wp_ajax_nopriv_yith_wcwl_update_wishlist_count', 'epicode_overwrite_yith_wcwl_ajax_update_count', 99 );

function epicode_overwrite_yith_wcwl_ajax_update_count() {

  // Build args array
  $args = array(
    'wishlist_id' => 'all',
    'user_id'     => is_user_logged_in() ? get_current_user_id() : YITH_WCWL_Session()->get_session_id()
  );

  // Get wishlist count from function instead of cache
  wp_send_json( array(
    'count' => YITH_WCWL_Wishlist_Factory::get_wishlist_items_count( $args )
  ) );
}

@shindhl Thanks this is very helpful, we’re gonna use the filter to set the pricing.
Thanks for resolving our issue.

The Netherlands

Hi @shadim,

Thanks for the fast reply, the “Free Shipping” shipping class is applied to some products in Woocommmerce, these products should receive no shipping cost for the DHL Shipping method.

However I see no option in the DHL plugin to set the shipping price of the “ServicePoint delivery” to € 0,- based on the shipping class.
I expected there to be a rule that can be applied to the Shipping Class just like there is with Cart total & Weight.

Currently we have the following setup:

• Shipping price = € 1,95, if Cart total exceeds € 25,- change shipping price to 0,-

But we need a additional rule to be applied:

• Shipping price = € 1,95, if product has Shipping class “Free Shipping” change shipping price to 0,-

Hope this makes sense, if you have any follow-up questions please let me know.

• This reply was modified 3 years ago by Epicode.
• This reply was modified 3 years ago by Epicode. Reason: format issue

Same problem here, however the code suggested above is not the appropriate fix.
The issue is really in the function get_order_ids() which uses the Woo function wc_get_order_statuses(); to query the active orders by known statuses.

The post_status “Trash” is not returned by wc_get_order_statuses();.

So the fix would be to simply add this minor change in the get_order_ids() function.

$default_order_statuses = array_keys( (array) wc_get_order_statuses() );
$default_order_statuses[] = 'trash';

This way the returned ID’s used by the plugin also takes the trashed orders into account.
Please fix this in the next release of the plugin!

@rvandew Top bedankt, wij hebben inmiddels ook probleemloos de overstap gemaakt naar de api-koppeling.

Wij ervaren dezelfde problemen, aangezien er fouten terug komen hebben we de Woocommerce update nog niet doorgevoerd bij onze klant dit willen we graag wel doen echter weten we niet goed of de e-Boekhouden plugin dan nog functioneerd zoals verwacht.

Kan iemand bevestigen of alles nog werkt zoals verwacht na het updaten van Woocommerce en vervolgens de e-Boekhouden plugin te verwijderen en te herinstalleren ?