mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1723] floccus does not seem to sync folders when synching the bookmark toolbar #1148
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#1148
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 @wolet-ft on GitHub (Sep 20, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1723
Which version of floccus are you using?
5.2.7
How many bookmarks do you have, roughly?
100?
Are you using other means to sync bookmarks in parallel to floccus?
No
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
firefox 130.0.1
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
No response
What kind of WebDAV server are you using? (if relevant)
koofr.net
Describe the Bug
floccus creates folder contained in the bookmark toolbar correctly when initially syncing, but does not consider changes later on. It does not create new folders on a 2nd device and it does not sync within folders after the initial sync.
Expected Behavior
walk through all sub-folders when syncing
To Reproduce
not sure if this is relevant: use webdav for syncing
create a new bookmark folder
check on a synced instance if the folder appears after syncing
floccus-5.2.7-2024-09-20-redacted.log
Debug log provided
@github-actions[bot] commented on GitHub (Sep 20, 2024):
Hello 👋
Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus a few years ago, maintaining it ever since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.
I look forward to working with you on this issue
Cheers 💙
@marcelklehr commented on GitHub (Sep 20, 2024):
hello @wolet-ft
Thank you for uploading the log file. From the log file, it seems that the bookmarks tree on the server and the tree on the client (of the sync run in the file) appear to be the same, so there would be no changes to be propagated in either direction. Is the folder you created empty? if this is the log file from the client where you expected the changes to show up, perhaps you can post the log file of the client where you produced the changes. Note also, that the log file only contains the logs of most recent sync run, so you have to be quick to get the log entries that matter.
@wolet-ft commented on GitHub (Sep 20, 2024):
Hello Marcel,
I am not sure how to get the right log. I only noticed today that the
folder was not synced at all. But maybe you can try reproducing the issue
on your side in the meantime?
BR. - Wolfgang
--- Original Nachricht ---
Von: Marcel Klehr @.***
Datum: 20. September 2024 13:21:14
An: floccusaddon/floccus @.***
CC: wolet-ft @., Mention @.
Betreff: Re: [floccusaddon/floccus] floccus does not seem to sync folders
when synching the bookmark toolbar (Issue #1723)
@marcelklehr commented on GitHub (Sep 20, 2024):
I cannot reproduce this offhand, so I think it's likely a more complex issue than your description attests to :/
My Steps:
Firefox
Chrome
@github-actions[bot] commented on GitHub (Dec 28, 2024):
Hello 👋
This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues
have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule
it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment
or remove the label to avoid it getting closed.
Cheers 💙
@github-actions[bot] commented on GitHub (Jan 2, 2025):
This issue was closed because it has been stalled for 5 days with no activity.
@github-actions[bot] commented on GitHub (Jan 3, 2026):
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.