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

  • Directory relative links between pages · 11 years ago

    https://github.com/getgrav/grav/commit/565152dee03b714a4b601cb6331d6926f664362e <- this one should do it.

  • Directory relative links between pages · 11 years ago

    Scratch that last commit, had to roll that back as it broke image links. I'll look to find a way to add active language prefix for markdown links only.

  • Directory relative links between pages · 11 years ago

    BTW I did commit a fix to add the active language to prefix the links as I missed this when doing the multilang implementation. https://github.com/getgrav/grav/commit/70831690a5009b483f2edb3230e09f6d

  • Directory relative links between pages · 11 years ago

    Well in my test they are all working fine. Obviously the example below is based on my testing site, but you can get an idea of the various link types: ### Directory relative * just down [01.item2-1]

  • Directory relative links between pages · 11 years ago

    Yes, but we have different needs for inter-page linking and were hoping the methods described in http://learn.getgrav.org/content/linking would work. 1) Using the proposed slug method would still not

  • Directory relative links between pages · 11 years ago

    First, it's much better not to use the actual folder directories. This is because if you change the directory or change the ordering, it will break your links. Better to use the route. So, for your

  • Directory relative links between pages · 11 years ago

    I am trying to generate links between pages using the method explained in http://learn.getgrav.org/content/linking None of the methods (directory relative nor absolute) I tried resolve the link correc

  • Include js/css only for one page · 11 years ago

    Thanks for your answers! The third way is quite similar to the one I tried to describe in my question.

  • Include js/css only for one page · 11 years ago

    that's the 3rd way, but its more maintenance than the first two. really performance differences will be quite minimal between them all.

  • Include js/css only for one page · 11 years ago

    For performance I think you can duplicate or create another template and for this page use the new template. Into the template you add the twig function for add the js/css.