In order to be clearer, is better if we give the possibility to select just the fields that we support as a Facet.
And create a message under the filter selector to inform the user of this decision.

CommentFileSizeAuthor
#4 filter-fields-supported-2809185-1.patch2.07 KBdimr
Screenshot from 2016-09-30 12-54-57.png21.22 KBdimr

Comments

dimr created an issue. See original summary.

dimr’s picture

dimr commented

I am working on this issue in the DublinCon Spring

simon georges’s picture

simon georges commented

Did you manage to make it work. What fields aren't supported as facets?

dimr’s picture

dimr commented
StatusFileSize
new filter-fields-supported-2809185-1.patch2.07 KB

Confirmed support of facets with type boolean, date, decimal, integer and string.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented
Status: Active » Needs review

Let's see what the bots think of this, but from a quick look - those changes look good.

  • borisson_ committed ca8ceb7 on 8.x-1.x authored by dimr 
    Issue #2809185 by dimr: Filter fields that we support creating facets
borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented
Status: Needs review » Fixed

With search_api_defaults installed, this removes the ability to create a facet on "rendered item" and that sounds like a good thing! Committed and pushed, thanks for picking this up during the sprints and sticking with it!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.