I'm sorry I can not explain things better, I do not speak English very well.
If you or the people developing Toolset discover something else, you tell me.
Thanks for your help Beda.
That's not necessarily a problem of the language you natively speak.
I am not an English native speaker either, and I know it is difficult AND annoying to report problems (highly complex technical problems) to a Supporter in a relatively anonymous forum, where it seems no one really cares, and usually also is not a English native speaker him/herself.
It is difficult to establish a working communication in such a scenario - and that is not your fault.
You reported correctly a problem that I did not understand.
Now we have spotted the exact issue, I replicated it and put all in track for development work.
Yes, I will let you know here as soon I have valid news in regard to the issue here.
Thanks again for your patience and collaboration.
OK, I have debugged this, and can state it is not a BUG, but a compatibility layer that we can introduce.
I have proposed a solution to the Developers, but off course this needs a review first.
It's a one line change in WooCommerce Views, on line 3866 in Class_WooCommerce_Views.php, change the existing if statement to:
if(('variable' == $this->wc_views_get_product_type( $product ) ) || ('variable-subscription' == $this->wc_views_get_product_type( $product ) )) {
Of courser I cannot suggest to edit the core files of our plugin, but I share this so you see why I say it's not a BUG.
The code does not know if a product is variable, we need to tell this to the code.
We do it for WooCommerce, but WooCommerce Subscriptions adds 2 new Product Types:
subscriptions and variable-subscriptions
Those are not considered in our code.
I tested the solution locally to see that it works fine.
But, I suggest to wait for an official update.
All right. I can wait for an update of WooCommerce Views.
You have to think that I also have to wait for other updates so that the site works correctly.
If I wait for these I can also wait for this.
It's a matter of having patience. 🙁
Thanks for the help Beda.
This is now solved in the stable release.