How to use Taxonomies/Terms in Forms

[pathly-dev]

Hey, I want to create a form with a select where the frontend user can choose between options that come from my taxonomy.
I have something similar on the panel, where I used the terms fieldtype, so the panel user can choose a option of the given taxonomy. But it seems like thats not working the same way.
This is what I have so far for my form:

{{ form:story-upload }}
  {{ fields }}
    <div>
      <label>{{ instructions }}</label>
      {{ if type == "terms" }}
        <select>
          {{ taxonomies }}
            <option value="">{{ title }}</option>
          {{ /taxonomies }}
        </select>
      {{ else }}
        <div>{{ field }}</div>
      {{ /if }}
    </div>
  {{ /fields }}
{{ /form:story-upload }}

But no taxonomy options are shown and also the {{ title }} is not the title of the taxonomy but the forms title.

[byron-roots]

You can make the Taxonomy Terms field type available to use by adding \Statamic\Fieldtypes\Terms::makeSelectableInForms(); your AppServiceProvider boot method.

Then you just need to create a view in resources/views/vendor/statamic/forms/fields/term.antlers.html and then you can do something like

<div class="o-form__select">
    <label class="u-sr" for="{{ handle }}">
        {{ display }}
    </label>
    <select id="{{ handle }}" class="c-select c-select--md"  name="{{ handle }}[]" {{ (validate | contains:required) ? 'required="required"' : '' }} {{ multiple ?= "multiple" }}>
        <option value>{{ if instructions }}{{ instructions }}{{ else }}Please select...{{ /if }}</option>
        {{ taxonomy from="{collections|option_list}" }}
            <option value="{{ id }}" {{ if old|in_array:id || old === id }}selected{{ /if }}>{{ title }}</option>
        {{ /taxonomy }}
    </select>
    {{ if error }}
        <span class="c-status c-status--error">
            {{ error }}
        </span>
    {{ /if }}
</div>

I've only done this with collections but that above should work, might need a few tweaks though

[byron-roots]

The options are there to limit what you can do when adding entries. As the form fields are read only it doesn't really matter, unless you want to use the options in the form template. If you already know what terms/taxonomies you want to use on then it's not really necessary on the form terms field.

<select name="handle-of-my-field">
    {{ taxonomy:categories }}
       <option value="{{ id }}" name="{{ slug }}">{{ title }}</option>
    {{ /taxonomy:categories }}
</select>

Hopefully that makes sense

[pathly-dev]

Ok got it, thanks! :)

[pathly-dev]

So actually the type of the fields in the form blueprint could be text even if it's in the frontend actually a select/terms, right? Because in the end the field just gets the value of the selected item. Or should this still be the type that it's supposed to be?

[byron-roots]

It could be a text field, but as you want to save the ID of the term (as this is how it would work in your entries) the terms field will display the actual term in Form submission. If you don't ever need to see the form submissions a text field would be fine.

If you aren't going to look at the form submissions, and are only using the form to send data, then you could probably just create a custom controller and route to handle the form submission and creating the entry

[pathly-dev]

Okay yes makes sense. Thanks for all the answers :)