[MGNLDMS-265] Encode/do not encode document handle and filename according to UTF8 setting Created: 11/Mar/13  Updated: 17/Apr/13  Resolved: 17/Apr/13

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.6.5
Fix Version/s: 1.6.7

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
is related to MGNLDMS-268 Uploading files with special characte... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Documents and images uploaded containing special characters in the filename generate broken DMS links.
For example: If a document or image contains german umlauts (äüö) in the filename the dms link gets incorrectly encoded.
The filename itself is encoded correctly but the dms path is wrong.
For example: /migrationAuthor/.imaging/..../dms/internet/äüöimage/document/%C3%A4%C3%BC%C3%B6image.png
This problem seems to concern all DMS links to document or images in the textimage component (referenced as dms image) or the richtext editor itself referenced as simple file link



 Comments   
Comment by Magnolia International [ 11/Mar/13 ]

Sounds like MGNLDMS-107 or MGNLDMS-209 or MGNLDMS-173 ...

Comment by Roman Kovařík [ 10/Apr/13 ]

Check encoding of plus sign.

Comment by Roman Kovařík [ 17/Apr/13 ]

The '+' sign breaks DMS links:

  1. UTF8 disabled: URLEncoder.encode() encodes spaces to ''-> encode '' back to encoded space (%20)
  2. UTF8 enabled: encode '+' to ' ' (space)
Generated at Mon Feb 12 00:49:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.