mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #221] Chromium Vivaldi - Syncing without Hierarchy #211
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#211
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 @tomershvueli on GitHub (Jan 2, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/221
Software versions
Steps to reproduce
Expected outcome
I would have expected the bookmarks to be synced locally in the proper hierarchy that they were saved in.
Actual outcome
All of the bookmarks were saved in the parent directory as siblings, without any hierarchical data.
Debug log
Debug looked a lot like this:
(local)CREATE - #undefined[MindSumo](https://mindsumo.com/home) parentId: 1715 COMPARE { localItem: null, cacheItem: null, serverItem: - #2670;-1[Course: EI Garage](https://moodle-projects.wolfware.ncsu.edu/course/view.php?id=1085) parentId: -1 } (local)CREATE - #undefined[Course: EI Garage](https://moodle-projects.wolfware.ncsu.edu/course/view.php?id=1085) parentId: 1715 COMPARE { localItem: null, cacheItem: null, serverItem: - #2671;-1[Interview Cake](http://interviewcake.com/tips-and-tricks) parentId: -1 } (local)CREATE - #undefined[Interview Cake](http://interviewcake.com/tips-and-tricks) parentId: 1715 COMPARE { localItem: null, cacheItem: null, serverItem: - #2672;-1[The Man in Seat Sixty-One - the train travel guide...](http://seat61.com) parentId: -1 } (local)CREATE - #undefined[The Man in Seat Sixty-One - the train travel guide...](http://seat61.com) parentId: 1715 COMPARE { localItem: null, cacheItem: null, serverItem: - #2673;-1[share passwords once](https://oneshar.es) parentId: -1 } (local)CREATE - #undefined[share passwords once](https://oneshar.es) parentId: 1715 COMPARE { localItem: null, cacheItem: null, serverItem: - #2674;-1[Algorithms [Algorithm Wiki]](http://will.thimbleby.net/algorithms/doku.php) parentId: -1 }@digrouz commented on GitHub (Jan 2, 2019):
same for me with nextcloud 15 and brave browser
@marcelklehr commented on GitHub (Jan 2, 2019):
Does the web UI have the correct hierarchy? If not this would indicate that things go wrong already when storing the bookmarks.
@tomershvueli commented on GitHub (Jan 2, 2019):
Yep, looks like it! I've also used Floccus successfully before for syncing locally and on the server.
@marcelklehr commented on GitHub (Jan 2, 2019):
The screenshot indicates that the bookmarks were uploaded with the legacy sync method. In order for sync to work, all devices have to use the same sync method.
@tomershvueli commented on GitHub (Jan 2, 2019):
Aha! Yes, that did the trick! Am I now able to sync my local bookmarks with the server using the new sync method?
@marcelklehr commented on GitHub (Jan 2, 2019):
In order to use the new sync method, you should remove the relevant accounts on all devices, then delete all bookmarks in the app and then set up accounts with the new method on all devices again.
I'm currently trying to add some directions to the UI in order to make it clearer what each option does.
@tomershvueli commented on GitHub (Jan 3, 2019):
Awesome! That seems to be working pretty alright for now! Thanks for your work on this, I feel much better now that my bookmarks are actually saved in the proper hierarchy. Cheers!
@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.