Community guidelines
Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.
Jeff Newcomer
@jhirschberg70 · Joined 8 years ago · 7 posts · 1 topics · 3 reputation
Badges
Recent posts
-
Set default taxonomy field value with blueprints
· 8 years ago
This change seems to be merged into the latest release at the very least. That's how I found it, actually. I was looking through files and found reference to the change. I have tried it with my own
-
Set default taxonomy field value with blueprints
· 8 years ago
Okay, I finally found the answer! It comes from https://github.com/getgrav/grav-plugin-admin/pull/1364: With this patch user can override in blueprint the taxonomy field to add custom taxonomy value
-
Set default taxonomy field value with blueprints
· 8 years ago
I don't think you're going to get the dropdown without using type: taxonomy rather than type: selectize. If there is some way to specify default values for type: taxonomy, then that's the way to go.
-
Set default taxonomy field value with blueprints
· 8 years ago
Strictly speaking, no, it doesn't appear necessary to unset header.taxonomy. However, what you will see is that you will have duplicate Category and Tag fields on your form, with the originals displa
-
Set default taxonomy field value with blueprints
· 8 years ago
I was having the same issue, and after digging around some I found an article on stackoverflow that had the solution. Here's the relevant portion of one of my blueprints. You'll notice that I've sep
-
Content Wrapped in <p> Tags?
· 8 years ago
Well, that was simple enough. I turned off Markdown processing, and I was able to make things work as I wished. Thanks!
-
Content Wrapped in <p> Tags?
· 8 years ago
In a twig file for a modular that I've created, I'm using {{ page.content }} to output the content. The content is being wrapped in paragraph tags. It appears that this is coming from Grav's proces