Hello,
here’s the scenario: Flex Object Blueprint with a tags selectize field, just like the one in the demo Contacts blueprint. We are in admin of course.
How to use in the selectize field the values from tags stored in other objects (of the same type) in directory? It’s not automatic like in the special taxonomy field (not supported yet). If you know how taxonomy field works, that’s the behaviour i’d love to replicate.
Thanks!
I believe these should explain why there’s no autocomplete
Hello everybody,
I am currently looking into the feasibility of doing a larger project with Grav. One of the stumbling blocks I’ve found so far is that tags do not seem to play as nicely with flex objects as I’m used to with pages.
The idea is to have several hundred (but no more than maybe a thousand) flex entries that feature a name, a location with geo coordinations, and some tags. I guesstimate that over those several hundred entries there may be 30 to 60 tags, possibly even more. I expect…
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!
opened 07:43PM - 08 Mar 21 UTC
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!
Thank you, I am the same phmg701 of GitHub issues… data-options@:
Ah, didn’t even notice nickname
No problem! I just need a lead, something to begin with… Sort of a kick-start
