[MAGNOLIA-5290] Link referencing uploaded binary resource with special chars in filename is not encoded. Created: 02/Sep/13  Updated: 20/Sep/13  Resolved: 04/Sep/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.5.12, 5.0.5, 5.1

Type: Bug Priority: Neutral
Reporter: Robert Šiška Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLSTK-1214 stkTemplatingFunctions.getAssetLink()... 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:
Sprint: 5.1 - RC1

 Description   

Links to mgnl:resource nodes in content are not encoded when no imaging variation is used.

Customer ran into this issue with MGNLSTK-1214.



 Comments   
Comment by Jan Haderka [ 04/Sep/13 ]

Is this issue just on 4.5.x or also on 5.x?

Comment by Robert Šiška [ 04/Sep/13 ]

It is on 5.x too, ported it now. But I thought that having uploaded assets in content doesn't work anymore? There are some mgnl:resource nodes in demo-project, but they're can't be used...

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