Several processors are unsuitable for use on Search API aggregated fields -- see #2895368: 'This field has no datasource' exception needs more detail and #2844895: Transform entity id into label doesn't work with aggregated fields.

In both of those cases (entity label transform, and list item label), the search view crashes when the facet processor tries to run.

The facet form should prevent the processor from being added in the first place.

Comments

joachim created an issue. See original summary.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented

This is a good idea, not sure how we should do this in practice.

We should start by implementing #2851851: Facet source plugins should provide metadata for facet fields, so that we have the data to base this on.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented

We have a similar issue for #2877691: Only display Facet Widget if certain conditions are met?, we should probably implement a similar solution for this as in the other issue.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented
Issue tags: +beta blocker

I think we can solve this in one go, together with #2877691: Only display Facet Widget if certain conditions are met?. See the patch attached there for an implementation that might work.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented
Status: Active » Closed (duplicate)

This was fixed in #2877691: Only display Facet Widget if certain conditions are met?