starred/floccus

Fork 0

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

[GH-ISSUE #1768] Losing the changes after sync error "E002: Bookmark to update doesn't exist anymore" #1180

New issue

Closed

opened 2026-02-25 22:39:14 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @alexmamutov on GitHub (Nov 13, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1768

Which version of floccus are you using?

5.3.3

How many bookmarks do you have, roughly?

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

Sync method

WebDAV

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

Edge

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)

Yandex Disk

Describe the Bug

I have two computers (A and B) to sync with both having MS Edge. Then after some period of successful syncing back and forth I get an error "E002: Bookmark to update doesn't exist anymore", and syncing effectively stops. The only way to unlock the syncing is to reset cache in Floccus options which, as it claims, should not delete data. Then this happens:

I reset cache on computer A and do syncing. At that moment the new bookmarks on A are still intact.
I do syncing on B, but got no new bookmarks from A. At that moment, I think, I got a message similar to "Failed to map parentId", but syncing is finished.
I do syncing on A and all the new bookmarks since the initial error are lost after syncing is finished.

Expected Behavior

Expecting no strange errors like "E002: Bookmark to update doesn't exist anymore" (what does it mean anyway?)
Expecting no bookmarks lost at any circumstances.

To Reproduce

I cannot reproduce the bug since the error "E002: Bookmark to update doesn't exist anymore" is rare and I cannot figure out what triggers it.

Debug log provided

I have provided a debug log file

Originally created by @alexmamutov on GitHub (Nov 13, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1768 ### Which version of floccus are you using? 5.3.3 ### How many bookmarks do you have, roughly? 5k ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method WebDAV ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Edge ### 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) Yandex Disk ### Describe the Bug I have two computers (A and B) to sync with both having MS Edge. Then after some period of successful syncing back and forth I get an error "E002: Bookmark to update doesn't exist anymore", and syncing effectively stops. The only way to unlock the syncing is to reset cache in Floccus options which, as it claims, should not delete data. Then this happens: 1. I reset cache on computer A and do syncing. At that moment the new bookmarks on A are still intact. 2. I do syncing on B, but got no new bookmarks from A. At that moment, I think, I got a message similar to "Failed to map parentId", but syncing is finished. 3. I do syncing on A and all the new bookmarks since the initial error are lost after syncing is finished. ### Expected Behavior Expecting no strange errors like "E002: Bookmark to update doesn't exist anymore" (what does it mean anyway?) Expecting no bookmarks lost at any circumstances. ### To Reproduce I cannot reproduce the bug since the error "E002: Bookmark to update doesn't exist anymore" is rare and I cannot figure out what triggers it. ### Debug log provided - [ ] I have provided a debug log file

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Nov 13, 2024):

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.
I'm Marcel and I created floccus a few years ago, maintaining it ever 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.
Note also that GitHub 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!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
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.

I look forward to working with you on this issue
Cheers 💙

@github-actions[bot] commented on GitHub (Nov 13, 2024): 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. I'm Marcel and I created floccus a few years ago, maintaining it ever 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. Note also that GitHub 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! To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket, 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. I look forward to working with you on this issue Cheers :blue_heart:

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Nov 16, 2024):

Hey @alexmamutov
It's a peculiar error that should not happen, indeed. Without a log it's hard to figure out what's causing this :/

@marcelklehr commented on GitHub (Nov 16, 2024): Hey @alexmamutov It's a peculiar error that should not happen, indeed. Without a log it's hard to figure out what's causing this :/

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Feb 24, 2026):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Feb 24, 2026): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-25 23:30:57 +03:00

[PR #1180] [MERGED] WebDav: Allow syncing via HTML file #1828

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#1180

No description provided.

Rows
Columns