[MGNLDAM-536] Files with whitespace in filename are not properly escaped when using upload action Created: 20/Jan/15  Updated: 01/Jul/15  Resolved: 04/Mar/15

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: 2.0.6
Fix Version/s: 2.0.8

Type: Bug Priority: Critical
Reporter: zzz_Philipp Güttler Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Issue Links:
Relates
causality
is causing MGNLIMG-163 Imaging always strips extension from ... Closed
duplicate
is duplicated by MGNLDAM-562 DirectUploadAction doesn't check for ... Closed
relation
is related to MGNLDAM-483 ImportAssetZipCommand chooses node na... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When uploading a file with whitespace in the filename within the assets choose dialog ('upload', 'upload & edit'), an asset node is created without escaping the whitespace correctly. This leads in some browsers to broken urls to assets :
/.imaging/stk/test/variation_400/dam/folder/filenameWith Whitespace.jpg/jcr:content/filenameWith%20Whitespace.jpg

In Magnolia 5.2 projects with dam-module version 1.2.6 this bug is not present.


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