Bug #12760
Master objects with lowercase jpg extension are shrunk to 225px width when using multi-uploader
| Status: | Verified | Start date: | 01/29/2019 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Digital object | |||
| Target version: | Release 2.5.0 | |||
| Google Code Legacy ID: | Tested version: | 2.5 | ||
| Sponsored: | No | Requires documentation: |
Description
- Find a top level description
- Use the "Import digital objects" option (AKA the multi-uploader) to attach the images appended to this ticket
Resulting error
- Files with .png or .JPG extensions are fine
- Files uploaded with a lower-case .jpg extension have the master object (and all derivatives) shrunk to a max 225px width
Expected result
- Master digital object is not altered during the upload process
History
#2 Updated by Steve Breker 7 months ago
- File Screen Shot 2.png added
- File Screen Shot 1.png added
This bug occurs during the initial multi-upload process, before the "Import" button is pressed when the small derivative is created for the multi-upload screen.
I have attached two screenshots - the two images are the same with the exception of the case of the extension - jpg vs JPG (see first screenshot). The second screen shot shows that the lower case reference copy is NOT uploaded to the /uploads/tmp directory - only the derivative for that image. I think this is the source of the issue - this thumbnail then becomes the reference copy once the "Import" button is pressed.
#3 Updated by Mike Cantelon 5 months ago
- Status changed from New to Code Review
PR for CR: https://github.com/artefactual/atom/pull/869
#5 Updated by Evelyn McLellan 4 months ago
- Status changed from Feedback to Verified
Verified on http://atom25.centos7.qa.accesstomemory.net and atom25.1804.qa.accesstomemory.net.
#6 Updated by Dan Gillean 4 months ago
- Target version set to Release 2.5.0
#7 Updated by Dan Gillean 4 months ago
- Category set to Digital object