[MGNLMULTPA-65] Same name between Pages app and custom page cause incorrect loading Created: 18/Dec/23  Updated: 01/Feb/24

Status: Accepted
Project: Multiple Pages Apps
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Chuong Doan Huy Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLMULTPA-66 CLONE - Implementation Sub-task To Do  
MGNLMULTPA-67 CLONE - Review Sub-task To Do  
MGNLMULTPA-68 CLONE - Pre-Integration QA Sub-task To Do  
MGNLMULTPA-69 CLONE - QA Sub-task To Do  
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: Multiple Pages App LD
Team: DeveloperX

 Description   

In main pages app and custom page app, create a page with same name like "banners".
Open to edit "banners" page in main page app.

Expect : page content load correctly.

Actual : "banners" page content from custom page loaded instead of main page.

The problem only happens when the page in Pages app is at the root. If the page is under another page, there is no problem.

Notes:

Magnolia system design might not support the use case mentioned in the description above. We need to decide how to handlle this. Maybe we prevent a page in the paages app to be created with saame name as page in Custom pages app or something.

-

Probably the problem is not actually relate to the name of the page in the custom-app, but really the name of the site used by the custom app. This makes sense in the Pages app, when you open that root page, the site resolution for the custom app detects it and applies the site to it - this causes it to use the workspace set in the site - so it opens the content from the wrong workspace.



 Comments   
Comment by Christopher Zimmermann [ 18/Dec/23 ]

Hi chuong.doan can you drop a comment on why this is a clone of MGNLMULTPA-59 ? Is the problem in thiss ticket only happening if the page name in both apps is the same?

Comment by Chuong Doan Huy [ 18/Dec/23 ]

Hi czimmermann, i just clone for faster creating ticket, not related to MGNLMULTPA-59 at all ( i don't know if cloning tickets imply some relations ???).
About the problem in this ticket, yes it only happening if page name in both apps is the same (the problem is that loading wrong content, not blank page like MGNLMULTPA-59).

Comment by Christopher Zimmermann [ 18/Dec/23 ]

I am pretty sure the problem is only when a root page in the Pages app has the name of the configured "Site" of the custom pages app.

The problem is likely that the system associaltes the wrong site with that page - and then uses the site configured workspace - and thus renders the content from the page from the other app.

So in a way It is working properly. But of course for our usecase it is a bug, because now we have the two apps.

The question is, how should we resolve this? How should it work? Could we block the page editor from opening and display a notification? "This path is already in use by another app: Banners.".

Comment by Chuong Doan Huy [ 19/Dec/23 ]

Instead of blocking the opening, can we just validate the page name (when users create new page) across all page-related workspaces to prevent same name issue ?

Comment by Christopher Zimmermann [ 19/Dec/23 ]

I like this idea of preventing authors from creating the problem.

It might be enough.

But theres always the possiblity that the node already existed - or that the node gets created by other means like Import, or REST or code. it would be tricky to cover all of those cases. These are more like edge cases - but something to consider.

Generated at Mon Feb 12 10:21:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.