mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1720] Syncing Problems when changing the titles of bookmarks in the browser (at least Firefox) #1146
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#1146
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 @elmanuke on GitHub (Sep 15, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1720
Which version of floccus are you using?
v5.2.7
How many bookmarks do you have, roughly?
50
Are you using other means to sync bookmarks in parallel to floccus?
No
Sync method
Nextcloud Bookmarks
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 (64-Bit)
Which version of Nextcloud Bookmarks are you using? (if relevant)
v14.2.5
Which version of Nextcloud? (if relevant)
v29.0.5
What kind of WebDAV server are you using? (if relevant)
I do not use a WebDAV server for syncing
Describe the Bug
When I do changes to my bookmarks in the Firefox Browser, i.e. changing the title, I have problems uploading these changes to nextcloud. The floccus addon shows the error "E018: Couldn't authenticate with the server.", sometimes even several times:
When I download the bookmarks from the remote server, my local title changes are overwritten (just as expected).
However, when adding or removing bookmarks locally within Firefox, the described syncing problem does not occur. It is just related to title changes of existing bookmarks.
Expected Behavior
I would expect the changes to be uploaded to the remote Nextcloud server
To Reproduce
Debug log provided
@github-actions[bot] commented on GitHub (Sep 15, 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 17, 2024):
Hello @elmanuke
This is a strange one. Can you check the nextcloud log for errors? Is it possible that these are bookmarks that you don't have write access in Nextcloud Bookmarks, because they were shared with you by someone else?
@elmanuke commented on GitHub (Sep 18, 2024):
Hi @marcelklehr,
thanks for answering so quickly! I use nextcloud with the hetzner storageshare and I haven't found out how to get the logs of the nextcloud instance..
Also the write access should not be a problem..
But I tried a bit around and found out, that for some reason it does only affect some of my bookmarks. And these are the bookmarks, that are marked as duplicates in the nextcloud bookmarks app. However, I do not know why these bookmarks are labled as duplicates. They are only in one folder and actually only exist once, just like all the other bookmarks.
Even exporting all bookmarks as an html file, deleting everything in nextcloud bookmarks and importing them again did not help. After uploading via a sync with floccus, I again was not able to change the title of these 38 bookmarks within firefox afterwards.
Do you have an idea what could be the reason for the wrong duplicates and why that creates the weird title change error described above?
@marcelklehr commented on GitHub (Sep 19, 2024):
This may have to do with the new trash bin feature in Nextcloud Bookmarks, could you try clearing the trash bin in Nextcloud Bookmarks?
@elmanuke commented on GitHub (Sep 20, 2024):
I tried it, but it did not help. The weird thing is that, even after deleting all bookmarks in Nextcloud and uploading them again, I still have exactly the same behaviour.
However, I found another way how to get rid of the wrong duplicates: I changed the titles of all wrong duplicates in Nextcloud, downloaded them via floccus, changed the titles back in Firefox and uploaded them again via floccus. Now I got rid of that strange behaviour, but it's a lot of manual and individual bookmark debugging..
@marcelklehr commented on GitHub (Sep 20, 2024):
So, the steps to reproduce would be
Would this be correct? I'm going to add a test case for this.
@elmanuke commented on GitHub (Sep 20, 2024):
Ah not really, I did not have any duplicate bookmarks in two separate folders, Nextcloud bookmarks for some reason just thought, that there were duplicates. But I have no idea why the bookmarks were interpreted as duplicates.
@marcelklehr commented on GitHub (Sep 20, 2024):
Mmmh, the only reason for duplicates being detected where there are none, to my knowledge, could be the trash bin :/ But you said you'd cleared that before trying again.
@elmanuke commented on GitHub (Sep 20, 2024):
I imported the same bookmarks file (html export file from firefox) hat caused the problem, in another nextcloud profile. There I did not see the wrong duplicate issue. So it must have been some kind of bookmarks stored in the background. Maybe clearing the trashbin does not work properly?
@marcelklehr commented on GitHub (Sep 23, 2024):
It's possible that your bookmarks installation has some corrupt bookmarks that cause trouble :/ Can you try updating to v14.2.6 of Nextcloud Bookmarks to see if that fixes things?
@github-actions[bot] commented on GitHub (Dec 23, 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 (Dec 29, 2024):
This issue was closed because it has been stalled for 5 days with no activity.
@github-actions[bot] commented on GitHub (Dec 30, 2025):
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.