mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #461] v4.0.2 legacy account type is deprecated... please switch to the new nextcloud sync method #342
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#342
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 @sunjam on GitHub (Mar 3, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/461
Hi, Firefox automatically upgraded Floccus to 4.0.2 and now I'm seeing
Last synchronized: 3 minutes ago Warning! This legacy account type is deprecated and will soon be removed. Please switch to the new nextcloud sync method. Improved performance and accuracy await you.I'm unsure on what switching to the new sync engine still entails, but I'm happy to do so. Just want to confirm how to stop using the deprecated method. I've been running Floccus for a long time... only options I've filled out are url/user/pw/root directory for sync.
I checked through documentation and didn't see exact steps for transitioning to the new method. Thanks for the major update!
@marcelklehr commented on GitHub (Mar 3, 2020):
Hey @sunjam 👋
The steps for the migration are documented over here: https://github.com/marcelklehr/floccus#switching-from-tag-based-to-folder-based-syncing
@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.