MyShaarli/tpl/vintage/page.footer.html
ArthurHoaro 818b3193ff 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.
2020-07-23 21:19:21 +02:00

34 lines
992 B
HTML

<div id="footer">
<strong><a href="https://github.com/shaarli/Shaarli">Shaarli</a></strong>
- The personal, minimalist, super-fast, database free, bookmarking service by the Shaarli community
- <a href="doc/html/index.html" rel="nofollow">Help/documentation</a>
{loop="$plugins_footer.text"}
{$value}
{/loop}
</div>
{loop="$plugins_footer.endofpage"}
{$value}
{/loop}
{if="$newVersion"}
<div id="newversion">
<span id="version_id">&#x25CF;</span> Shaarli {$newVersion} is
<a href="https://github.com/shaarli/Shaarli/releases">available</a>.
</div>
{/if}
{if="$versionError"}
<div id="newversion">
Error: {$versionError}
</div>
{/if}
<script src="{$asset_path}/js/shaarli.min.js#"></script>
{if="$is_logged_in"}
<script>function confirmDeleteLink() { var agree=confirm("Are you sure you want to delete this link ?"); if (agree) return true ; else return false ; }</script>
{/if}
{loop="$plugins_footer.js_files"}
<script src="{$value}#"></script>
{/loop}