How to work with "data-options@:" and Flex Objects blueprint

Karmalakas · May 29, 2021, 1:40pm

I believe these should explain why there’s no autocomplete

category and tags in Flex Objects

opened 08:40PM - 05 Mar 21 UTC

feature flex-objects

Hello, while testing Flex Objects, I noticed some unexpected behaviours. Fir…st, here's relevant parts of my custom Flex Object definition: ``` test_tags: type: selectize size: large label: Test Tags classes: fancy validate: type: commalist categories_and_tags: type: taxonomy label: Category and Tag multiple: true validate: type: array ``` ``` list: title: title fields: test_tags: ``` * test_tags do not have the autocomplete function, otherwise found in `taxonomy` field type. This is very very helpful in creating a catalog or any other type of organized data. * test_tags results in `["Test1","Test2","Test3"]` in list view, typical array/plain text representation. * test_tags cannot be searched when other text fields can. We could expect the field to be searchable, given its plain text representation. * no matter how I try to configure it, in list view, `taxonomy` never displays. However this way we have the autocomplete function. I think I tried many combinations, if not every possible one, so I decided to open this issue. Is there something else I can try? As usual, thank you!

github.com/trilbymedia/grav-plugin-flex-objects

"selectize" field type handling and filtering in list view

opened 07:43PM - 08 Mar 21 UTC

phmg701

Hello, following the issue [here](https://github.com/getgrav/grav/issues/3257),… there seems to be an unexpected behaviour in field representation. Relevant my_object.yaml parts: ``` test_tags: type: selectize size: large label: Test Tags classes: fancy validate: type: commalist test_category: type: selectize size: large label: Test Category classes: fancy validate: type: commalist ``` * added field(s) do not have the autocomplete function, otherwise found, for example, in `taxonomy` field type. This is very very helpful in creating a catalog or any other type of organized data. * added field(s) results in ["Test1","Test2","Test3"] in list view, typical array/plain text representation. * added field(s) cannot be searched while other text fields can. We could expect the field to be searchable, given its plain text representation of the array. Thank you!

Topic		Replies	Views
Tags and flex objects: no auto-complete? how do I best organise the tags? no tag cloud? Plugins admin	4	752	April 19, 2021
Couple of questions - Flex Support first-time	0	495	November 11, 2019
Populate a selectize field with taxonomy options Support form , admin	2	362	November 26, 2023
Using images with Flex-objects Support	4	1073	April 1, 2021
Create a list of tags for images in a blueprint?	0	468	October 24, 2017

How to work with "data-options@:" and Flex Objects blueprint

Related topics