Problem/Motivation
Error
The website encountered an unexpected error. Please try again later.
Error: Call to undefined method Drupal\core_views_facets\Plugin\facets\facet_source\¸::getViewsDisplay() in Drupal\facets_summary\Plugin\Block\FacetsSummaryBlock->build() (line 101 of modules/contrib/facets/modules/facets_summary/src/Plugin/Block/FacetsSummaryBlock.php).
Also while editing the facet getting below error.
/admin/config/search/facets/content_state/edit
The website encountered an unexpected error. Please try again later.
Error: Call to undefined method Drupal\core_views_facets\Plugin\facets\facet_source\CoreViewsExposedFilter::getIndex() in Drupal\facets\Plugin\facets\processor\BooleanItemProcessor->supportsFacet() (line 101 of modules/contrib/facets/src/Plugin/facets/processor/BooleanItemProcessor.php).
Steps to reproduce
Tried with the below combinations. Getting the same error for all scenarios
Added One Paragraph filed which contains Taxonomy Reference in the exposed filter.
One Taxonomy reference field in Content type in the exposed filter.
Content Published status in the Exposed filter
Content Types as an Exposed filter
I am getting the same error for all of the scenarios.
Comment | File | Size | Author |
---|---|---|---|
#4 | NastyBooleanItemProcessor-3226284-3.patch | 1.28 KB | hugronaphor |
Screenshot 2021-08-02 at 3.57.26 PM.png | 98.56 KB | kuralarasanm |
Issue fork facets-3226284
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
hugronaphor CreditAttribution: hugronaphor at Acrosto for Cornell University commentedI confirm the error "while editing the facet"
The "facets" module expects a
CoreViewsExposedFilter::getIndex
method triggered viaBooleanItemProcessor::supportsFacet
but it's missing completlyComment #3
dwkitchen CreditAttribution: dwkitchen at Centarro commentedThe issue is with BooleanItemProcessor::supportsFacet()
Processesor should look like this:
Comment #4
hugronaphor CreditAttribution: hugronaphor at Acrosto for Cornell University commentedComment #7
borisson_Thanks for the patch.
PS: It seems you (like many others – it's really easy to misinterpret) are confused by the "Issue tags" field. As the guidelines state, they aren't meant for free text tags related to the issue, but only for specific categorization purposes, usually by module maintainers.
So, if you aren't sure your current usage is correct, please just leave the field empty.
Comment #9
mkindred CreditAttribution: mkindred commentedNastyBooleanItemProcessor-3226284-3.patch fixed the problem I was having, which I mistakenly attributed to Core Views Facets (https://www.drupal.org/project/core_views_facets/issues/3245999#comment-...).