Originally reported on Google Code with ID 3916
What archive revision are you testing on? (See the version label in
the footer, for example v0.8.13.8.)
If appropriate, enter the URL of a page where the problem can be seen:
What steps will reproduce the problem?
1. Go to the Manage Items page of a collection you own or moderate (collection doesn't
have to be moderated)
2. Find a work you'd like to kick out of the collection
3. Choose anything from the dropdown menu other than what it's currently set to
4. Tick the box next to "Remove"
5. Click "Submit"
What is the expected output? What do you see instead?
Expect the work to be removed from your collection. Instead get Error 500 and the
work's status is unchanged.
Please use labels and text to provide additional information.
This seems most likely to happen in the case of wanting to get rid of a work, and choosing
"Rejected" and "Remove" at once, but changing the setting on the dropdown to anything
it's not currently set to (including blank) will trigger the issue.
*Labels added*: Keep-SJ
Regarding a 500 error encountered in AO3-5584:
ticking instant [19:04]
They're likely frozen because remove= calls destroy, which freezes the hash.
(The attributes hash, that is.)
I think you get the same kind of error in https://otwarchive.atlassian.net/browse/AO3-3908
This is addressed in , I believe.
Work was removed from the collection when I simultaneously set it to Rejected and ticked Remove, yay! (Definitely removed – it wasn’t listed on the Rejected page.)
I tried a bunch of different ways. I never got an error, always got what should be expected. Whatever I put in dropdown, if I checked remove it was completely removed.