mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #78] Trying to create a URL that is already bookmarked. This shouldn't happen! Please tell the developer about this! #77
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#77
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 @pablohess on GitHub (Apr 9, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/78
Software versions
Steps to reproduce
Expected outcome
sync completes successfully
Actual outcome
Trying to create a URL that is already bookmarked. This shouldn't happen! Please tell the developer about this!
url=https://fontawesome.com/v4.7.0/
@marcelklehr commented on GitHub (Apr 23, 2018):
Hey there, sorry for the delay!
I have a few questions for you. Did you already have any bookmarks on the server before syncing? Had you synced to the server before syncing it with the toolbar. Does this happen everytime you sync?
@pablohess commented on GitHub (Apr 25, 2018):
I can't reproduce it anymore with floccus 2.1.0.
But I'm using now the root folder as sync folder. Before I used the bookmark toolbar.
@marcelklehr commented on GitHub (Apr 26, 2018):
I've opened a pull request upstream, that fixes this: https://github.com/nextcloud/bookmarks/pull/479
@marcelklehr commented on GitHub (May 10, 2018):
This should be fixed in v2.2.2 now. Let me know if you still experience this error.
@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.