Facet links created perfectly except with a colon rather than

Created on 29 May 2025, about 1 month ago

Problem/Motivation

This miraculous module is producing links with the correct facet keys and the correct entity IDs… but a different format, that does not work with the view set up using Facets 3 and Better Exposed Filters 7.

Entity Reference Facet Link is producing facet links like this:

/projects?f[0]=services:1191

My view produces facet links like this:

/projects?services[0]=1191

(or encoded, like /projects?f%5B0%5D=services%3A1191 versus /projects?services%5B0%5D=1191)

Steps to reproduce

I am using this with Drupal 11 (with the core patch for πŸ› Dependencies from only one instance of a widget are used in display modes Needs work ) and Facets 3.

Configure a couple fields to use Facet Link, watch as the only available facet immediately is the configuration option, save, and be amazed that the facet link looks to be generating perfectly!

Be somewhat disappointed that your view is not actually filtered.

Proposed resolution

Adjust something somewhere somehow for some specific setup?

Remaining tasks

User interface changes

API changes

Data model changes

πŸ’¬ Support request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States mlncn Minneapolis, MN, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mlncn
  • πŸ‡ΊπŸ‡ΈUnited States mlncn Minneapolis, MN, USA

    I think the problem here is that Entity Reference Facet Link is not compatible with Facets 3.0.x and the new recommended way to do Facets filters with Views at all:

    New in Facets 3: For new sites it is recommended to use the "Facets Exposed Filters" submodule for Facets on Views. This module uses native Views filters instead, which has many advantages.
    Click here for documentation on how to use this new workflow.

    What it was picking up is the old-style facets i still had which are not needed nor used with Views now.

    Opened a support/documentation issue in Facets looking for guidance, πŸ’¬ Upgrading Facets ecosystem module to Facets 3 Active

  • πŸ‡ΊπŸ‡ΈUnited States mlncn Minneapolis, MN, USA
  • πŸ‡ΊπŸ‡ΈUnited States dcam

    That's not good. Thank you for reporting it.

    I don't have any projects using Facets 3 yet. I'll have to set something up from scratch.

    I have a bad feeling that this will force a complete rewrite of ERFL.

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    Uh, yeah. This is a problem. Don't expect a quick fix. It's going to require something completely new to be developed. TBH, there's probably an argument that it should be done as a separate module.

    I'm going to update the project page to note that it's incompatible.

  • πŸ‡§πŸ‡ͺBelgium StryKaizer Belgium

    I'm not using this module myself.
    Let me know if this module has any advantages which entity_ref_filtering_link does not have, so I can help out supporting them.
    I will probably contribute them to entity_ref_filtering_link though, as I want people to use modules focusing on the entire views ecosystem, not facets specific.

    Facets used to do too much (widget handling, url handling, summary handling, ajax handling, ....)
    Since 3.x exposed filters, this all moved to views, which has a lot of advantages.
    Everything works for every filter, not just facets filters.
    Ajax works, Site builder ux improved, ...

    This module might become obsolete by that reasoning. (As facets_summary and some others did too).

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    This module might become obsolete by that reasoning.

    I think that's a very real possibility.

Production build 0.71.5 2024