Karmalakas Veteran

Recent posts

• Crikey error instead of error page · 5 years ago

  @Netzhexe: this is supposedly line 287 in user/plugins/flex-objects/flex-objects.php : $parts = explode('/', $route->getRoute()); But when I check out that file, that line looks like this: $page =

• Using loop for with slice to show elements in two columns · 5 years ago

  Ah, right :) It's Twig and strict comparison here would be {% if not loop.last and loop.index is same as((loop.length + 1) // 2) %} But yes, == in this case will work perfectly fine

• Using loop for with slice to show elements in two columns · 5 years ago

  <ul class = "divided icons col-6 col-12-mobile"> {% for item in theme_config.social%} <li class = "icon brands fa - {{item.icon}}"> <a href="[[ item.url }-lex.europa.eu">

• Two additional <p> tags generated in content · 5 years ago

  I don't think this will work on page.content, because it's always parsed. Even if it worked, then you wouldn't get paragraphs separated. I see only two options here: wrap in &lt;div/&gt; use custom i

• Two additional <p> tags generated in content · 5 years ago

  Can't you just use like this? &lt;div class="custom"&gt; {{ page.content|raw }} &lt;/div&gt;

• Two additional <p> tags generated in content · 5 years ago

  It is. That's why I'm suggesting custom input

• Calendar shows wrong times for recurring entry · 5 years ago

  Did not dig into the issue, but as a note, UTC, GMT and GMT+0 are different things and interpreted differently by PHP. Just a week ago we were solving an issue where data was mismatched and it turned

• Two additional <p> tags generated in content · 5 years ago

  Not that I know of. Also can't find anything quickly by looking at the code. What's your use case, if I might ask? I don't see any benefit of not wrapping it. Maybe you should consider using other (cu

• Two additional <p> tags generated in content · 5 years ago

  Could you dump your content|raw and see what's there? I believe Grav wraps every paragraph into &lt;p/&gt; - and that would make sense, because otherwise you wouldn't have a separation between your co

• Two additional <p> tags generated in content · 5 years ago

  I assume, because your page.content already has &lt;p&gt;Content&lt;/p&gt; If you were to look at the proper source instead of inspector, I'd bet you will see something like &lt;p&gt;&lt;p&gt;Content&