Details
-
Story
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
Description
The goal of this story is to allow page administrators to import page templates alongside fragments in the ZIP. Since a page template may contain a number of variations of content and configuration, to keep the scope of this story limited, only the following data will be supported:
- Fragments added to the page
- The layouts of columns added to the page and the fragments inside its columns
- Inline content introduced within fragment editable elements
- The configuration of all the fragments of the page
- The look & feel configuration of the page
Known limitations
The following information will not be imported for now (support will be added in subsequent stories):
- Widget Configuration (Portlet Preferences)
- Widget Permissions
- Mappings of editables to existing content
- Fragment HTML, CSS, JavaScript & Resources: Only a reference to the name of the fragment will be exported. On import in the fragment entry is not found, it will be ignored.
Technical notes
- The import format should be done into a JSON file as defined in
LPS-106212. - The JSON file must have a JSON Schema that facilitates modifying it and validating the change.
Test Scenarios
Test Scenarios | Test Strategy | Kind of test | Is it covered by FrontEnd ? (JS-Unit) | Is it covered by BackEnd ? (unit or integration) |
---|---|---|---|---|
Can import a zip file with single content page template to page templates collection | Smoke | Manual | No | Yes, LayoutPageTemplatesImporterTest |
Can import a zip file with multiple content page templates to page templates collection | Smoke | Manual | No | TO DO |
Smoke | Manual | No | No | |
The fragments that not existing in current site will be ignored when import a content page template | Sanity | Manual | No | No |
When import a content page template, the layout elements and nested elements from zip file also be imported | Sanity | Manual | No | Yes, LayoutPageTemplatesImporterTest |
When import a content page template, the edited inline content of fragments from zip file also be imported | Sanity | Manual | No | Yes, LayoutPageTemplatesImporterTest |
When import a content page template, the custom configuration settings of fragments from zip file also be imported | Sanity | Manual | No | Yes, LayoutPageTemplatesImporterTest |
When import a content page template, the custom Look and Feel of it should also be imported | Sanity | Manual | No | TO DO |
Can import a content page template based on custom master to page templates collection | Sanity | Manual | No | TO DO |
When import a content page template with thumbnail, the thumbnail should also be imported | Smoke | Manual | No | TO DO |
Can export a content page template with custom fragments and import | Sanity | Manual | No | No |
Attachments
Issue Links
- is related to
-
LPS-113287 LPS-107748 - Product QA | Test Automation Creation
-
- Closed
-
- Testing discovered
-
LPS-110791 The name of archive file is inconsistent with in portal when rename the content page template before export
- Closed
-
LPS-110800 The Look and Feel settings in file are inconsistent with in portal when content page template based on custom master
- Closed