Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
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.
Checklists
Attachments
1.
|
CLONE - Implementation |
|
To Do | Unassigned |
2.
|
CLONE - Review |
|
To Do | Unassigned |
3.
|
CLONE - Pre-Integration QA |
|
To Do | Unassigned |
4.
|
CLONE - QA |
|
To Do | Unassigned |