Virtual Category Root Subtree doesn't apply rules to filtered category

[rhoerr]

Preconditions

Magento Version : Magento OS 2.4.6-p4 (latest)
ElasticSuite Version : 2.11.5.1 (latest)
Environment : Dev and production
Third party modules : N/A -- can reproduce the issue with Magento/blank theme and only Smile_Elasticsuite modules enabled

Steps to reproduce

1. Create a virtual category with one or more Virtual Rule conditions (like 'is discounted')
2. Select a Virtual Category Root
3. Set "Generate Virtual Category Root Subtree" to Yes
4. Open the virtual category on the frontend
5. See that the category filter product counts show a limited number of products in each category
6. Apply a category filter
7. See that the actual product count on the filtered product list is higher

Expected result

1. The virtual category with a category filter applied should also apply the virtual rules (like 'is discounted').

Actual result

1. The filtered virtual category shows all products from the selected category, without virtual rules applied.

Before filter is applied: 'Gas Engines' shows 1 matching product

After category filter is applied: The product list shows 21 matches (all products in Gas Engines), which is more than the virtual category contained to begin with.

Applying the 'category' filter appears to be nullifying the virtual rules. This doesn't happen with other filters -- attribute filters seem to work fine. Only the category filter is affected.

[romainruaud]

@vahonc can you check this ?

You should be able to get the root category applied here :

https://github.com/Smile-SA/elasticsuite/blob/2.11.x/src/module-elasticsuite-virtual-category/Model/Layer/Filter/Category.php#L180

If $appliedRootCategory is empty, it might have been initialized unproperly here :

https://github.com/Smile-SA/elasticsuite/blob/2.11.x/src/module-elasticsuite-virtual-category/Controller/Router.php#L107

[rhoerr]

Hi! Checking in on this. Any progress @vahonc ?

[romainruaud]

@vahonc what's the state of this issue ?

[rhoerr]

Hi, checking in, any status or findings on this? This bug is still in play for us.

Thanks