mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #824] Bookmark file not create on WebDAV server #527
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#527
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 @truegreyhound on GitHub (Feb 7, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/824
Describe the bug
After a few tests with Floccus and LoFloccus, I decided to test Floccus in conjunction with a WebDAV server.
Floccus reports a successful synchronization after an E109 error, but no xbel file is generated.
After the synchronization, all entries in the bookmarks bar are deleted, the entries in the bookmarks menu were not synchronized according to the log
To Reproduce
Steps to reproduce the behavior:
Expected behavior
a xbel file on the WebDAV server, but nothing
Then I copied an xbel file from the LoFloccus test to the WebDAV server and synchronized it again. This file has then been changed. It seems like a new file cannot be created. In the screenshot this can be seen as bookmarks-all.xbel-test1.
As I understand it, clicking on "new synchronization" clears the cache and the complete list of bookmarks should be in the xbel file. However, the "remove" indicates that the cache was not empty. How can I control the clearing of the cache?
Desktop
(please complete the following information)
Server
debian buster, with Apache 2.4
Debug log
from FireFox
from WebDAV server
Additional context
Add any other context about the problem here.
@github-actions[bot] commented on GitHub (Feb 7, 2021):
Hi @truegreyhound! This issue is being automatically closed because it does not follow the issue template.
@marcelklehr commented on GitHub (Feb 7, 2021):
That bot is a bit overzealous apparently...
@bhlevca commented on GitHub (Feb 8, 2021):
Marcel, I have the same issue. The Webdav solution does not work at all. It is basically stuck and does not advance at all for hours and even days. I think that there is a major design problem with the file lock which may work for 2 devices but not for more as it will be in a racing condition that only one lock cannot solve.
I tried to go back to the Bookmarks App, but since v 4.4.10 nothing works. My Bookmark app hosted on a Raspberry Pi 4 is useless as it is very slow and I have the latest nextcloud version as of today.
I made a contribution as a sponsor to help with the development, but I need a functional app to store my bookmarks and I will stop using it for a while until things get better. The issue appears on all the browsers.
I will use the private Brave sync which has synced all my 3000 bookmarks in less then 30 seconds. There must be a way that floccus can be made more reliable and fast. If money can help I will contribute more, but at this time floccus is at its worst that has ever been, at least for me and I tried to erase bookmarks , and do it form scratch but nothing helped.
@marcelklehr commented on GitHub (Feb 8, 2021):
Thanks for your feedback, folks! I'm sorry for your troubles. This has been due to a stale cache, indeed.
It seems this has been reported in #814 #819 and #650, but I couldn't reproduce it then. The hint with the sync from scratch was the clue.
@bhlevca Thank you for your donation! Initial sync with the bookmarks app is usually slower than normal, but subsequent syncs should be quite fast.
@truegreyhound commented on GitHub (Feb 8, 2021):
I did a new test today.
First a new initial synchronization without an existing xbel file. This ends with the following error:
Then I created an empty xbel file in the WebDAV directory via WinSCP:
and then performed an initial synchronization again:
the xbel file has now been updated.
The problem is therefore that it does not appear to be checked whether an xbel file already exists and that it may have to be created again.
@marcelklehr commented on GitHub (Feb 9, 2021):
@truegreyhound The webdav adapter is extensively unit-tested with Nextcloud where this request works as intended. I'm happy to change code in floccus to make this work, but as it stands it seems like this would be a problem with your server configuration, as PUT requests should create a new file if it doesn't exist.
@truegreyhound commented on GitHub (Feb 9, 2021):
I had successfully tested my WebDAV installation with various clients.
Today I extended the logging on the WebDAV server and found the following message:
"Negotiation: discovered file (s) matching request: /var/www/webdav/floccus/bookmarks-all.xbel (None could be negotiated)"
After deactivating MultiViews, Floccus created the file successfully.
Here is my current configuration:
Do you have any recommendations on how WebDAV should be configured for floccus with Apache 2.4.
@bhlevca commented on GitHub (Feb 10, 2021):
@marcelklehr Unfortunately, there is something wrong somewhere, the synchronization is not working at all. In Firefox I monitored with the task manager and floccus has barely any activity. It may be my nextcloud server, which resides on a raspberry pi 4? However, the file synchronisation works just fine and floccus was performing well before with the same configuration. I tried with WebDAV and Bookmarks app none of them works, not in chrome nor in firefox, and I don't know why. It just sits there and does nothing. I removed the bookmarks from the browser and I tried to sync from the App, but it did not work either. I will put it to rest for a while as I don't have the time to investigate now.
For the next while, I will use for the sync provided by the browser for now even if this means that Firefox and Brave/Chrome will not have a common repository.
@marcelklehr commented on GitHub (Feb 10, 2021):
@truegreyhound I don't have much experience in hosting a WebDAV server. Would you mind adding your config to the wiki, so other people can benefit? :)
@deragon commented on GitHub (May 1, 2021):
@marcelklehr, following is my config for a Webdav. The problem is specific to Floccus. If I use Nautilus to copy/create file on that Webdav, all works fine. I am a first time users, started today, thus never got Floccus working yet.
@deragon commented on GitHub (May 1, 2021):
Found the problem, at least for me. I added
Options -MultiViewsto the block. Following, the full configuration. Upload worked, but download got HTML parse error. Investigating...@marcelklehr commented on GitHub (May 3, 2021):
Debugging network traffic from the addon may help:
Firefox
about:debuggingdebugbutton next to floccus entrysync nowfor the account of your choice.Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "sync nowfor the account of your choice@marcelklehr commented on GitHub (May 3, 2021):
If you get this to work, it'd be cool to have a tutorial or at least your config in the wiki. :)
@marcelklehr commented on GitHub (Aug 13, 2021):
@deragon Any news?
@deragon commented on GitHub (Aug 14, 2021):
I got it to work somewhere in may. Currently I am on vacation so I cannot look this up. But when I return, I will check to see what I have done and report here. Sorry for having not responded earlier.
@marcelklehr commented on GitHub (Nov 2, 2021):
bump @deragon
@deragon commented on GitHub (Nov 13, 2021):
Very sorry for the very late response. Following, the configuration that works 100% for me on my Apache 2.4.41-4ubuntu3.6 HTTP server. Now everything works fine.
@github-actions[bot] commented on GitHub (Mar 20, 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.