The personal, minimalist, super-fast, database free, bookmarking service - community repo
I cant find any release notes or migration guides - does shaarli no longer support installation in a subdirectory (with reverse proxy)?
OK so I just tried, and it's working fine. BUT I had to ajust the nginx rewrite rule from:
location / {
# Slim - rewrite URLs
try_files $uri /index.php$is_args$args;
}to
location / {
# Slim - rewrite URLs
try_files $uri /shaarli/index.php$is_args$args;
}.docker/nginx.conf by changing the root directory from /var/www/shaarli to /var/www (and the above change), built the Docker image, and ran it behind my usual reverse proxy.
llaq On my fresh shaarli installation, i have a error :
llaq Failed to lock the file./srv/data/webserver/links.lelibreauquotidien.fr/vendor/malkusch/lock/classes/mutex/FlockMutex.php141
llaq On my fresh shaarli installation, i have a error :
llaq Failed to lock the file.vendor/malkusch/lock/classes/mutex/FlockMutex.php141
llaq Error : An unexpected error happened, and the error template could not be displayed.
Couldn't load data from the data store file "data/datastore.php". Your data might be corrupted, or your file isn't readable.
llaq ls -l result : -rw-r--r-- 1 root root 0 Dec 6 19:03 datastore.php
llaq * ls -l result :-rw-r--r-- 1 root root 0 Dec 6 19:03 datastore.php
hook_pluginname_save_link function, nothing happens on application side. It's like no error occurred. I guess that the error is catched by Shaarli and sent to the next template rendering function but since the response to POST /shaare is a 302, the user never sees the error.Would there be a way to provide better error handling for plugins? We could imagine something similar to middlewares in most web frameworks (Slim, Express.js, etc.) where each plugin would be responsible for calling the next one and could interrupt the chain with an exception if relevant, or keep going but still logging the exception somewhere so that it can be displayed in the UI.
plugin_errors variable. It prevents plugins from making Shaarli unusable due to (for example) plugin compatibility issue. In the default template it used in page.header.html.If you think errors should be handled in a better way, you can open an issue, but I'm not in favor of blocking everything due to plugin errors.
Ah sorry I missed the redirection part of your message. I have recently develop such a feature, similar to Symfony flashbag, here:
- https://github.com/shaarli/Shaarli/blob/master/application/render/PageBuilder.php#L170
- https://github.com/shaarli/Shaarli/blob/master/application/front/controller/admin/ShaarliAdminController.php#L51
We should find a proper way to tie the SessionManager with plugins, BUT if you want to hack your way through, you might get the result you want by using superglobals, e.g. $_SESSION['global_errors'][] = 'Noooo!';.
@ArthurHoaro my apologies.
So anywho, doing some research of backing up and restoring...I found retrieving the datastore.php is where all of your clippings/saved things are.
I pulled the datastore.php and transferred it to where it was supposed to go (/data/)
But I'm getting this error: https://pastebin.com/NBwv8e8K
That made me think of the initial installation process. I remember seeing something about 'slim' under the php prerequisites
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