Bug #6548
showDownloadComponent assumes digital object is located on AtoM server
Status: | Verified | Start date: | 04/02/2014 | ||
---|---|---|---|---|---|
Priority: | Low | Due date: | |||
Assignee: | Dan Gillean | % Done: | 80% | ||
Category: | Digital object | ||||
Target version: | Release 2.1.0 | ||||
Google Code Legacy ID: | Tested version: | 2.0.0, 2.0.1 | |||
Sponsored: | No | Requires documentation: |
Description
The portion of showDownloadComponent that handles constructing a path to be used as the target of the digital object link makes an assumption that all paths are contained on the server on which AtoM is running, and constructs a path via `public_path()`. This breaks URLs for objects imported via URL, since their "path" is actually the URL to their source.
For instance, the generic download thumbnail image would link to "http://www.atom.com/http://www.example.com/foofoo" instead of to "http://example.com/foo".
Related issues
History
#1 Updated by Misty De Meo about 8 years ago
Fixed in dev branch dev/issue-6548-showDownloadComponent
#2 Updated by Misty De Meo about 8 years ago
- Status changed from New to QA/Review
- % Done changed from 0 to 80
#3 Updated by Misty De Meo about 8 years ago
- Target version set to Release 2.1.0
#4 Updated by Dan Gillean almost 8 years ago
- Tested version 2.0.0, 2.0.1 added
I think that we need to fix the regression in #6989 before I can test this...
#5 Updated by Jesús García Crespo over 7 years ago
- Assignee changed from Misty De Meo to Dan Gillean
#6989 waiting for code review, so you'll be able to test this soon!
#6 Updated by Dan Gillean over 7 years ago
- Category set to Digital object
#7 Updated by Dan Gillean about 7 years ago
- Status changed from QA/Review to Verified