starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 14:45:59 +03:00

[GH-ISSUE #425] Purged bookmarks in FF #327

New issue

Closed

opened 2026-02-25 22:36:49 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 22:36:49 +03:00

Owner

Originally created by @enoch85 on GitHub (Dec 29, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/425

Describe the bug
I just noticed like 20 of my ~300 bookmarks are gone!

To Reproduce
Steps to reproduce the behavior:

Use the bookmarks app in Firefox as usual and sync it with Nextcloud

Expected behavior
Bookmars shouldn't be purgedif a sync fails.

Desktop (please complete the following information):

OS: Ubuntu Budgie 18.04
Browser Firefox
Browser Version 70.0.1
Floccus version: 3.5.3
Floccus sync method: Webdav I think

Server (please complete the following information):

OS:Ubuntu 18.04
Nextcloud version: 17.0.2 (maybe happened earlier, noticed it now)
Bookmarks app version: 2.3.4

Debug log
https://is.gd/PcrAdP

Debug log provided

Additional context
Just a question really, are deleted/purge bookmarks easy to get back?

Originally created by @enoch85 on GitHub (Dec 29, 2019). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/425 **Describe the bug** I just noticed like 20 of my ~300 bookmarks are gone! **To Reproduce** Steps to reproduce the behavior: 1. Use the bookmarks app in Firefox as usual and sync it with Nextcloud **Expected behavior** Bookmars shouldn't be purgedif a sync fails. **Desktop (please complete the following information):** - OS: Ubuntu Budgie 18.04 - Browser Firefox - Browser Version 70.0.1 - Floccus version: 3.5.3 - Floccus sync method: Webdav I think **Server (please complete the following information):** - OS:Ubuntu 18.04 - Nextcloud version: 17.0.2 (maybe happened earlier, noticed it now) - Bookmarks app version: 2.3.4 **Debug log** https://is.gd/PcrAdP - [X] Debug log provided **Additional context** Just a question really, are deleted/purge bookmarks easy to get back?

kerem

2026-02-25 22:36:49 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jan 9, 2020):

Hello @enoch85
I'm sorry you ran into trouble with missing bookmarks.

Just a question really, are deleted/purge bookmarks easy to get back?

With the webdav method, there is no way to get back deleted bookmarks. For the bookmarks app, a trash bin to recover bookmarks from is planned. However, if you are looking for the contents of the folder called "Github", you can still find them in the logs 🎉

@marcelklehr commented on GitHub (Jan 9, 2020): Hello @enoch85 I'm sorry you ran into trouble with missing bookmarks. > Just a question really, are deleted/purge bookmarks easy to get back? With the webdav method, there is no way to get back deleted bookmarks. For the bookmarks app, a trash bin to recover bookmarks from is planned. However, if you are looking for the contents of the folder called "Github", you can still find them in the logs :tada:

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@enoch85 commented on GitHub (Jan 9, 2020):

if you are looking for the contents of the folder called "Github", you can still find them in the logs

Thanks!

a trash bin to recover bookmarks from is planned

That would have saved me this time. Would be nice to see in the near future, like tomorrow. :D

Also, it would be nice if you warned the user somehow on big sync changes before they happen - or fix this bug so that it never happens again.

Thanks for a great app!

@enoch85 commented on GitHub (Jan 9, 2020): > if you are looking for the contents of the folder called "Github", you can still find them in the logs Thanks! > a trash bin to recover bookmarks from is planned That would have saved me this time. Would be nice to see in the near future, like tomorrow. :D Also, it would be nice if you warned the user somehow on big sync changes before they happen - or fix this bug so that it never happens again. Thanks for a great app!

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jan 9, 2020):

That would have saved me this time.

If you are indeed using the webdav sync method, that wouldn't have saved you either. But using the bookmarks app sync method that would have saved you.

Also, it would be nice if you warned the user somehow on big sync changes before they happen - or fix this bug so that it never happens again.

I will analyse you log further to find out what caused this exactly.

@marcelklehr commented on GitHub (Jan 9, 2020): > That would have saved me this time. If you are indeed using the webdav sync method, that wouldn't have saved you either. But using the bookmarks app sync method that would have saved you. > Also, it would be nice if you warned the user somehow on big sync changes before they happen - or fix this bug so that it never happens again. I will analyse you log further to find out what caused this exactly.

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@7usr7local commented on GitHub (Jan 10, 2020):

I seemed to have that issue to. Hard to reproduce, so I cannot provide logs (yet).
However, when I ticked "Trigger sync from scratch" in the options, a lot of the bookmarks seemed to have come back. Some were duplicated. Worth to know, I am syncing with two firefoxes on two different desktop systems at the same time - maybe there is some kind of race condition. Whether everything was restored or some are still missing I cannot say, as I have no second source to compare with.
Anyway, @enoch85, trying that checkbox might be worth a try in your case too - and your experience with that might give @marcelklehr some clues on the issue itself.
(Doing a bookmark backup on the firefox side beforehand is hopefully needless to say ...)

@7usr7local commented on GitHub (Jan 10, 2020): I seemed to have that issue to. Hard to reproduce, so I cannot provide logs (yet). However, when I ticked "Trigger sync from scratch" in the options, a lot of the bookmarks seemed to have come back. Some were duplicated. Worth to know, I am syncing with two firefoxes on two different desktop systems at the same time - maybe there is some kind of race condition. Whether everything was restored or some are still missing I cannot say, as I have no second source to compare with. Anyway, @enoch85, trying that checkbox might be worth a try in your case too - and your experience with that might give @marcelklehr some clues on the issue itself. (Doing a bookmark backup on the firefox side beforehand is hopefully needless to say ...)

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@enoch85 commented on GitHub (Jan 10, 2020):

I've actually disabled Floccus after this happened.

I'm happy to test when a fix is released.

@enoch85 commented on GitHub (Jan 10, 2020): I've actually disabled Floccus after this happened. I'm happy to test when a fix is released.

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@marcelklehr commented on GitHub (Feb 1, 2020):

@enoch85 v4.0.0-alpha.1 is available for testing, now :) see https://github.com/marcelklehr/floccus/issues/439

@marcelklehr commented on GitHub (Feb 1, 2020): @enoch85 v4.0.0-alpha.1 is available for testing, now :) see https://github.com/marcelklehr/floccus/issues/439

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 2, 2020):

I'm happy to announce that v4.0.0 has just been released, which should fix this. I'm closing this for now. Feel free to shout if this comes up again!

@marcelklehr commented on GitHub (Mar 2, 2020): I'm happy to announce that v4.0.0 has just been released, which should fix this. I'm closing this for now. Feel free to shout if this comes up again!

kerem commented

2026-02-25 22:36:49 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 21, 2023):

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 (Mar 21, 2023): 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 22:40:27 +03:00

[PR #327] [MERGED] Bump @babel/preset-env from 7.4.5 to 7.5.5 #1511

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

No description provided.

Rows
Columns