Actions
Bug #16123
openBrowsing trash produces spurious errors
Story points:
-
Release:
Release relationship:
Auto
Description
- Create a project
- Add a collection
- Trash the project
- Go to the trash
- Double click on the project
- You'll get an error, but you'll be able to browse it and see the collection
- Double click on the collection
- You'll get more errors, but still be able to browse it
I suspect that browsing still works because despite request failures, the components are rendered from the internal resource cache (not directly from the request response).
Browsing should work with include_trash=true
so queries need to be aware that the item is in the trash and add the flag.
Updated by Peter Amstutz almost 5 years ago
- Target version changed from 2020-02-26 Sprint to 2020-03-11 Sprint
Updated by Peter Amstutz almost 5 years ago
- Target version changed from 2020-03-11 Sprint to 2020-03-25 Sprint
Updated by Peter Amstutz almost 5 years ago
- Release set to 31
- Target version deleted (
2020-03-25 Sprint)
Actions