mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #251] Behavior: Old links are updated even when ONLY_NEW=False #176
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#176
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 @Pofilo on GitHub (Jul 1, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/251
Describe the bug
I'm using a file where I add links I want to archive. When using the
ONLY_NEW = Trueoption, my links still get updated. I think the behavior of this option is broken.Steps to reproduce
ONLY_NEW = Truewith an already archived linkSoftware versions
not relevant
Discuss the option
Do we agree my link should not be updated ?
If yes, I can push immediately a merge request to fix it.
It is in
index.pyin the functionload_links_index(). This function returnsnew_linksbut if a link ofimport_pathalready exists, it will still add it innew_links.My fix: check if a link is in
existing_linksbefore adding it tonew_links.If we do agree about this behavior, I will create a PR right now.
Thanks.
@pirate commented on GitHub (Jul 5, 2019):
I think this is fixed already in the upcoming v0.4 release, but I'll keep this open double check after I finish the pending security work.
Follow here for updates: https://github.com/pirate/ArchiveBox/pull/207#issuecomment-494107553
@Pofilo commented on GitHub (Jul 6, 2019):
Oh, okay, thanks for the answer, I'll close after the release then.
@pirate commented on GitHub (Jul 24, 2020):
I believe this is fixed now.
If you still see this on the latest django branch comment back here and I'll reopen the issue.