Muut Archive Legend

Recent posts

• Twig in user page · 11 years ago

  in the system.yaml it should be: pages: process: twig: true Example in the documentaiton

• Twig in user page · 11 years ago

  Hello, thanks for your answer. I cannot figure out why it doesn't work when I set it in the system.yaml. Yet, I've set it in the page where I need it: title: Access menu: Access image_align: right pro

• Twig in user page · 11 years ago

  if you have it in your system.yaml then it's enabled site-wide. I like to have it off in system.yaml, and just add it in the pages header where I need it. This saves every page from being processed f

• Twig in user page · 11 years ago

  Hi, thanks for the help. So it seems that twig is not running fine on my configuration. In my system.yaml, I have: pages: theme: antimatter markdown_extra: false process: markdown: true

• Twig in user page · 11 years ago

  should be: process: markdown: true twig: true That with the plugin enabled should do it. You can test by putting this in your content: page title: {{ page.title() }} If that displays the titl

• Twig in user page · 11 years ago

  Hello, If I understood correctly, I can use twig in my user pages as long as I declare twig as activated in the system.yaml. theme: antimatter markdown_extra: false process: markdown: true twig: true

• Separate sub navbar · 11 years ago

  Just add some custom header variables in each page mycustom1: foo and then access them in the twig with {{ child.header.mycustom1 }}

• Separate sub navbar · 11 years ago

  Trying to adapt this code to my own site, and your code does work well. However I would like to modify it to include some more detail for each menu item. Is there anywhere I can see what each child co

• Separate sub navbar · 12 years ago

  thanks :D

• Separate sub navbar · 12 years ago

  Maybe your looking for what we would term as a split-menu ? By that I mean that rather than showing the dropdown menus for all pages all the time (like a traditional dropdown menu does), it only shows