Good idea, I'm now converting them to relative path names. I'm still having trouble with getting custom templates to work, though; I have a file *analysis/document.html.pm *and I'd like it to be render with a *special-template.html*, which is in the root directory* (*outside of the *anaylsis *folder*). *I can't find any way to do that.
I tried to set the template file using define-metas, but neither of these worked: *special-template.html, /**special-template.html, /full/system/path/to/file/**special-template.html.* Got any more tips? Dne pondělí 21. ledna 2019 17:12:28 UTC+1 Matthew Butterick napsal(a): > > > > On Jan 20, 2019, at 11:33 PM, Evžen Wybitul <wybitu...@gmail.com > <javascript:>> wrote: > > And it works, partially. However, when I call `(next here)` on order to do > page navigation, the value for file1 is `analysis/file2.html`, but I'd need > it to be only `file2.html`. Of course, I could just strip the `[...]/` part > programatically, but that feels really hack-ish. Especially if there's a > better way. > > > In essence, you are tracking absolute path names in the pagetree, but you > want them to behave like relative path names. You can either 1) convert > them to relative path names, or 2) use them as absolute URLs (that is, > prefix them with "/") though that assumes you only need the links to work > when served via HTTP. > -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to pollenpub+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
