From 818b3193ffabec57501e3bdfa997206e3c0671ef Mon Sep 17 00:00:00 2001 From: ArthurHoaro Date: Sat, 13 Jun 2020 11:22:14 +0200 Subject: Explicitly define base and asset path in templates With the new routes, all pages are not all at the same folder level anymore (e.g. /shaare and /shaare/123), so we can't just use './' everywhere. The most consistent way to handle this is to prefix all path with the proper variable, and handle the actual path in controllers. --- tpl/default/includes.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'tpl/default/includes.html') diff --git a/tpl/default/includes.html b/tpl/default/includes.html index 07a487bb..0f6a6628 100644 --- a/tpl/default/includes.html +++ b/tpl/default/includes.html @@ -5,11 +5,11 @@ - - - + + + {if="$formatter==='markdown'"} - + {/if} {loop="$plugins_includes.css_files"} @@ -17,7 +17,7 @@ {if="is_file('data/user.css')"} {/if} - {if="! empty($links) && count($links) === 1"} {$link=reset($links)} -- cgit v1.2.3