Community guidelines
Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.
Nico Petri Member
@npetri · Joined 9 years ago · 65 posts · 14 topics · 12 reputation
Badges
Recent posts
-
Email plugin works on a hard coded form
· 7 years ago
Hello there, does anyone tries to use the email plugin without defining a form in the frontmatter as usal? I mean in my case, i want to use a hard coded form and pass the params to the email plugin. T
-
Umlaute Ü ä in frontmatter
· 8 years ago
The description of ur problem was way too short. It lacks the part that u r in a context of a modular. But yea u found a solutiuon. U can create any variable in frontmatter and use it for ur purpose.
-
Umlaute Ü ä in frontmatter
· 8 years ago
U may look how the theme is initializing the smoothscroll.js. Maybe it already supports the slug: variable of the frontmatter which u can serve a different slug. So try to define a slug. If not u can
-
Page.find fails only on custom route
· 8 years ago
Yes, i just tagged it as solved.
-
Page.find fails only on custom route
· 8 years ago
Hello again, its all related to the option routeable: false. However, in this case page.find() deliver the current page as a fallback. I don't know if this is suppost to be. This option was set in the
-
Page.find fails only on custom route
· 8 years ago
Preliminary result: I checked some options that maybe related to routes. I had disabled the default language in route. So i enabled this option and now the page.find() call works as expected. I will d
-
Page.find fails only on custom route
· 8 years ago
Wow, thank u for ur effort. The code block that doesnt work is inside the footer partial that is used by the base.html.twig. The modular page that is called via / which points to /pages/01.home is ext
-
Page.find fails only on custom route
· 8 years ago
/pages: _footer _poi_nz 01.home .. .. .. 06.blog .. .. error imprint The 01.page is a modular page, the home route is set to this page.
-
Page.find fails only on custom route
· 8 years ago
Thank u for checking on that! Yea the /_footer/links' is within the /usr/page folder. Otherwise it could never be found, but it works when in 'normal' cases. But it behave different if its used in a c
-
Page.find fails only on custom route
· 8 years ago
Hello there, i ve setup a route like /keyword -> /blog/keyword in the site.yaml. If the the page is invoked by this route the following find doesnt work as expected: <div class="links"> {