Subfolders with same name do not get pushed correctly

[nzstefan]

Which version of floccus are you using?

5.7.0

How many bookmarks do you have, roughly?

3

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

no

Sync method

Git

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

Firefox 143.04, vivaldi 7.6.3797.63, chrome 141.0.7390.66, but I believe the actual issue is with firefox

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

My setup is based on one "master" (firefox) and multiple "slaves" (many other browsers). When I want to bookmark something, I bookmark it in the master, which always discards other bookmarks, and pushes its own bookmarks, while all other browsers are only allowed to pull, but never push to the repo. The repo is an xbel file.
I exclusively use the bookmarks bar for sync.
I have several folders on this bar, with subfolders and bookmarks in the subfolders. Some of the subfolders have the same name between the main folders. When I push, bookmarks that are added to one of the folders with a specific name appear in the xbel file in a different folder with the same name. It seems to be the "last" one in the order.

Expected Behavior

Bookmarks end up in the folder they were originally saved in.

To Reproduce

Create folder1, create subfolder, create folder2, create subfolder with same name as in subfolder1, save bookmark to first subfolder, bookmarks are published into the incorrect folder.

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! 💙

[nzstefan]

Sorry, it was meant to say 300 bookmarks

[marcelklehr]

Hi @nzstefan
I'm sorry for the delay, I've been on a much needed vacation. Thank you for taking the time to give feedback by opening this issue! I'll try to help troubleshoot as best I can.
Could you try triggering a sync from scratch in the profile settings of the "master" client? Make sure you have a backup of your bookmarks before you do this, and check your bookmarks for deleted bookmarks that may have come back. You can be sure that nothing will be deleted in this step, though.
This will reset the folder mappings and hopefully cause the correct folders to be associated with each other again between server and client. Let me know how it goes 🤞

[nzstefan]

Hi Marcel, Thanks for taking the time to look into this, I hope you had a good trip. Here is what I have done to test: 1. Make sure I have no deleted bookmarks in the Firefox master 2. Deleted all bookmarks in Vivaldi client, and cleared the deleted folder. 3. Reset the cache 4. Triggered a new upload 5. In Vivaldi triggered a new download Initially, the same thing happened: The bookmarks were supposed to appear like this: Client A ├── bookmarks… └── Devices (folder) ├── some bookmarks... ├── device A └── device B Client B ├── bookmarks… └── Devices (folder) ├── some bookmarks... ├── device C └── Device D After the sync on Vivaldi they appear like this Client A ├── bookmarks… └── Devices (folder) └── some bookmarks... Client B ├── bookmarks… └── Devices (folder) ├── some bookmarks... ├── device C ├── Device D ├── device A └── device B What is curious is that some of the “older” bookmarks stay put, while newer bookmarks have this behaviour, so possibly this was introduced in one of the updates. I know it's frustrating but I cannot tell you when this behaviour started. The bookmarks.xbel file already has the folders incorrect, so I think it is an upload, not a download issue. What I did next was to delete the bookmarks.xbel file and repeat the cache clear, delete etc exercise. This time, the bookmarks went into the correct folders. I am not sure if this is worth fixing for now because there seems to be an acceptable albeit cumbersome work-around. Let me know what else I can do to help. Best Regards Stefan

…

------ Original Message ------ From "Marcel Klehr" ***@***.***> To "floccusaddon/floccus" ***@***.***> Cc "nzstefan" ***@***.***>; "Mention" ***@***.***> Date 15/11/2025 12:52:24 AM Subject Re: [floccusaddon/floccus] Subfolders with same name do not get pushed correctly (Issue #2078)

marcelklehr left a comment [(floccusaddon/floccus#2078)](#2078 (comment)) Hi ***@***.***(https://github.com/nzstefan) I'm sorry for the delay, I've been on a much needed vacation. Thank you for taking the time to give feedback by opening this issue! I'll try to help troubleshoot as best I can. Could you try triggering a sync from scratch in the profile settings of the "master" client? Make sure you have a backup of your bookmarks before you do this, and check your bookmarks for deleted bookmarks that may have come back. You can be sure that nothing will be deleted in this step, though. This will reset the folder mappings and hopefully cause the correct folders to be associated with each other again between server and client. Let me know how it goes 🤞 — Reply to this email directly, [view it on GitHub](#2078 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ASJM2ISXLMKMRX3KZXGHTJD34W67RAVCNFSM6AAAAACJAWZNSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZSGM4DQMZTHE). You are receiving this because you were mentioned.Message ID: ***@***.***>

[marcelklehr]

Thank you for the explanation. I still cannot reproduce this, though. Has this been happening again since you nuked the xbel file? Have you updated to the latest version?

[github-actions]

Hello 👋
This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues
have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule
it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment
or remove the label to avoid it getting closed.

Cheers 💙

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.