Closed wragge closed 1 week ago
This one looks like an error with us trying to render the JSON to return after the deletion is done, I think a regression that was introduced when we added @reverse
to the API.
This should be fixed in b192c2d3cb07fd84ea03b58a5b9b781b0b87597e. Thanks, @wragge, for this excellent bug report!
Omeka-S version: 4.1.1
When I try to delete an item using the REST API I get a 500 error, even though the item is deleted as expected.
Here's a minimal example in Python that creates a new item, deletes it, then checks to see if it has really been deleted:
Running this code produces the following output:
The error and traceback in the Omeka logs is: