[MGNLUI-3061] Documents with multiple dots in name are linked incorrectly from CK editor Created: 15/Jul/14  Updated: 01/Jul/15  Resolved: 08/Dec/14

Status: Closed
Project: Magnolia UI
Component/s: widgets
Affects Version/s: 5.2.4
Fix Version/s: 5.3.6

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-3294 Links to magnolia pages created from ... 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   

To reproduce:

  • upload pdf file with dots in name to DAM
  • open any page and add Text and Image component to it.
  • in text part of the component, add internal link pointing to previously uploaded pdf
  • activate a page
  • observe on public, link is still pointing to author instance
  • upon opening page and editing component, observe that internal link is now external with url pointing to author instance


 Comments   
Comment by Jan Haderka [ 09/Sep/14 ]

@Eric MGNLDAM-498 has fix version for DAM 2.0.3 which is released with Magnolia 5.3 - does it work also for 5.2 branch?

Comment by Eric Hechinger [ 09/Sep/14 ]

Tested on a 5.3.3 and 5.2.8 and this issue is no more reproducible.
I suspected that the fix was done within MGNLDAM-498 but as this ticket is only relevant for 5.3.x... my assumption was incorrect....

Comment by Zdenek Skodik [ 03/Oct/14 ]

For the reproduction it's necessary to set images=true at the field definition since the link transformation is done as part of the presentation2model2presentation processing of AssetsEnabledRichTextFieldFactory#createFieldComponent(), which is skipped otherwise. Since there are no commits on this issue, can we just reopen it despite the fact 5.3.3 has already been released, or do you prefer a clone?

Comment by Christoph Meier [ 08/Dec/14 ]

This is not an issue anymore. It works fine on master and 5.3.6.
It was most likely fixed on DAM-2.0.3

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