-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"sticky/pinned" posts #186
Comments
+1 |
Would a Or store a list of sticky posts in a config variable Core feature or plugin? |
Bump to top : no. It risk to be diffcult to have a good setting (how do you choose until when sticky post need to be retrieved, or how many time they will be sticked at the top, etc...) If it is implemented, it needs to work as private links are managed/displayed when logged in : logged user can identify private links into the full linklist and get only private links clicking on ?privateonly. We need the same without be logged. This function could be nice by default (because is yet pretty commons to "star" liked content : mail clients, github, twitter, etc...) |
"Bump link to top" button: see https://github.com/shaarli/Shaarli/wiki/Datastore-hacks#changing-the-timestamp-for-a-link Can we start by adding a
|
I created a github account to +1 this. Bump link to top wouldn't work. What I've been using as a workaround is setting the date timestamp to "2999" with some template hacks, but there should be a better way (like a star or pin button which edits the date in the background, or preferably add that :starred: key) |
Any insight on that feature? |
The workarounds in this thread are probably outdated because the IDs aren't dates anymore. I'm bumping the milestone because this shouldn't be very hard to implement. PR are appreciated, as always. |
Meaning that they always appear on top of all links Fixes shaarli#186
Meaning that they always appear on top of all links Fixes shaarli#186
add the ability to mark posts as "sticky", always displayed first on the first link list page.
The text was updated successfully, but these errors were encountered: