mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #446] Versioning #335
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#335
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 @dsiminiuk on GitHub (Feb 3, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/446
Is your feature request related to a problem? Please describe.
No backups exist I am aware of.
Describe the solution you'd like
If your bookmarks are lost for any reason there is no way to go back to a previous version. I would like the plugin to rename the existing file with a date/time stamp on the WebDAV share and save that last n (configurable) files.
Describe alternatives you've considered
If the existing file on the WebDAV share can be renamed and then deleted on a push operation, the deleted file would show up in the NextCloud recycle bin where it could be recovered. You could change the plugin to overwrite local, restore the file, rename it back, and sync. That would restore bookmarks from a catastrophic loss.
Additional context
Maybe this can be done already but I don't see how.
@leggewie commented on GitHub (May 1, 2020):
I don't know, this sounds a bit like bloat and feature creep. Proper Backup solutions are already out there.
If you are using NextCloud for the backend then you can already very easily restore any previous version in the web front-end.
@dsiminiuk commented on GitHub (May 1, 2020):
Yup, I see the old/previous versions now.
@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.