mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #258] Bookmarks doubling since new Floccus Version #249
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#249
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pemuelle79 on GitHub (Apr 5, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/258
Software versions
Steps to reproduce
Having a Bookmark with following a '#' in its URL Structure seems to confuse Floccus since the new version resulting in multiplying entries on each sync.
Expected outcome
Actual outcome
Debug log
@marcelklehr commented on GitHub (Apr 5, 2019):
Hey,
sorry for your trouble. I cannot replicate this, however. Do the duplicates reappear after removing them manually?
@e-alfred commented on GitHub (Apr 6, 2019):
I see this problem with links containing a hash (#) somewhere. These links are synced multiple times with strange changes to them. Here is one example:
Sync worked perfectly before the latest release.
Another problem is that deleting the links doesn't work because Floccus seems to re-sync them from a client even if they were deleted from the server in the Bookmarks UI. Shouldn't the latest change on the server (or on any Floccus client) take precedence over older states?
@marcelklehr commented on GitHub (Apr 6, 2019):
Strike this, confirmed. 😕
@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.