mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1989] Bookmarks and tabs completely out of order #1332
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1332
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @erahhal on GitHub (Jul 12, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1989
Which version of floccus are you using?
Chrome extension 5.5.6
How many bookmarks do you have, roughly?
60 tabs
Are you using other means to sync bookmarks in parallel to floccus?
No
Sync method
Linkwarden
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Version 138.0.7204.92 (Official Build) (64-bit)
Which version of Nextcloud Bookmarks are you using? (if relevant)
Linkwarden v2.10.1
Which version of Nextcloud? (if relevant)
No response
What kind of WebDAV server are you using? (if relevant)
No response
Describe the Bug
When syncing tabs (or bookmarks), they end up on linkwarden completely out of order, and thus out of order when synced back to other browsers.
Expected Behavior
Tabs and bookmarks remain in original order
To Reproduce
I don't now how to NOT reproduce
Debug log provided
@github-actions[bot] commented on GitHub (Jul 12, 2025):
Hello 👋
Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.
Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙
@marcelklehr commented on GitHub (Jul 12, 2025):
Hi @erahhal
Thank you for taking the time to give feedback by opening this issue. I appreciate it!
I'm sorry for your trouble. This is, however, expected as linkwarden does not have a way to store the order of links. I've already updated the code to reflect this in the UI to avoid surprises like this in the future.
@erahhal commented on GitHub (Jul 12, 2025):
Ah thank you. I will look for a corresponding ticket on Linkwarden.
@erahhal commented on GitHub (Jul 12, 2025):
Which backends support ordering? I'm looking at the floccus page and not finding the info.
@marcelklehr commented on GitHub (Jul 12, 2025):
Nextcloud Bookmarks, WebDAV, Google Drive, Git all support ordering. Only Linkwarden and Karakeep do not.
@erahhal commented on GitHub (Jul 14, 2025):
Thank you!
@erahhal commented on GitHub (Jul 26, 2025):
After thinking about this for a bit, I'd suggest removing Linkwarden or at least having a checkbox that the user acknowledges that their bookmarks will be scrambled if they use it. It's been a huge pain getting my thousands of bookmarks back in order.
@marcelklehr commented on GitHub (Jul 27, 2025):
I'm sorry for the trouble this has caused you. In the latest version I've added this information to the description of the relevant backends in the UI.
@erahhal commented on GitHub (Jul 27, 2025):
Thank you, your effort is appreciated!