Category Layered Filter Issue

[kost08]

When you search for something, using sample data for example, a 'bag' no category filters are displayed. That happens because category filters are only rendered if Category in $categories has no children categories. In Magento\CatalogSearch\Model\Layer\Filter\Category in ::_getItemsData() $category is Default Category and $categories is a collection of it's direct children categories.

But $optionsFacetedData is an array of Categories which are children of the $categories

When you check

...
foreach ($categories as $category) {
    if ($category->getIsActive()
        -> && isset($optionsFacetedData[$category->getId()]) <-
        && $this->isOptionReducesResults($optionsFacetedData[$category->getId()]['count'], $collectionSize)
) {
...

There is no match and filters aren't rendered.

[magebay99]

why not using isotope filtering?

[davidalger]

The GitHub issue tracker is intended for technical issues only. Please refer to the Community Forums or Magento Stack Exchange site for technical questions. In your case, the programming questions forum is likely the most appropriate. Feel free to reopen this issue if you think you have encountered a bug in Magento 2.

[psol7]

I think it is a technical issue (bug) with M2.
Categories in layered are only rendered if Category in has no children.
Layered category filter only shows non-anchored sub-categories, all is_anchor ones are not displayed.
Same with search results layered category.
This happen with the demo sample data as well as our migrated store from 1.9.01 (2000 categories in 4 levels). in our 1.9.0.1 all categories and sub-categories are displayed fine in layered left nav.

[RakeshJesadiya]

I have same kind of issue available for category with subcategory have product then its not display inside layered navigation.

I have checked category with subcategory all have is_anchor equal yes.

Any update for this issue?

[ktruehl]

Here's a patch that fixes the issue:

diff --git a/www/vendor/magento/module-catalog-search/Model/Adapter/Mysql/Plugin/Aggregation/Category/DataProvider.php b/www/vendor/magento/module-catalog-search/Model/Adapter/Mysql/Plugin/Aggregation/Category/DataProvider.php
index f54a60f..678226b 100644
--- a/www/vendor/magento/module-catalog-search/Model/Adapter/Mysql/Plugin/Aggregation/Category/DataProvider.php
+++ b/www/vendor/magento/module-catalog-search/Model/Adapter/Mysql/Plugin/Aggregation/Category/DataProvider.php
@@ -74,8 +74,8 @@ class DataProvider
             $derivedTable->from(
                 ['main_table' => $this->resource->getTableName('catalog_category_product_index')],
                 [
-                    'entity_id' => 'product_id',
                     'value' => 'category_id',
+                    'entity_id' => 'product_id',
                 ]
             )->where('main_table.store_id = ?', $currentScopeId);
             $derivedTable->joinInner(

The problem is the following. In Magento\CatalogSearch\Model\Adapter\Mysql\Aggregation\DataProvider in the execute-method the fetchAssoc method is used to convert the query result into an associative array. The fetchAssoc method however uses the first column for the keys of the associated array. For all attribute aggregations the first column is always the value column, as it should be. However for the category aggregation the first column for some reason is the entity_id column, which is not unique. The fix consists thus in making the value column the first column to be returned by the select.

[psol7]

Right on ktruehl. Problem fixed. Thks.

[choukalos]

Hi @ktruehl Thanks for the patch! I've created a bug for internal tracking purposes - MAGETWO-52436 .
Closing the other github issue as a dup.

[Krapulat]

Thanks @ktruehl, your fix works perfectly.