[PAGES-303] Subpages Created Under Pages With "Resources" For Its Name Results In Missing Page Created: 20/May/20  Updated: 30/Sep/21  Resolved: 30/Sep/21

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 5.7.2, 6.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Unassigned
Resolution: Obsolete Votes: 2
Labels: y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
duplicate
duplicates MAGNOLIA-8155 Resource mapping conflict is not dete... Open
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   

User gets a 404 error message when creating subpages under pages named “resources”. Also occurs on the demo when created under “travel” or “sportstation”. But does not occur with other names nor when you duplicate “travel” or “sportstation”. See below examples with different page structures and the recorded results:

test1
->resources
    ->subpage_test
Page is displayed correctly

(within the demo)
travel
->resources
    ->subpage_test
Results in 404 page

(within the demo)
sportstation
-> resources
    ->subpage_test
Results in 404 page

(within the demo)
sportstation0 (duplicated page)
-> resources
    ->subpage_test
Page is displayed correctly

resources
->subpage_test
Results in 404 page

test1
->subpage_test1
    ->resources
        ->subpage_test2
Page is displayed correctly

Error is reproduced in 5.7.6 as well as 6.2 from fresh instances and within the demo. Workaround would be to use a different name other than "resources". Tried using other keywords but did not see any difference.



 Comments   
Comment by Marta Kobus [ 30/Sep/21 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

 

Thank you,

The Magnolia Team

Generated at Mon Feb 12 06:17:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.