Muut Archive Legend

Recent posts

• Render Variables in Frontmatter Header · 10 years ago

  @bleutzinn: Thx, tried it, but still it won't show up...

• Render Variables in Frontmatter Header · 10 years ago

  You could try replacing the single quotes around title-image by double quotes so page.media['title_image'] becomes page.media["title_image"], in order not to confuse the parser.

• Render Variables in Frontmatter Header · 10 years ago

  I tried metadata: 'og:image' '{{ page.media['title_image'].url }}' but it wouldn't show up... If i use page.header.title instead, the meta data is showing up. Does it mean I can't access the page.

• Render Variables in Frontmatter Header · 10 years ago

  Edit: Obviously it is: frontmatter: process_twig: true ---

• Render Variables in Frontmatter Header · 10 years ago

  Thanks a lot for all the help! I managed to get it working using the tip from rhukster: frontmatter: process_twig: false ignore_fields: ['form','forms'] However, its important to note: When

• Render Variables in Frontmatter Header · 10 years ago

  Try changing this in your user/config/system.yaml: https://github.com/getgrav/grav/blob/develop/system/config/system.yaml#L64 It's an option that lets you process Twig in frontmatter :)

• Render Variables in Frontmatter Header · 10 years ago

  There's no indication in the documentation that this is possible. Your twig files already have access to {{site.config.*}}, though. Plugins like Import and Header by Taxonomy can inject page headers.

• Render Variables in Frontmatter Header · 10 years ago

  Having exactly the same issue... when you use open graph I would like to access the images.

• Render Variables in Frontmatter Header · 10 years ago

  Is it possible to have Twig render a variable, which is defined in user/config, inside a .md header? For example: content: items: '@taxonomy': category: 'foobar' exhibition: {{ site

• Issues with "og:description" tag on pages that don't have summaries? · 10 years ago

  You could "make" a summary by taking the content and cutting it down to a suitable length, but you could also just revert to the site description in lieu of a page's summary, like this: {% if page.sum