[PAGES-943] Integrate norsu pages with the site module Created: 28/Nov/22  Updated: 09/Jun/23  Resolved: 06/Jun/23

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3

Type: Story Priority: Neutral
Reporter: Andrei Ichimescu Assignee: Unassigned
Resolution: Outdated 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

Issue Links:
relation
is related to PAGES-933 Edit page properties action should be... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-944 Implementation Sub-task To Do  
PAGES-945 Review Sub-task To Do  
PAGES-946 Pre-Integration QA Sub-task To Do  
PAGES-947 QA Sub-task To Do  
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)
Date of First Response:
Epic Link: Post TPR. SaaS Norsu Pages
Sprint: POST TPR backlog
Team: AuthorX

 Description   

With the implementation of PAGES-933, we do not have to wait for a page to be rendered in order for the edit page properties to be shown. By not relying on the client side to provide the dialog id, the page prototype (from the site module) is not taken into consideration.
At the writing time of this issue, the site-app is not bundled into the saas instance, therefore there is no page prototype. When the site prototype is going to be available, we need to integrate with the module in order to present to the user the merged dialog (page dialog + prototype dialog) in order for the complete property set to be editable.

AC: 
  integrate pages app with the site module

  read the prototype page template from the site module, and if available, apply the changes to the edit page property action and action availability



 Comments   
Comment by Pierre-Yves Lendenmann [ 06/Jun/23 ]

I migrated this ticket to Jira Cloud. The new ticket replacing this one is SAAS-92. I therefore close this one here.

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