-
Bug
-
Resolution: Fixed
-
Neutral
-
1.7.5, 1.8.1
-
None
-
None
-
-
Empty show more show less
-
Kromeriz 78
-
8
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.
Acceptance criteria
- is causing
-
MGNLADVCACHE-89 FragmentInjectionLister can produce invalid content path
- Closed
-
MGNLEE-476 Add localhost domain to demo project sites
- Closed
- is related to
-
DOCU-996 Reflect changes to path resolving introduced by MGNLADVCACHE-83
- Closed