[MGNLUI-4202] Make Zip upload behavior configurable Created: 14/Apr/17  Updated: 22/Sep/21  Resolved: 09/May/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5.4

Type: Improvement Priority: Major
Reporter: Ondrej Chytil Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 1
Labels: support
Remaining Estimate: 0d
Time Spent: 6d 1.5h
Original Estimate: 5d

Attachments: PNG File asset-upload-variations.png    
Issue Links:
Cloners
is cloned by MGNLUI-4206 Make Zip upload behavior configurable... Closed
Relates
relates to MGNLDAM-896 Upload Zip archive - no Location option Closed
causality
is causing MGNLUI-5541 Encoding is not properly considered w... Open
is causing MGNLUI-5292 Encoding is not properly considered w... Closed
dependency
relation
is related to MGNLUI-3973 After zip import, location points to ... Closed
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)
Release notes required:
Yes
Date of First Response:
Sprint: Saigon 93, Saigon 94, Saigon 95
Story Points: 8

 Description   

When uploading a zip file with assets to the Dam app a folder is created using the name of the zip file. Under this folder all the assets of the zip file are uploaded.
Until MGNLUI-3973 the files were extracted directly to the selected location (or root). This should be configurable, ideally user should be able to select the desired behavior in the upload dialog.



 Comments   
Comment by Mohan Sundararajan [ 17/Apr/17 ]

Hi Team,
Our production env is affected by this issue. Could you please share the expected fix release date for this issue?

Thanks,
Mohan S

Comment by Mikaël Geljić [ 09/May/17 ]

Closing with one minor remark I observed:

Extracting a zip file "in place" where an asset with same-name already exists: this unexpectedly overrides the binary node, but not the asset properties. This does not affect extracting within a new folder (a new folder with unique suffix may be created).

This issue was likely present as well before 5.4.9; so it is not critical and may be addressed in a follow-up ticket.
We should probably ask for confirmation when there are naming collisions.

Generated at Mon Feb 12 09:14:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.