mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #158] Chrome won't download bookmarks from NextCloud #150
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#150
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 @bernd-wechner on GitHub (Aug 28, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/158
OK, I have floccus working beautifully between Firefox instances at home and work. Thumbs up.
Now I tried my first Chrome instance. I first deleted all my local bookmarks. Clean slate. Then installed NextCloud from the Chrome store, and configured my server. I click Sync Now and it finishes fast and does nothing.
I checked the logs, and it sees all my bookmarks on the server fine. But crucial bits just before th end sync look like this:
which looks suspicious. But I can't interpret it. Can provide whole log if it helps. But it may be a use case that rings bells. New install, No bookmarks. What should happen? Server marks downloaded and installed I guess (as a special outcome of server marks downloaded, compared and merged).
@marcelklehr commented on GitHub (Aug 28, 2018):
Thanks for reporting! :)
@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.