mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #292] floccus + kiwi + subfolders #266
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#266
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 @humarf on GitHub (May 14, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/292
I read that kiwi as first mobile browser will support the floccus plugin. That's why I tried kiwi + floccus on my android tablet. Installation and set up went fine. Unfortunately all bookmarks are synced to the chosen sync folder in kiwi without recognizing any subfolders. It's a flat list now. Is this as expected? If not how to get subfolder replicated, please?
Software versions
@marcelklehr commented on GitHub (May 17, 2019):
Hey,
This is not as expected. Are you aware that you are using a beta version of floccus? Have you tried the latest stable release?
@humarf commented on GitHub (May 18, 2019):
Hello,
I am aware of that. First I tried stable release from chrome webshop. There was the same problem. Then I thought since mobile sync is brand new it only works with latest beta version. But I got the same result.
Is there any debug information that I can provide to find out what's wrong?
@marcelklehr commented on GitHub (May 18, 2019):
You can provide the debug logs. There's a link in the bottom right corner of the floccus panel. Out of a hunch: Which sync method do you use on your desktop?
@humarf commented on GitHub (May 19, 2019):
I am using the "with folders" sync methond.
I had a look at the log file of floccus. I think it's about undefined parent id but on server side. Here is one example:
COMPARE { localItem: - #143[Amazon.de: Günstige Preise für Elektronik & Foto, Filme, Musik, Bücher, Games, Spielzeug & mehr](https://www.amazon.de) parentId: 140, cacheItem: - #143[Amazon.de: Günstige Preise für Elektronik & Foto, Filme, Musik, Bücher, Games, Spielzeug & mehr](https://www.amazon.de) parentId: 140, serverItem: - #6;-1[Amazon.de: Günstige Preise für Elektronik & Foto, Filme, Musik, Bücher, Games, Spielzeug & mehr](https://www.amazon.de) parentId: -1 } Bookmark unchangedComparing this to the log from desktop version parent ID is there:
COMPARE { localItem: - #124[Amazon.de: Günstige Preise für Elektronik & Foto, Filme, Musik, Bücher, Games, Spielzeug & mehr](https://www.amazon.de) parentId: 13, cacheItem: - #124[Amazon.de: Günstige Preise für Elektronik & Foto, Filme, Musik, Bücher, Games, Spielzeug & mehr](https://www.amazon.de) parentId: 13, serverItem: - #6;/Shopping[Amazon.de: Günstige Preise für Elektronik & Foto, Filme, Musik, Bücher, Games, Spielzeug & mehr](https://www.amazon.de) parentId: /Shopping } Bookmark unchanged@marcelklehr commented on GitHub (May 19, 2019):
The log file from your desktop would indicate that you are not using the folder sync on your desktop, but the legacy sync method, which creates folders as tags on the server. I recommend changing either client to match the other and you'll be fine. ;)
@marcelklehr commented on GitHub (May 19, 2019):
(Also see: https://github.com/marcelklehr/floccus#switching-from-tag-based-to-folder-based-syncing)
@humarf commented on GitHub (May 20, 2019):
That was it. I had to delete the desktop account and recreate it.
Thanks a lot.
@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.