Problem/Motivation
When using an address field and exposing the "country" element of it via views exposed filter + better exposed filters, "tagify" is offered as a widget, but it does not work.
Steps to reproduce
- Install "address", "better exposed filters" and "tagify".
- Create an address field (type Address) "field_address" on any content type
- Create a view for that content type and select "field_address:country_code" as filter and mark it as exposed
- Use "better exposed filters" and see the settings for that field. Tagify is offered as an option, choose it.
- Save

The filter does NOT use tagify (neither admin theme nor frontend theme).

Proposed resolution
Either don't offer it as option or even better, make it work for that field.
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot 2026-04-28 at 13.21.45.png | 25.79 KB | fjgarlin | |
| Screenshot 2026-04-28 at 13.21.09.png | 17.81 KB | fjgarlin |
Issue fork tagify-3587368
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
fjgarlin commentedI've tried via form alter but that didn't work.
I've also tried via custom JS, and while that rendered the element, it didn't fully connect it to the actual input:
In this case, the tagify field works (though it renders the values instead of the labels) but it does NOT update the underlying field.
Comment #3
fjgarlin commentedThis code made it work (with help from claude), for reference:
I don't think this is a proper patch or fix so I'm not attempting to create an MR for it, just putting here as reference.
Ideally, the hook form alter would have been great, or calling any sort of api function at that level that will do all the wiring.
Comment #6
gxleano commentedComment #7
fjgarlin commentedThe code looks good and covers what was missing (as far as I can see). I tested the MR and it works perfectly, I no longer need to add the above JS code.
Marking this RTBC.
Comment #8
gxleano commentedComment #9
fjgarlin commentedTagify is offered now where it wasn't before but it's NOT offered where it was before.
The "tagify" option does not appear now for normal exposed vocabulary fields set as dropdown.
Comment #10
fjgarlin commentedIt does appear when set as "autocomplete", but not as "dropdown".
However, I am not sure if it's due to this issue or if it's a separate non-related issue. I'll let you debug just in case. I'm happy to create a separate issue if needed.
If this is not brought by this issue, this one can be back to RTBC.
Comment #11
fjgarlin commentedNot related to this.
Comment #12
gxleano commentedThe BEF widget just needed some work.
I will add the next approach:
1. When you are trying to add a filter using an entity reference field and choosing the Selection type "Autocomplete", we will provide a Exposed filter widget called Tagify - This is already working by design.
2. When you are trying to add a filter using an entity reference field and choosing the Selection type "DropDown", we will provide a Exposed filter widget called Tagify Select - This will be added as new feature.
3. For the rest of the filter type that can use a select filter, like Published, Address and other fields, we will add a Exposed filter widget called Tagify Select - This will be added as new feature.