Closed dajare closed 3 years ago
Exactly the same situation here, even the same error message. Thank you for any hint as where to go now. Salutations
Exactly the same situation here, even the same error message. Thank you for any hint as where to go now. Salutations
I rolled back to 0.11.1 Shaarli on the instance that I use with Material. Hopefully we can work out (or @kalvn can! 😬) how to get this working with 0.12.1.
I didn't have enough time to start working on v0.12.1 (which seems to be massive) compatibility but I'll try to do that soon!
I didn't have enough time to start working on v0.12.1 (which seems to be massive) compatibility but I'll try to do that soon!
Grateful for that! I've actually had a look a few times at trying to create a "minimalist" theme for Shaarli (something I've done with my CMS of choice quite few times over the years). It looks anything but easy with Shaarli, and all the trickier if a point-upgrade brings so many changes! So thanks for keeping Material up-to-date.
Many projects treat the 0th major release as unstable where even point releases can break things, and maintainers don't guarantee compatibility with earlier releases, so while this is being annoying, this is how the world works. Shaarli is about to get its 1st major release in some time, then point releases shouldn't break so many things: https://github.com/shaarli/Shaarli/issues/1640
I just published v0.12.0 https://github.com/kalvn/Shaarli-Material/releases/tag/v0.12.0 which should solve that problem.
Working on v0.12.1 now :)
I just published v0.12.0 https://github.com/kalvn/Shaarli-Material/releases/tag/v0.12.0
Thank you very much. I'm only in this situation because I like your work so much. So thank you for sharing it!
This theme is great ! But, when using it with shaarli v0.12.1, the red "plus" button is missing (the button used to add new links)
You can follow this issue here @pascollin : https://github.com/kalvn/Shaarli-Material/issues/117
I've rebuilt my Shaarli using the support-v012
branch, and now all my previously observed issues are gone. There were some unnoticed changes on that branch in November, I suggest you all to try it :) Happy new year to everyone! :tada:
FYI: I had similar symptoms (but different cause). My problem was due to folder/file permissions on the /data and /cache folders and subfolders. When I reinstalled Synology DSM (this is where docker is installed and Shaarli is hosted)... I forgot about making the /data and /cache folders writeable to "users".
To fix MY problem: I stopped the container, stopped inheritence of permissions for /shaarli folder in docker, then made /data and /cache writeable to 'users'. Then I restarted the container and it started up with no problems!
Hopefully this anecdote/scenario can help someone else with a similar (Synology-related) problem in the future.
I've been using Material for a long time now with a particular Shaarli instance (beginning around v. 0.9, I think). I've been keeping things up-to-date, though, and today upgraded my Shaarli's to 0.12.1 (from 0.11.1). With the default template, everything is fine. With Material (latest!), however, I get this error message:
I have read through the "Compatibility with Shaarli v0.12.0-beta" #115 thread, and I'm none the wiser. Grateful for any help with this — I miss Material! (Update 2020-11-20 : I missed Material so much that I rolled that instance back to 0.11.1! So normal service is resumed, although it would be great to have this running with 0.12.1, too.)