The personal, minimalist, super-fast, database free, bookmarking service - community repo
It should read something like this
srvadmin@demo1:~$ sudo ls -l /var/www/links.xinit.se/data/datastore.php
-rw-r--r-- 1 www-data www-data 2379 Apr 11 18:03 /var/www/links.xinit.se/data/datastore.phpwww-data must have rw permissions so if it doesn't: sudo chown www-data /path/to/your/datastore.php; sudo chmod u+rw /path/to/your/datastore.php
hi folks, my docker just auto-updated to 0.12, and now my installation is broken - all links, assets etc. ignore the subdirectory shaarli is installed in
I cant find any release notes or migration guides - does shaarli no longer support installation in a subdirectory (with reverse proxy)?
Hello, I more or less have the same issue. Shaarli v0.11.1 is working just fine on my setup:
- PHP 7.3
- Nginx server as a reverse proxy (listens to ports 80 and 443), forwarding to Apache
- Apache server listen to port 8080 runs PHP with mod_php
- Shaarli installed in
/shaarli/subdirectory
But with v0.12.1 Shaarli behave just like if mod_rewrite was disabled:
- a
GET /shaarli/tags/cloudfails with a404 Not Found - a
GET /shaarli/index.php/tags/cloudworks (200 OK)
Setting general.root_url to https://www.example.com/shaarli/index.php/ in config.json.phpas advised in the documentation does not fixes the issue (GET /shaarli/tags/cloud still returns a 404).
Is this a bug I should post on GitHub?
.htaccess properly allowed? You can also try to include these directives in your vHost configuration directly: https://github.com/shaarli/Shaarli/blob/master/.htaccess#L16-L21If that doesn't help you can open a support issue on github with your web servers config files as it will be easier to follow.
.htaccess were not taken into account by Apache (they disallowed AllowOverride in <Directory> with regular expression: and I did not know that...). One this part was fixed everything work just fine without any hack on change in .htaccess`: Thanks for the pointer.
If you're stuck please post your full setup on https://github.com/shaarli/Shaarli/issues/ including installed version, installation method/commands used, nginx/php-fpm configuration, error/debug logs, expected behavior/observed behavior etc etc
I'm starting a skin before google favoris shutdown
https://lab.frogg.it/agentcobra/google_favoris #WIP
Hi, I'm trying to install Shaarli on a ovh perso 2014 server. This server has no ssh access (only "professionnal", double price). I changed my php version to 7.3, no firewall, and I have this message : Warning: require_once(/home/MYDOMAIN/www/Shaarli-master/vendor/autoload.php): failed to open stream: No such file or directory in /home/MYDOMAIN/www/Shaarli-master/index.php on line 17
Fatal error: require_once(): Failed opening required '/home/MYDOMAIN/www/Shaarli-master/vendor/autoload.php' (include_path='.:/usr/local/php7.3/lib/php') in /home/MYDOMAIN/www/Shaarli-master/index.php on line 17 . I tried php 7.1 and 8.0, blank pages with other errors, and nothing in debug mode... Do someone have an idea on how to make it work? Thank you.
@kalvn RainTPL applies a bunch of regexes on links and resource path which are not always very accurate. One easy way to trick it is to put the href attribute in a new line. Another way is to output link instead of using it directly.
{$tmp='link'}
<{$tmp} rel="me" href="https://mastodon.xyz/@kalvn">
<link rel="me"
href="https://mastodon.xyz/@kalvn">It's very hacky, but that template engine served us well.
1 reply
var _paq = window._paq = window._paq || [];
/ tracker methods like "setCustomDimension" should be called before "trackPageView" /
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
(function() {
var u="//MYDOMAIN/matomo/";
_paq.push(['setTrackerUrl', u+'matomo.php']);
_paq.push(['setSiteId', '1']);
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
})();
</script>
I put the code generated by matomo inside MYDOMAIN\www\BLOG\tpl\default\page.header.html, but it doesn't work.
What do you mean by "it doesn't work"? Is the code you added present in the HTML page when you render it in your browser?
I'll check what's up with the Piwik plugin, maybe it got outdated without anyone noticing.