mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 06:25:54 +03:00
[GH-ISSUE #681] Update will delete all archive data #344
Labels
No labels
component:backend
component:builds
component:builds
component:extension
component:frontend
component:readability
database
database:mysql
database:postgres
database:sqlite
feature:ebooks
github_actions
good first issue
hacktoberfest
note:duplicate?
note:fixed?
note:out-of-scope?
os:windows
priority:high
priority:low
pull-request
resolution:as-intended
resolution:cant-reproduce
resolution:duplicate
resolution:fixed
resolution:wontfix
tag:TBD
tag:big-task
tag:help-wanted
tag:huge-data
tag:meta
tag:more-info
tag:next
tag:no-stale
tag:requires-migrations
tag:research
tag:security 🛡️
tag:stale
tag:waiting-for-assignee
type:bug
type:documentation
type:enhancement
type:meta
type:ux
user:cli
user:web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shiori#344
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 @rmayergfx on GitHub (Jul 27, 2023).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/681
Data
Describe the bug / actual behavior
Updating Archiv will delete all information

Expected behavior
unable to update archive without loosing date
To Reproduce
Steps to reproduce the behavior:
Select any older Bookmark
Update
@Monirzadeh commented on GitHub (Jul 27, 2023):
Source URL is still exist?
Do you keep something like #634 in mind, or you need versioning system for archive while updating them?
@rmayergfx commented on GitHub (Jul 28, 2023):
Still available, see https://github.com/go-shiori/shiori/issues/670
@fmartingr commented on GitHub (Jul 29, 2023):
This seems a duplicate of #634. Can you confirm @rmayergfx?
@stale[bot] commented on GitHub (Sep 3, 2023):
This issue has been automatically marked as stale because it has not had any activity for quite some time.
It will be closed if no further activity occurs.
Thank you for your contributions.
@Monirzadeh commented on GitHub (Sep 3, 2023):
@rmayergfx is it fix with last commit on master?
@stale[bot] commented on GitHub (Oct 3, 2023):
This issue has been automatically marked as stale because it has not had any activity for quite some time.
It will be closed if no further activity occurs.
Thank you for your contributions.