Skip to content
● Critical PHP security fixes are out: update PHP on your Grav sites. What to do →

pamtbaau Legend

Grav Forum Moderators

@pamtbaau · Joined 8 years ago · 3203 posts · 17 topics · 1020 reputation

Badges

Grav Core Team ModSquad Team Member ✏️ First Post 💬 Conversation Starter ❤️ Well Liked

Recent posts

  • Error on first run After Composer install. Undefined Constant · 3 years ago

    @mikejones3, The issue also suggests... it seems that clearing OPcache by restarting PHP-FPM, which I randomly thought of, actually did the job.

  • Workaround for using 'validate.required' on form file fields · 3 years ago

    @bleutzinn: I guess the secret in why the Twig way didn’t work for me and did for you is {% block input_attributes %} The problem is that variables in Twig are only accessible in their scope. Tags li

  • Problem with inherited theme · 3 years ago

    @bjaz, Since your issue has been solved, it might be a kind gesture to the developer of the plugin to close the issue you created at Github...

  • Blog and translations · 3 years ago

    @KlaasHDec, Have you had a chance to read the docs? Especially about content_fallback in section Language Configuration?

  • Error on first run After Composer install. Undefined Constant · 3 years ago

    @Karmalakas, I assume installing via Composer will not install required plugins. That's an incorrect assumption... After running $ composer create-project getgrav/grav ./site-tmp, Grav is installed

  • Use Markdown in twig template · 3 years ago

    @Jerry, Try filter |markdown instead of |markdown_to_html See https://learn.getgrav.org/17/themes/twig-tags-filters-functions/filters#markdown Note: I'm not a fan of using Twig containing Markdown. I

  • Workaround for using 'validate.required' on form file fields · 3 years ago

    @bleutzinn, Three alternatives: 1. Using Twig When searching for datasets in the template folder of the Form plugin, I find a reference inside user/plugins/form/templates/forms/default/field.html.twig

  • Problem with inherited theme · 3 years ago

    @bjaz, I'm sorry to say, but this is not a problem of the Social Media Links plugin. It's a PEBKAC problem. In the issue you've created on Github, you're showing the following code snippet: {% if con

  • How to remove menu-items from Woo skeleton · 3 years ago

    @pmflav, That's because this theme uses menu-items which are hardcoded in /user/config/site.yaml menu: - text: Features link: "#features" - text: Pricing link: "#pricing" - text: Screens

  • Problem with inherited theme · 3 years ago

    @bjaz, Please help the community help you by providing a succinct question containing only relevant information. I copied a vanilla sidebar.html.twig to my theme There is no such thing as a vanilla