Bookmarks order changed

[pierreribeiro]

Which version of floccus are you using?

5.6.0

How many bookmarks do you have, roughly?

500

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Google Drive

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

140.0.7339.81 64 bits

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

In my bookmarks bar, I organize each one by importance. It's happening that, after syncing, my folders appear disorganized, in random positions. So I manually rearrange the positions, but after another sync, they're messed up again.

Expected Behavior

Keep each bookmark folder in its original position in the bookmarks bar before synchronization

To Reproduce

I manually rearrange the positions, but after another sync, they're messed up again.

Debug log provided

• I have provided a debug log file

[github-actions]

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]

Hi @pierreribeiro
Thank you for taking the time to give feedback!
Can you try if updating to floccus v5.7.0 helps?

[marcelklehr]

@pierreribeiro Any update?

[balthanon]

So I've run across this myself (or at least something similar) and finally got an example captured-- I've attached the redacted after log here (or maybe I'll just email it to you-- still having issues uploading a file for some reason). If it doesn't have the information you need, let me know and I can get the full logs to you. I have one that was a before and after.

What I'm seeing happen is that sometimes bookmarks will move to the bottom of a folder after being updated. For instance, I have a set of comic links where as I catch up on the comic I will update the bookmark with the new page that represents whatever comic I'm on. Sometimes just the URL, sometimes URL and title.

The attached file is an example of a Penny Arcade bookmark (rwiEFa6OX5Zc) in the Monthly check folder (tanDgkBL1c9R) getting pushed to the bottom of the folder rather than where I had it located near the top since I check on it pretty regularly.

This is on Floccus 5.7.0 and Firefox 144.0.2 (64-bit). (There is also another addon in the mix-- Update Bookmarks v1.9.3; if I can get it happening regularly again today I'll try and just update the bookmark manually too to make sure that also triggers it.)

[balthanon]

floccus-5.7.0-2025-11-07-redacted.log

Or apparently it's just that Github doesn't like Firefox.

[dearkafka]

Bookmarks order changed - but different algo:
When I add new bookmark that last added bookmark (added by Chrome, placed at the end) after sync always appears on top of all bookmarks. So as I see nothing like that was reported by anyone, I need to add that my top bookmarks (that I want to be top) have empty name field (that way they use less space in UI). actually no, its not the core, same happens with names as well. so after sync, when it fetches remote it always reorder.

[chrysillis]

2025-11-26T09:01:19.173Z Failed to execute REORDER: E012: Folder ordering is missing some of the folder's children
Moving on.

Starting recently, I noticed floccus no longer respects my bookmark ordering in Firefox. I've tried clearing cache, pushing sync to server and so on. It just won't sync the order anymore. This only seems to impact Firefox, as Chrome works correctly.

Firefox version: 145.0.2
Floccus version: 5.8.1
Backend sync: GitLab
Sync type: XBEL

floccus-5.8.1-2025-11-26-redacted.log

[jms667]

Hello,

I also have the same issue.
When re-ordering my bookmark in firefox and syncing again, the original order come back (not the modified one).
Doing the same with chrome is working fine.

Firefox version: 145.0.2
Floccus version: 5.8.1
Backend sync: google drive
Sync type: XBEL

Chrome version: 142.0.7444.176
Floccus version: 5.8.0
Backend sync: google drive
Sync type: XBEL

Thanks for your help.

[marcelklehr]

Hello everyone!
Thank you for taking the time to give feedback via this issue!

Folder ordering is missing some of the folder's children

This error turned out to be the key to solving this issue: The BrowserTree implementation that executes the ORDER action on the actual browser bookmarks doesn't even throw this error, but the Caching tree does. Since September, floccus employs a tree double that gets the exact same manipulation as the actual tree in order to be able to tell when the user has changed the tree while floccus is changing the tree. And this tree double uses the Caching tree, which is fine as long as the user doesn't have any bookmarks in their tree that cannot be synced. You'll notice that the BrowserTree is nice enough to keep your unsyncable bookmarks at the same location in the list as before the sync. But with the tree double, as soon as such bookmarks turn up things get haywire because the BrowserTree implementation leaves the actual tree with a different order than the tree double which will just fail (with the above message) and just keep the old order. After this first sync, the tree double will be used as the ground truth for the next sync, and it will appear to floccus that the bookmarks order has changed, when it hasn't and weird things will happen. Now that this is fixed, it' is a great moment for me to add a test case for this scenario so that it won't happen again :)