[MGNLDAM-788] Special characters in Zip-Upload are not stored correctly Created: 16/Apr/19  Updated: 02/Dec/19  Resolved: 25/Jul/19

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

Type: Bug Priority: Neutral
Reporter: Kathrin Kaufleitner Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2019-04-16-14-59-15-974.png     PNG File image-2019-04-16-15-02-20-185.png     PNG File image-2019-04-16-15-03-46-478.png     Zip Archive testfolder with special char.zip    
Issue Links:
Relates
relates to MGNLUI-5312 Extraction folder may be created with... Closed
causality
caused by MGNLUI-5541 Encoding is not properly considered w... Open
caused by MGNLUI-5292 Encoding is not properly considered w... Closed
duplicate
is duplicated by MGNLDAM-734 ZIP Upload with Unicode characters pr... 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   

Tested in Magnolia Demo itself with the attached zip.
The following settings were taken: 

1.  spaces of the new folder name are written as JCR node name: 

2. Special characters in assets are replaces to hyphens in JCR node names - that's correct, but the name property isn't:



 Comments   
Comment by Antti Hietala [ 17/Apr/19 ]

Magnolia replaces invalid JCR characters (&, space, etc.) with hyphens correctly, also in files inside the zip.

But valid special characters such as ÑîÅôöé· are incorrectly reduced to �������. 

Example:

GrÅ·e with &uuml and &szlig.txt
Gr��e-with--uuml-and--szlig.txt

To reproduce:

  1. Enable URI encoding in the web container (Tomcat)
  2. Set magnolia.utf8.enabled to true in magnolia.properties
  3. Upload the attached zip file into the DAM.
Comment by Rico Jansen [ 24/Apr/19 ]

We are hitting this one too, but only the space in the folder name part of it.

It does result in asset links in which the spaces are not correctly escaped. Most browser don't have problems with it, but for instance Facebook does, so in our case the opengraph image is not retrieved.

Comment by Mikaël Geljić [ 25/Jul/19 ]

Hi there,

The underlying issue MGNLUI-5292 has been resolved and will be released with Magnolia 6.1.1, therefore I'm closing this one as done.

rico.jansen, the space-to-dash escaping is independent from the encoding mismatch that was discussed here; I could verify the problem—it only happens with the "extract into new folder" option, and have now filed MGNLDAM-801.

Cheers,

Comment by Rico Jansen [ 30/Jul/19 ]

Ok, I have added myself as watcher to that issue.

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