Skip to content

[BUG] Bookmark reading incorrectly #1898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task
FlootingDream opened this issue Apr 2, 2025 · 3 comments
Open
1 task

[BUG] Bookmark reading incorrectly #1898

FlootingDream opened this issue Apr 2, 2025 · 3 comments

Comments

@FlootingDream
Copy link

Which version of floccus are you using?

5.4.5

How many bookmarks do you have, roughly?

500

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.

Edge 133.0.3056.0

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)

jianguoyun

Describe the Bug

  1. The newly added bookmark was mistakenly placed in a different folder (i.e. in a different location than the browser bookmark folder)
  2. Bookmark ID value is empty

Expected Behavior

New bookmarks are added to the right location

To Reproduce

The browser adds bookmarks normally and performs normal synchronization behavior

Debug log provided

  • I have provided a debug log file
Copy link

github-actions bot commented Apr 2, 2025

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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general 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!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), 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.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

@marcelklehr
Copy link
Member

Hi @FlootingDream
Can you provide more details? What did you do? what did you expect? What happened instead?

@FlootingDream
Copy link
Author

Hi @FlootingDream Can you provide more details? What did you do? what did you expect? What happened instead?

There is no further information at present. I should be synchronizing normally and there is no synchronization failure prompt.
Finally, delete webdav's bookmark sync file and synchronize it again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants