[MGNLUI-3294] Links to magnolia pages created from CK editor are rendered wrong on public instances when node names contain dots (wrong context-path). Created: 10/Dec/14  Updated: 20/Jan/15  Resolved: 15/Jan/15

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

Type: Bug Priority: Neutral
Reporter: Christoph Meier Assignee: Michael Mühlebach
Resolution: Cannot Reproduce Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLDAM-535 Changing internal link after initial ... Closed
relation
is related to MGNLUI-3061 Documents with multiple dots in name ... 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:

Use a dialog with a Richtext-Editor which the property images=true.
=> To keep it easy, just add a text/image component on an article-page.
Before doing:
Set /modules/standard-templating-kit/dialogs/generic/controls/text@images=true

Duplicate the node events-overview under demo-project/news-and-events.
Rename the duplicate to events.overview.
Add the text/image component.
Link to a magnolia-page which has in its path a node with a dot (like events.overview).
Publish all.

=> You will/should notice, that the link made with CK-Editor on the public instance is still linked to a page in author instance.



 Comments   
Comment by Evzen Fochr [ 19/Dec/14 ]

Problem found. LinkUtil.java LINK_PATTERN must be upgraded so it don't catch first occurrence of dot but last occurrence before ? or # or end of string. Bud if we are not sure that extension will be appended (configurable ?) than its not possible to solve it by regexp, maybe we can replace dots in node names.

Comment by Michael Mühlebach [ 14/Jan/15 ]

I tested it on the current 5.3.x branch and could not reproduce it. Used an image, page and asset link but the context was always correct.

Comment by Michael Mühlebach [ 15/Jan/15 ]

Eating my words: The problem was not fixed but only existed, if one of the node names contained a dot like events.overview.
But MGNLDAM-535 fixes this problem as well.

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