- Issue created by @dieterholvoet
- 🇩🇪Germany Anybody Porta Westfalica
That would be suuuper awesome! +1 for this suggestion!
- First commit to issue fork.
- Assigned to gxleano
- last update
over 1 year ago 2 pass - Issue was unassigned.
- Status changed to Needs review
over 1 year ago 5:53pm 22 November 2023 - Status changed to Needs work
over 1 year ago 2:10pm 4 December 2023 - 🇧🇪Belgium dieterholvoet Brussels
Doesn't seem to work yet, the autocomplete endpoint returns a HTTP 403 response. Diving into the controller code, I noticed
$selection_settings
is FALSE, causing this code to be triggered:// Disallow access when the selection settings key is not found in the // key/value store. throw new AccessDeniedHttpException();
Something else: it would look better if these widgets would be the same height as other form fields, but that might be a Gin specific issue (not tested using Claro).
- last update
over 1 year ago 2 pass - 🇪🇸Spain gxleano Cáceres
@DieterHolvoet Thanks for the review!
I've added a quick change to fix the issue with the height in the Tagify element.
The rest of the implementation works fine for me.
Claro
Gin Theme
Also works with Olivero.
- Status changed to Needs review
over 1 year ago 7:46pm 4 December 2023 - last update
over 1 year ago 2 pass - 🇧🇪Belgium dieterholvoet Brussels
You're right, it does work for taxonomy autocomplete filters. I forgot only taxonomy autocomplete filters are currently supported by core, I'm using a patch from ✨ Continuation Add Views EntityReference filter to be available for all entity reference fields Active to support other entity types as well. It didn't work in combination with that patch, but I found a fix and pushed it to the fork. One minor issue I noticed: it's not possible anymore to submit the filter form by pressing enter.
- last update
over 1 year ago 2 pass - Status changed to RTBC
over 1 year ago 11:40am 7 December 2023 - Status changed to Fixed
over 1 year ago 11:48am 7 December 2023 - 🇺🇸United States ec-adam
I've recently installed Tagify on both Drupal 11 and its running on the latest version of Drupal CMS (different install). It works great on the admin side except its a little inconsistent for me to be able to have awesome tagify select lists on entities where I can control the form display but not on selects lists like the /admin/content content type filter.
I've been trying to use Tagify with Better Exposed Filters to get Tagify to work on the /admin/content filter (as well as select views filters on the front-end). There is a fatal error when using the BEF Tagify option on filters configured to be select lists. Works just fine on filters set to be autocomplete.
When using Tagify on entity form display select fields there is a specific Tagify Select option to use. Can that option be added to the BEF integration so Tagify can work on views filter select lists?