cancel
Showing results for 
Search instead for 
Did you mean: 

In Layered Navigation not show attributes with "Filterable (with Results)"

0 Kudos

In Layered Navigation not show attributes with "Filterable (with Results)"

Feature request from redicer, posted on GitHub Jan 29, 2016

Preconditions

  1. I am installing Magento 2.0.2. No customization. No sampledata. Apache 2.4, PHP 5.6.

Steps to reproduce

  1. Create test category. Is Anchor - Yes.
  2. Create test product.
  3. I look my test category on the storefront. Layered navigation filter with 'Price' is not displayed.
  4. Returns to the Admin page, and add to the my product test attribute 'Color'. (Filterable (with results)).
  5. Attribute 'Color' is also not displayed in the filter.
  6. Returns to the Admin page, and change attribute 'Color'. from 'Filterable (with results)' to 'Filterable (no results)'.

Expected result

Price filter is visible.

Actual result

Attribute 'Сolor' display begins. But the "Price" is still not visible.

In /var/log/system.log

[2016-01-29 23:21:49] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_28f8f27b8478aea82e0ee080b652907b7: Please correct the XML data and try again. [] [] [2016-01-29 23:21:49] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_2a7ccd8094436548b564a588f6303121c: Please correct the XML data and try again. [] [] [2016-01-29 23:21:49] main.CRITICAL: Broken reference: the 'store.settings.currency' tries to reorder itself towards 'store_language', but their parents are different: 'store.settings' and 'header.panel' respectively. [] [] [2016-01-29 23:21:49] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_26f1b068ec7ccf4878f9284dd1137afd1: Please correct the XML data and try again. [] [] [2016-01-29 23:21:54] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_2d41d8cd98f00b204e9800998ecf8427e: Please correct the XML data and try again. [] [] [2016-01-29 23:23:04] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_3942059a62c87af8724fe1ef3f757dc31: Please correct the XML data and try again. [] [] [2016-01-29 23:23:04] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 23:23:04] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 23:23:04] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] [] [2016-01-29 23:23:10] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_3d377266e3d6552ca5fe63f5fe36483b7: Please correct the XML data and try again. [] [] [2016-01-29 23:23:10] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_3793edbdc1c00dd1c3aa9e1b3dc856b39: Please correct the XML data and try again. [] [] [2016-01-29 23:23:11] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 23:23:11] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 23:23:11] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []

Do you have any ideas about this?

31 Comments
Not applicable
Status changed to: Investigating
 
Not applicable

Comment from kandy, posted on GitHub Feb 01, 2016

@redicer Thanks for reporting, definitely sounds like a bug. We have created ticket MAGETWO-48639 to investigate.

Not applicable

Comment from davidnguyen2205, posted on GitHub May 20, 2016

Is it fixed? I got the same problem...

Not applicable

Comment from blizam, posted on GitHub Jun 13, 2016

Is your test category a sub-category of another non-root category? Does your test category have any of its own sub-categories?

https://github.com/magento/magento2/issues/5009

Not applicable

Comment from bartek9007, posted on GitHub Jul 08, 2016

Same here, attribute shows when attribute is set Filterable (no results) but not when with results. The problem apperas both in non-root categories and their subcategories.

Not applicable

Comment from blizam, posted on GitHub Jul 08, 2016

seems better/fixed in 2.1.0 -- I haven't tested thoroughly but Layered Navigation seems much better in 2.1.0

Not applicable

Comment from bartek9007, posted on GitHub Jul 11, 2016

No it is not - as I pointed out higher. Attribute assigned Filterable (with results) shows randomly or don't appear at all. It doesn't happen when Filterable (no results) is set, but it doesn't work when I set it programatically, only works set from adminhtml.

Not applicable

Comment from alphatwenty, posted on GitHub Sep 07, 2016

I'm having the same issue using the color attribute on 2.1.0.

Not applicable

Comment from pyyick, posted on GitHub Oct 30, 2016

@alphatwenty Same on 2.0.10

Not applicable

Comment from Juigeli, posted on GitHub Nov 13, 2016

Same here on Magento 2.1.0 CE. Attributes set to Filterable (with results) or Filterable (no results) shows randomly in different categories or don't appear at all. I already tried flush cache, delete and re-compile static files and re-import products. I can give access to our development server if that helps to solve this problem.