[MAGNOLIA-8234] URI Mapping Issue with repository mapping Created: 10/Sep/21  Updated: 16/Dec/21  Resolved: 02/Dec/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 6.2.11
Fix Version/s: 6.2.14

Type: Bug Priority: Blocker
Reporter: Leah Staniorski Assignee: Dai Ha
Resolution: Fixed Votes: 0
Labels: cs-bk, maintenance
Remaining Estimate: Not Specified
Time Spent: 0.25d
Original Estimate: Not Specified

Attachments: PNG File screenshot1.png     PNG File screenshot2.png     PNG File screenshot3.png    
Issue Links:
relation
is related to MULTISITE-109 Incorrect i18n links with subsites Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* 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: Global Maintenance 1, Global Maintenance 2, Global Maintenance 3
Story Points: 8

 Description   

Suppose you have the following root level pages with site definitions sharing the same domain:
/site-a (URI mapped to root/empty)
/site-a-patient (URI mapped to /patient)
Now suppose you also have the following page:
/site-a-patient/patient-information
Magnolia is delivering 404 for that page or any subpage that starts with /patient

Steps to reproduce on demo author:
1. Add new site in Pages app called travel-patient and a subpage called patient-information both with some content. Publish both. See screenshot1.
2. Duplicate travel site definition. Update mapping as shown in screenshot2. Publish site definition.
3. Go to https://travel-demo.magnolia-cms.com/patient/patient-information.html and see error as shown in screenshot3.

Error in logs:
WARN info.magnolia.rendering.engine.RenderingFilter : Resource not found: [/patient/patient-information.html?null]

No non-human workaround found


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