starred/floccus

Fork 0

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

[GH-ISSUE #259] Sync does not respect the latest changes on another client or Nextcloud Bookmarks app #248

New issue

Closed

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

kerem commented

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

Owner

Originally created by @e-alfred on GitHub (Apr 9, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/259

Software versions

Browser: Vivaldi, Opera, Firefox, Chrome
Nextcloud: 15.0.6
Nextcloud Bookmarks app: 0.16.4
Floccus: 3.2.15
Floccus sync method: nextcloud-folders

Steps to reproduce

A lot of redundant bookmarks were created due to this bug: https://github.com/marcelklehr/floccus/issues/258
If I delete or change bookmarks on one client or the Nextcloud Bookmarks App directly, the will be re-synced by other clients.

Expected outcome

The latest changes on a client or the Bookmarks app should always take precedence over an older state on another client or the server. Bookmarks that have changed or were deleted shouldn't be re-synced with an older state from another client.

Actual outcome

Unwanted and deleted or changed Bookmarks are re-synced from other clients to the server while ignoring the fact that they were deleted or changed on another system.

Originally created by @e-alfred on GitHub (Apr 9, 2019). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/259  ### Software versions  - Browser: Vivaldi, Opera, Firefox, Chrome - Nextcloud: 15.0.6 - Nextcloud Bookmarks app: 0.16.4 - Floccus: 3.2.15 - Floccus sync method: nextcloud-folders  ### Steps to reproduce  1. A lot of redundant bookmarks were created due to this bug: https://github.com/marcelklehr/floccus/issues/258 2. If I delete or change bookmarks on one client or the Nextcloud Bookmarks App directly, the will be re-synced by other clients. ### Expected outcome  The latest changes on a client or the Bookmarks app should always take precedence over an older state on another client or the server. Bookmarks that have changed or were deleted shouldn't be re-synced with an older state from another client. ### Actual outcome  Unwanted and deleted or changed Bookmarks are re-synced from other clients to the server while ignoring the fact that they were deleted or changed on another system.

kerem closed this issue

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

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Apr 9, 2019):

Could you try resetting the cache on all clients, syncing all clients, and then removing the bookmarks in question again?

@marcelklehr commented on GitHub (Apr 9, 2019): Could you try resetting the cache on all clients, syncing all clients, and then removing the bookmarks in question again?

kerem commented

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

Author

Owner

@e-alfred commented on GitHub (Apr 10, 2019):

Okay, I bit the bullet and did the following:

Disable all Floccus clients so they stop syncing bogus bookmarks
Remove all redundant bookmarks from the Bookmarks UI in Nextcloud (the new interface makes it really easy which is awesome!)
Removed the bookmarks in the folder synced with Floccus on each browser
Set the "merge bookmarks" checkmark and enabled sync in Floccus again

Now everything works again, but I think this is still a bug. The last change on any client or the server UI should take precedence over all other clients with an older state. Syncing back old bookmarks from other clients is very annoying for users actually. The only exception probably would be a deletion of all bookmarks similar to the Nextcloud sync client warning of a complete removal of everything. Maybe a recycle bin in the Bookmarks app would be another idea to mitigate this?

@e-alfred commented on GitHub (Apr 10, 2019): Okay, I bit the bullet and did the following: - Disable all Floccus clients so they stop syncing bogus bookmarks - Remove all redundant bookmarks from the Bookmarks UI in Nextcloud (the new interface makes it really easy which is awesome!) - Removed the bookmarks in the folder synced with Floccus on each browser - Set the "merge bookmarks" checkmark and enabled sync in Floccus again Now everything works again, but I think this is still a bug. The last change on any client or the server UI should take precedence over all other clients with an older state. Syncing back old bookmarks from other clients is very annoying for users actually. The only exception probably would be a deletion of all bookmarks similar to the Nextcloud sync client warning of a complete removal of everything. Maybe a recycle bin in the Bookmarks app would be another idea to mitigate this?

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Apr 10, 2019):

the new interface makes it really easy which is awesome!

Glad you like it :)

Syncing back old bookmarks from other clients is very annoying for users actually.

I will try to replicate this, but I agree, it shouldn't do this.

@marcelklehr commented on GitHub (Apr 10, 2019): > the new interface makes it really easy which is awesome! Glad you like it :) > Syncing back old bookmarks from other clients is very annoying for users actually. I will try to replicate this, but I agree, it shouldn't do this.

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Apr 10, 2019):

I cannot replicate this with any normal bookmarks that I delete, so this behavior probably was specific to the circumstances with the duplicates. Thanks for your feedback, as always :) 🌟

@marcelklehr commented on GitHub (Apr 10, 2019): I cannot replicate this with any normal bookmarks that I delete, so this behavior probably was specific to the circumstances with the duplicates. Thanks for your feedback, as always :) :star2:

kerem commented

2026-02-25 22:36:36 +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:21 +03:00

[PR #248] [MERGED] Added font color as black #1477

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

No description provided.

Rows
Columns