[MAGNOLIA-6344] Page gets 404 when parent page has the context path as name Created: 19/Aug/15  Updated: 01/Mar/18  Resolved: 01/Mar/18

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.0
Fix Version/s: 5.6.1

Type: Bug Priority: Major
Reporter: Edwin Guilbert Assignee: Unassigned
Resolution: Done Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tomcat 7.0.47 (bundled)


Issue Links:
Relates
causality
relation
is related to MAGNOLIA-7166 Page gets 404 when the beginning of t... Closed
is related to PAGES-149 Visual warning clue for context path 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:
Story Points: 5

 Description   

If a top level page has the same name as the context path, the children pages will get 404 when rendered.

Example:

Context path: /magnoliaAuthor
Page name: magnoliaAuthor
Subpage name: test

If you try to go to http://localhost:7001/magnoliaAuthor/magnoliaAuthor/test it gives 404.

Tested on magnolia enterprise bundle.



 Comments   
Comment by Jan Haderka [ 01/Mar/18 ]

Retested. Issue is fixed as of Multisite 1.3 and Magnolia 5.6.1. Most likely related to removal of Content API or deprecated prefix handling and unbundling of legacy admin central/interface code.

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