Content
View differences
Updated by Eric Schubert almost 4 years ago
### Steps to reproduce
1. link a folder to an WP
2. in the files view of the WP click the download button for that file-link
### What is the buggy behavior?
`{"_type":"Error","errorIdentifier":"urn:openproject-org:api:v3:errors:InternalServerError","message":"An internal error has occurred. 400 Bad Request"}`
### What is the expected behavior?
I can think of two solutions:
1. don't display the download button for folders (could be determined by the mimetype returned by the fileInfo API) -> **UPDATE: this is the preferred result**
2. ~~present a ZIP file of the folder content, similar to the public link "Download all files" button~~ (that would not work because even getting the token does not work for folders. response: HTTP 400 `{"ocs":{"meta":{"status":"failure","statuscode":400,"message":"Direct download only works for files"},"data":[]}}`
1. link a folder to an WP
2. in the files view of the WP click the download button for that file-link
### What is the buggy behavior?
`{"_type":"Error","errorIdentifier":"urn:openproject-org:api:v3:errors:InternalServerError","message":"An internal error has occurred. 400 Bad Request"}`
### What is the expected behavior?
I can think of two solutions:
1. don't display the download button for folders (could be determined by the mimetype returned by the fileInfo API) -> **UPDATE: this is the preferred result**
2. ~~present a ZIP file of the folder content, similar to the public link "Download all files" button~~ (that would not work because even getting the token does not work for folders. response: HTTP 400 `{"ocs":{"meta":{"status":"failure","statuscode":400,"message":"Direct download only works for files"},"data":[]}}`