Skip to content
Grav 2.1 is out: every page speaks Markdown. Read the announcement →

Creating a blueprint for a front-end form

form

Started by Oona O'Neil 9 years ago · 1 replies · 869 views
9 years ago

Does creating a blueprint for a front-end form (made with the Form plugin) differ from creating other blueprints? So far all my blueprints have been working fine, but now need to create two for forms I have on my website and they don't display correctly. Trying to find a reason. May it be due to the file naming?

I have a 'navigation_form.md' in a '_navigation' (modular) folder and 'navigation.yaml' file. And accordingly:
'contact_form.md' in a '_contact' (modular) folder and 'contact.yaml'.

Even before getting to displaying form data, a simple header neither works:

YAML
title: Newsletter
extends@: default

form:
  fields:
    tabs:
      type: tabs
      active: 1

      fields:
        gallery:
          type: tab
          title: Newsletter Fields

          fields:
            header.header:
              type: text
              label: Header
              validate:
                required: true
9 years ago

Indeed it was a matter of renaming the file to 'newsletter_form.yaml'. Should have checked before posting here. Sorry for taking your time, but maybe it will be useful for someone.

👍 2

Suggested topics

Topic Participants Replies Views Activity
General · by jeremycherfas, 1 week ago
4 180 2 days ago
General · by lynbor, 5 days ago
2 119 3 days ago
General · by Old Man Umby, 1 week ago
1 100 1 week ago
General · by Sebastian, 1 week ago
1 124 1 week ago
General · by Andy Miller, 3 weeks ago
0 248 3 weeks ago