Uploaded image for project: 'Magnolia pages module'
  1. Magnolia pages module
  2. PAGES-943

Integrate norsu pages with the site module

    XMLWordPrintable

Details

    • Story
    • Resolution: Outdated
    • Neutral
    • 6.3
    • None
    • None
    • None

    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

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            1.
            Implementation Sub-task To Do Unassigned
            2.
            Review Sub-task To Do Unassigned
            3.
            Pre-Integration QA Sub-task To Do Unassigned
            4.
            QA Sub-task To Do Unassigned

            Activity

              People

                Unassigned Unassigned
                aichimescu Andrei Ichimescu
                AuthorX
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD