[MNT-14924] Upload new version with different file (mime) type does not update properties or .extension Created: 02-Oct-15 Updated: 02-May-18 Resolved: 04-May-16
|Project:||Service Packs and Hot Fixes|
|Reporter:||Will Taylor [X] (Inactive)||Assignee:||Closed Bugs (Inactive)|
|Remaining Estimate:||0 minutes|
|Time Spent:||1 week, 2 days, 5 hours, 7 minutes|
|Original Estimate:||Not Specified|
|Attachments:||New File Version Upload Work Flow.png uploadNewVersion.PNG|
QA, 00138590, 00489538
As an end user I want Alfresco to handle changes in filenames and Mimetypes gracefully so that when a new version is created that has a different file extension and/or a different Mimetype the transforming does not fail and downloads by other users can be opened easily.
|Comment by Derek Hulley [X] (Inactive) [ 05-Oct-15 ]|
I am presuming that the interface used is Share.
I would suggest that we flag this up at the UI (at most) but we cannot prevent a low-level (repo API) binary upload from pushing data in and nor can we magically change the filename.
|Comment by Will Taylor [X] (Inactive) [ 05-Oct-15 ]|
With the upload of a different filetype as a version, other than the mime type for transforms on the server, the extension is used on download for the clients to determine which application to open the file with.
Can the Share product owner clarify what should be done in this scenario?
|Comment by John Knowles [X] (Inactive) [ 17-Dec-15 ]|
MIME Type not updating is also described in
In the case of the file extension, and even the file name, not updating we will have to enhance the upload new version mechanism to ask the user to confirm what they want to do:
Will Taylor [X] this feels like an important enhancement to do due to customers reporting the problem, and the resulting problems that end users can get themselves into - can sustaining do this work?