mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #315] Floccus does not remember saved options for the account. #279
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#279
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 @bhlevca on GitHub (Jun 14, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/315
Software versions
Steps to reproduce
Expected outcome
The checkmark and the 60 min sync interval are not there
Actual outcome
The sync interval is still empty and the checkmark is not selected
Debug log
unavailable
@marcelklehr commented on GitHub (Jun 16, 2019):
I can't replicate this. Note that the "trigger sync from scratch" checkbox always clears itself when saving, as that information is used directly.
@bhlevca commented on GitHub (Jun 16, 2019):
I understand, I did not know about the "trigger sync from scratch" behaviour. The other one I cannot reproduce either. I may have been something transient.
On another note, I have varied succes with synchronisation. Sometimes take a long long time and seems stuck there, sometimes it fails. Now that I think about it is possible that my settings with nextcloud server being behind a difficult to configure HAProxy setup may be the problem for me.
@marcelklehr commented on GitHub (Jun 16, 2019):
If it helps, I've copied a guide below on how to check the live debug log.
Firefox
about:debuggingdebugbutton next to floccus entryforce Syncfor the account of your choice.Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "force Syncfor the account of your choice@bhlevca commented on GitHub (Jun 16, 2019):
It worked, but it always worked if I delete the xbel file and the lock. It took 17 sec from almost 4000 bookmarks. That's a great improvement!!!
Here are a few observations:
The problem is that subsequent syncs take much longer (minutes).
Also, creating the tree structure from the xbel file in Firefox browser takes long minutes.
The tree created in Firefox had the order of folders and bookmarks reversed, the last version 3.3.1 is OK
Also, often Firefox seems to "forget" to remove the lock file, after a firefox initial sync :
E023: Unable to clear lock file, consider deleting bookmarks.xbel.lock manually.Sometimes before the "/Bookmars Bar" selected directory a @Nextcloud string is appended, but I still have to figure out when that happens.
In general 3.3.1 is much improved and floccus can finally be used as a main sync tool. It woerk now even in kiwi browser.
Below is the log from the successful initial run to create a new xbel file on the server:
@tessus commented on GitHub (Jun 17, 2019):
I just wanted to create a new issue, but found this one. I'm not 100% sure, if they are related, so if they are not, please let me know and I open a new one.
When I uncheck the
Enabledoption for a sync item (so that it isn't synced automatically), and restart the browser, it's checked again.@marcelklehr commented on GitHub (Jun 19, 2019):
@tessus I think that's probably unrelated (and I cannot reproduce this at the moment) -- a new issue would be good :)
@tessus commented on GitHub (Jun 19, 2019):
@marcelklehr ok, last time I restarted the brower, the account was still disabled. maybe this only happened when the add-on was updated. I will open a new issue, if it happens again.
@marcelklehr commented on GitHub (Jun 19, 2019):
I can't reproduce this. With 5000 bookmarks an XBEL sync run is quite fast for me.
This can happen when a different floccus instance is syncing at the same time.
Mmmh. That sounds weird.
@bhlevca commented on GitHub (Jun 19, 2019):
Anyway, this version is good, it is stable, fast and I can finally rely only on it and I can finally delete eversync from my browsers. Thanks
@marcelklehr commented on GitHub (Jun 20, 2019):
Cool. Thanks for your feedback. Feel free to open a new issue if something new comes up :)
@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.