[MGNLADVCACHE-83] Paths created for dynamic fragments are not site aware Created: 05/Jan/17  Updated: 12/Apr/17  Resolved: 12/Jan/17

Status: Closed
Project: Advanced Cache
Component/s: None
Affects Version/s: 1.7.5, 1.8.1
Fix Version/s: 1.7.6, 1.8.2

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLADVCACHE-89 FragmentInjectionLister can produce i... Closed
is causing MGNLEE-476 Add localhost domain to demo project ... Closed
relation
is related to DOCU-996 Reflect changes to path resolving int... 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
Sprint: Kromeriz 78
Story Points: 8

 Description   

After resolving the MAGNOLIA-6882 we uncovered yet another where handle was wrongly resolved.

The FragmentInjectionListener was not removing site prefix for the resolved page / component node, leading to 404 errors.

Issue can be reproduced when domain is correctly configured and you access a page with fragments.


Generated at Sun Feb 11 23:10:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.