Describe the bug
After introducing following custom customTaxonomy, the TAXONOMY view on the dashboard displays additional, wrong one-char-entries (see screenshot):
I have checked all my posts for invalid Front Matter and tried to put quotes around the SERIES entry, where my default Front Matter doesn't use quotes. I also have tried to configure noPropertyValueQuotes, but this doesn't help either:
I can reproduce the behaviour on 2 Windows 10 machines locally (Front Matter v9.1.5938539-beta BETA) and on gitpod.com within a virtual Linux environment (Front Matter v9.0.0).
**Describe the bug**
After introducing following custom ``customTaxonomy``, the TAXONOMY view on the dashboard displays additional, wrong one-char-entries (see screenshot):
```
"frontMatter.taxonomy.customTaxonomy": [
{
"id": "series",
"options": [
"A New Blog",
"Discoveries",
"Great Finds",
"Golem",
"IndieWeb",
"Lightroom Presets",
"Step By Step",
"SV Wehen Wiesbaden"
]
}
]
...
"frontMatter.taxonomy.contentTypes": [
{
"name": "default",
"pageBundle": false,
"fields": [
...
{
"title": "Series",
"name": "series",
"type": "taxonomy",
"taxonomyId": "series"
},
...
]
]
```

I have checked all my posts for invalid Front Matter and tried to put quotes around the SERIES entry, where my default Front Matter doesn't use quotes. I also have tried to configure ``noPropertyValueQuotes``, but this doesn't help either:
```
"frontMatter.taxonomy.noPropertyValueQuotes": [
"series"
]
```
**To Reproduce**
Steps to reproduce the behavior:
1. Clone https://github.com/kristofzerbe/kiko.io
2. Open dashboard
3. Switch to Taxonomies View
I can reproduce the behaviour on 2 Windows 10 machines locally (Front Matter v9.1.5938539-beta BETA) and on gitpod.com within a virtual Linux environment (Front Matter v9.0.0).
<!-- github-sync-id:1866586907 -->
Thanks @kristofzerbe. This is because the taxonomy fields expect multiple values (or at least one) and you configured it to use it as a string.
The frontMatter.taxonomy.noPropertyValueQuotes setting won't help.
I have added a minor fix to overcome the faulty rendering of the taxonomy view.
Thanks @kristofzerbe. This is because the taxonomy fields expect multiple values (or at least one) and you configured it to use it as a string.
The `frontMatter.taxonomy.noPropertyValueQuotes` setting won't help.
I have added a minor fix to overcome the faulty rendering of the taxonomy view.
<!-- github-comment-id:1693020372 -->
Ah ... because not all of my posts have a SERIES! Thnx for your upcoming fix :)
No, because you use the series field as a string, instead of an array (what FM expects). ☺️
> Ah ... because not all of my posts have a SERIES! Thnx for your upcoming fix :)
No, because you use the `series` field as a string, instead of an array (what FM expects). ☺️
<!-- github-comment-id:1693028809 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
After introducing following custom
customTaxonomy, the TAXONOMY view on the dashboard displays additional, wrong one-char-entries (see screenshot):I have checked all my posts for invalid Front Matter and tried to put quotes around the SERIES entry, where my default Front Matter doesn't use quotes. I also have tried to configure
noPropertyValueQuotes, but this doesn't help either:To Reproduce
Steps to reproduce the behavior:
I can reproduce the behaviour on 2 Windows 10 machines locally (Front Matter v9.1.5938539-beta BETA) and on gitpod.com within a virtual Linux environment (Front Matter v9.0.0).
Thanks @kristofzerbe. This is because the taxonomy fields expect multiple values (or at least one) and you configured it to use it as a string.
The
frontMatter.taxonomy.noPropertyValueQuotessetting won't help.I have added a minor fix to overcome the faulty rendering of the taxonomy view.
Ah ... because not all of my posts have a SERIES! Thnx for your upcoming fix :)
No, because you use the
seriesfield as a string, instead of an array (what FM expects). ☺️