mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #144] Folder structure is not preserved. #133
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#133
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 @arnauldb on GitHub (Aug 16, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/144
Hello,
I finally succeeded in synchronizing my whole bookmark bar. But there is no folder structure. Is it possible to have the folders with the bookmarks inside? Currently, I have all the bookmarks but no folder.
Thank you.
@bernd-wechner commented on GitHub (Aug 16, 2018):
Alas you're not clear on what settings you're using. So no-one will be able to say for sure why you see what you see. Nor is it clear what you mean. But I can offer one small experience. That is, if you're syncing to the NextCloud Bookmarks app, it does't support folders alas, though I filed an issue with it to ask for that. And so floccus uses the tag with its own syntax to record the folder structure. It's a compromise and not real nice. But they are maintained with folders on the browser.
@arnauldb commented on GitHub (Aug 19, 2018):
Ok, thank you, that is what I wanted to know.
@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.