Skip to content
Grav 2.0 is officially stable. Read the announcement →

Muut Archive Legend

@Muut · Joined 9 years ago · 18337 posts · 3878 topics · 137 reputation

Badges

✏️ First Post 💬 Conversation Starter ❤️ Well Liked

Recent posts

  • Add fields to admin content page · 10 years ago

    Thanks! This works perfectly. Thought override is an defined string for expanding a form with additional fields :|

  • Add fields to admin content page · 10 years ago

    In this example, this blueprint will append a new field to the section 'override', which is on the advanced tabs. However, the field 'override' is not present on the 'content' tab. Here is an example

  • Add fields to admin content page · 10 years ago

    How could I add fields to the content page in the Grav backend. I used the first example blueprint of this official doc https://learn.getgrav.org/forms/blueprints/example-page-blueprint and changed "a

  • Header and footer navigation · 10 years ago

    what you can do is using a page collection (for-loop) to add the items to a header menu and add an additional parameter in the .MD file's header area like for example "nav-text" and use that as the te

  • Header and footer navigation · 10 years ago

    Are there any plugin or extension idea for the realisation of an additional menu tree in Grav?

  • Multiple Collections · 10 years ago

    It works now, thank you

  • Multiple Collections · 10 years ago

    Hi, I would say: {% for child in fruitcollection %} Your fruitcollection is already a page object.

  • Multiple Collections · 10 years ago

    I have problem to access the custom collection which i defined in page header. So i have doubt that does i need to defined it in yaml file. my code to access just like this: {% set fruit_collection =

  • Multiple Collections · 10 years ago

    Hi there, Grave allow Multiple Collections, i wanna define my own collection. I defined it within a page header. does it also need to be defined in yaml file? i have no idea where to define the yaml f

  • Page collections based on page.header components · 10 years ago

    As I haven't used page collections I realise I'm on dangerous ground here but I'm sure there is no need for many Twig templates. By default Grav looks for a Twig template file based on the page file n