[MGNLDAM-589] Incoherence on uploading: Upload asset does not store suffix in Node name, upload the same file a zip (zip upload) creates the node with the suffix Created: 28/May/15  Updated: 27/Oct/16  Resolved: 07/Aug/15

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: 2.0.7
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Christian Ringele Assignee: Trang Truong
Resolution: Cannot Reproduce Votes: 0
Labels: support
Remaining Estimate: 1d 2.5h
Time Spent: 2d 5.5h
Original Estimate: 4d

Attachments: PNG File The Two URLs.png     PNG File UploadAsset.png    
Issue Links:
Relates
relates to MGNLIMG-163 Imaging always strips extension from ... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Sprint 5 (Basel)
Story Points: 8

 Description   

In the linked support case SUPPORT-4669 there is a nice screen cast showing this behavior.
I can confirm the same behavior.

reproduce:
1. Upload an image directly as assets. -> Node name does not contain the suffix
2. Zip the same image and do a "Zip Upload" of it. -> Node name does contain the suffix

The behavior should be aligned for both cases.

I'm not sure which one of the cases is the goal for the future:

  • Having the suffix in the node name
  • Not having the suffix in the node name

I'm in favor of having the suffix in the out of a simple reason:
I've seen in many projects, that they need to provide files with the same names but different extensions, for example:
A movie file and its cover file (.mov & .jpg) must usually have the same name.
Or different images in different qualities/formats:
image.tiff (the original high quality, could also be .bmp)
image.jpg (one with no alpha channel
image.png (one with alpha channel)

As long the suffix is not in the file name this can't be achieved.

I'm aware that this impacts the link creation.
If you have the suffix in the file name then the link creation has two times the suffix in it: once form the node name, once form the file extension property of the asset, see print screen "The Two URLs.png".
So the cases should be aligned and the link creation should take account of having the suffix in the node name (and then ignoring the file extension within the asset), or something alike.



 Comments   
Comment by Sang Ngo Huu [ 04/Aug/15 ]

Tried to reproduce as description, but seem the issue has been fixed. Please see the screen capture file https://dl.dropboxusercontent.com/u/36681201/Reproduce_MGNLDAM-589.swf
I used Dropbox because of limited of Jira file uploader.

Please reopen and let me know if I have any mistakes.

Thanks.

Comment by Trang Truong [ 07/Aug/15 ]

I've uploaded successful an asset with the node name included suffix. Here are steps that I reproduced

  1. Upload TestNG-Framework.jpeg file to demo-project node. It stored a new node name /demo-project/TestNG-Framework.jpeg
  2. Zip that file and upload zip, it overrided the above file.
  3. Add one more file to zip archive with the same name but different extension TestNG-Framework.png to demo-project node. It show 2 nodes as the attachment UploadAsset.png.

It's correct behavior that we expected.

Generated at Mon Feb 12 05:01:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.