mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #215] Chromium Brave: Folder #-1[undefined] contains an nonexistent bookmark 19875 #206
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#206
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 @digrouz on GitHub (Dec 20, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/215
Software versions
Steps to reproduce
Hello, as the latest brave is now based on chromium, I tried to install the Floccus extension to sync my bookmark.
Expected outcome
bookmark syncs :)
Actual outcome
I receive the following error and none bookmark were synchronized
Note that floccus work successfully in Chrome.
Debug log
@Tank-Missile commented on GitHub (Dec 20, 2018):
There's a bug in versions prior to 0.14.3 that caused the bookmarks app to return other user's bookmark IDs (but no actual data) in multi-user environments. All signs point to the issue I was having in #201.
@marcelklehr commented on GitHub (Dec 20, 2018):
I agree, this is reminiscent of #201. @digrouz please try updating the bookmarks app :)
@digrouz commented on GitHub (Dec 20, 2018):
I just updated my bookmark app and still have the same issue.
@digrouz commented on GitHub (Dec 21, 2018):
Do you need the debug log ?
@marcelklehr commented on GitHub (Dec 21, 2018):
@digrouz That would be useful, yes. You can also send it via mail, if you like :)
@digrouz commented on GitHub (Dec 22, 2018):
I've sent it by email.
@iroedius commented on GitHub (Dec 23, 2018):
I have the same error.
Folder #-1[undefined] contains an nonexistent bookmark 7When there are no bookmarks on the server the sync goes fine but as soon as I add at least one bookmark and sync that to the Nextcloud server, every sync after that returns this error.
Chromium 71.0.3578.98 on Linux (vanilla, not Brave)
Nextcloud 15.0.0
Bookmarks 0.14.3
Floccus 3.2.0 with Nextcloud Bookmarks (v0.14+) sync method
@marcelklehr commented on GitHub (Dec 23, 2018):
I have a suspicion: Which database do you use on the server?
@iroedius commented on GitHub (Dec 23, 2018):
PostgreSQL 11.1 here.
@digrouz commented on GitHub (Dec 23, 2018):
PostgreSQL 9.6 here.
@marcelklehr commented on GitHub (Dec 23, 2018):
I knew it.
@marcelklehr commented on GitHub (Dec 23, 2018):
PostgreSQL doesn't return numbers as strings like mysql which makes a strict equality check fail. This is a one liner :)
@tomershvueli commented on GitHub (Dec 29, 2018):
I'm also seeing this issue on Vivaldi 2.2.1388.37, Nextcloud 14.0.4, Bookmarks 0.15.1, and Floccus 3.2.1 with Nextcloud Bookmarks (v0.14+) sync method. Commenting so I can stay in the loop.
@marcelklehr commented on GitHub (Dec 31, 2018):
I've just released the fix :)
@tomershvueli commented on GitHub (Dec 31, 2018):
Just in time for the New Year! ;) however, I'm now seeing a different issue where all of my bookmarks are imported into the selected folder as siblings, and not in the hierarchal manner they were saved in. Am I missing something?
@marcelklehr commented on GitHub (Dec 31, 2018):
@tomershvueli Mmh. Could you open a new issue for this and fill out the issue template? This should make troubleshooting easier :)
@digrouz commented on GitHub (Jan 1, 2019):
I see the same behavior, All my bookmark are now syncing, but they are not in a folder.
@tomershvueli commented on GitHub (Jan 2, 2019):
@marcelklehr I just opened up a new ticket (#221) with the new issue. Happy to help test new versions!
@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.