mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #694] Bug: Adding tags to an existing snapshot throws a server error (500) #435
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#435
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 @erob8 on GitHub (Apr 7, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/694
Describe the bug
Adding tags to an existing snapshot throws a server error (500)
Steps to reproduce
Screenshots or log output
docker-compose logs:
The request payload I'm sending which shows
&tag=which is the source of the issue I imagine. Opening the index.sqlite3 file and examining the core_snapshot table shows a non-null id as expected.csrfmiddlewaretoken=k7UGcaLI0w0vRBgfWrDjOjfIkTcxwPOJsCVZMEV0AnUzW5r5vqyMEpc7KQq4CBIo&action=add_tag&select_across=0&tag=&index=0&_selected_action=45d3506e-8b69-4ab8-af5c-dafb198d8ed0ArchiveBox version
@pirate commented on GitHub (Apr 7, 2021):
I just touched the JS recently which handles sending the tag IDs so it's probably broken from that, will investigate, thanks.
@pirate commented on GitHub (Apr 10, 2021):
Fixed in
a9986f1. Try the latest v0.6 build and comment back here if you have any issues and I'll reopen it.