starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #1959] Bookmarklets get duplicated in browser #1311

New issue

Closed

opened 2026-02-25 22:39:38 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 22:39:38 +03:00

Owner

Originally created by @Nebucatnetzer on GitHub (May 17, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1959

Which version of floccus are you using?

5.4.5

How many bookmarks do you have, roughly?

200

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

Yes, I also sync via Mozilla account

Sync method

Nextcloud Bookmarks

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

Firefox

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

15.1.0

Which version of Nextcloud? (if relevant)

31.0.4

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

No response

Describe the Bug

Similar to #1731 my bookmarklets all show up as duplicates on Firefox.
On Nextcloud they seem to be working fine.

In this screenshot you can see that the bookmarklets show up more than once.

In order to not mess up the bookmarks in Nextcloud I tried to only pull the bookmarks from Nextcloud to the browser but that didn't work.

Some bookmarklets are stored twice in different directories because I use them both at work and at home.

floccus-5.4.5-2025-05-17-redacted.log

Expected Behavior

The same file structure as on Nextcloud should appear in my browser.

To Reproduce

I don't know.

Debug log provided

I have provided a debug log file

Originally created by @Nebucatnetzer on GitHub (May 17, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1959 ### Which version of floccus are you using? 5.4.5 ### How many bookmarks do you have, roughly? 200 ### Are you using other means to sync bookmarks in parallel to floccus? Yes, I also sync via Mozilla account ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Firefox ### Which version of Nextcloud Bookmarks are you using? (if relevant) 15.1.0 ### Which version of Nextcloud? (if relevant) 31.0.4 ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug Similar to #1731 my bookmarklets all show up as duplicates on Firefox. On Nextcloud they seem to be working fine. In this screenshot you can see that the bookmarklets show up more than once. ![Image](https://github.com/user-attachments/assets/ae0309b9-7b6b-4819-9210-0b0480697985) In order to not mess up the bookmarks in Nextcloud I tried to only pull the bookmarks from Nextcloud to the browser but that didn't work. Some bookmarklets are stored twice in different directories because I use them both at work and at home. [floccus-5.4.5-2025-05-17-redacted.log](https://github.com/user-attachments/files/20265944/floccus-5.4.5-2025-05-17-redacted.log) ### Expected Behavior The same file structure as on Nextcloud should appear in my browser. ### To Reproduce I don't know. ### Debug log provided - [x] I have provided a debug log file

kerem

2026-02-25 22:39:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:39:39 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 17, 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 💙

@github-actions[bot] commented on GitHub (May 17, 2025): Hello :wave: 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 :blue_heart:

kerem commented

2026-02-25 22:39:39 +03:00

Author

Owner

@Nebucatnetzer commented on GitHub (May 17, 2025):

I first wrote that some directories aren't correct.
After I cleared the cache the bookmarks started to show up.

@Nebucatnetzer commented on GitHub (May 17, 2025): I first wrote that some directories aren't correct. After I cleared the cache the bookmarks started to show up.

kerem commented

2026-02-25 22:39:39 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 18, 2025):

Hey Andreas,
thank you for giving feedback by opening this issue! I appreciate it.

~~I cannot to reproduce this, but~~ judging from the code, it's possible that this can happen if the first sync after opening the browser fails because of missing network access. If you then get network access and floccus syncs, it will try to create bookmarklets again for intricate reasons. Edit: I can reproduce this! 🎉

Going forward, you should be able to simply delete the duplicates and continue syncing normally. I will fix this in the upcoming release.

@marcelklehr commented on GitHub (May 18, 2025): Hey Andreas, thank you for giving feedback by opening this issue! I appreciate it. ~~I cannot to reproduce this, but~~ judging from the code, it's possible that this can happen if the first sync after opening the browser fails because of missing network access. If you then get network access and floccus syncs, it will try to create bookmarklets again for intricate reasons. Edit: I can reproduce this! 🎉 Going forward, you should be able to simply delete the duplicates and continue syncing normally. I will fix this in the upcoming release.

kerem commented

2026-02-25 22:39:39 +03:00

Author

Owner

@Nebucatnetzer commented on GitHub (May 19, 2025):

Thank you I will report back how it behaves on my side.

@Nebucatnetzer commented on GitHub (May 19, 2025): Thank you I will report back how it behaves on my side.

kerem commented

2026-02-25 22:39:39 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 29, 2025):

Any news?

@marcelklehr commented on GitHub (Jul 29, 2025): Any news?

kerem commented

2026-02-25 22:39:39 +03:00

Author

Owner

@Nebucatnetzer commented on GitHub (Jul 30, 2025):

Please excuse, I forgot about this.
I've seen it happen once after the new release but not since.

@Nebucatnetzer commented on GitHub (Jul 30, 2025): Please excuse, I forgot about this. I've seen it happen once after the new release but not since.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1311

No description provided.

Rows
Columns