mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 22:55:59 +03:00
[GH-ISSUE #104] Trying to create a URL that is already bookmarked. This shouldn't happen! Please tell the developer about this! #100
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#100
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 @JDrewes on GitHub (May 16, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/104
Trying to create a URL that is already bookmarked. This shouldn't happen! Please tell the developer about this!
Hereby done!
At first, I added a new bookmark on computer B.
This bookmark was then synced to computer A, but in 4 identical copies. After deleting 3 of them on A, the above error appeared. Computer B is showing a different error about a non-existing entry (I am not in front of that computer right now).
Computer C can still sync without problems (and without duplicates).
Deleting all 4 copies of the newly added bookmark on A didn't change anything.
Software versions
Steps to reproduce
@marcelklehr commented on GitHub (May 16, 2018):
Hey @JDrewes
So, this is a known problem, more or less. There's a bug in the server app that doesn't handle specific URLs very well. If URL A is redirected to URL B on some website, the nextcloud server stores the bookmark as URL B, but when URL A is being added again later on, it appears that it hasn't been added yet, which is true in some way, as URL A has been replaced with URL B as per the redirect.
I've known about this problem for some time, fixed it on the server side (which hasn't been released yet) and fixed a reincarnation on the client side.
Now, I've got a few questions for you to narrow this down:
Since when does the error appear for you and was v2.2.2 the first floccus version that you installed?
@JDrewes commented on GitHub (May 17, 2018):
Hi Marcelklehr,
I've been attempting to use floccus since several versions, I don't quite remember which one - definitely before 2.x.
Several times, but most recently when 2.2.1 came out, I made a backup, deleted all bookmarks on all clients and the server, then restored the backup on one client and synced it back to all others.
The current error occurs since 2.2.2, but 2.2.2 came out very quickly after 2.2.1 so I can't be sure it wouldn't have happened there, too.
Originally, my intention was to sync all my bookmarks, but there was soooo many duplicates in there (intentionally) that I gave up on it. I am now syncing only one folder (the toolbar folder).
I used firefox sync before, but I have long since turned it off on all my computers.
PS: It would be neat to have a "delete all bookmarks" function on the server side, rather than having to click through all every time.
Thank you for your valiant efforts, by the way!
@marcelklehr commented on GitHub (May 19, 2018):
Ok thank you, then I'll investigate some more.
Deleting multiple bookmarks will get easier with the upcoming version of the bookmarks app (fingers crossed).
@marcelklehr commented on GitHub (May 23, 2018):
@JDrewes Do you still experience this error with the latest version? (v2.2.3)
@JDrewes commented on GitHub (May 24, 2018):
On the computer affected by the error, the error disappeared after upgrading to 2.2.3, and new bookmarks arrived (previously, syncing didn't work, likely because of the above-mentioned error).
I will check later on other computers but it seems to be resolved, for now. I didn't find any duplicates, yet, either. Nice :-)
@marcelklehr commented on GitHub (May 26, 2018):
Closing for now. Shout if anything pops up :)
@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.