Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-112093

As a user I would like to be able to add a "Content Display" fragment within a a Collection Display fragment so that I can use predefined templates to control how it is displayed

    Details

      Description

      Intro/Context:

      Adding styles to a Collection Display Fragment is possible using most of the basic fragments. But when we want to re-use existing templates it is not clear how to do that (today a mapping allows it - the template appears with a star). 

      The goal of this story is to allow having enable to leverage "Content Display" fragment in a collection display where a default template is used automatically and all fields are mapped. Like this we can leverage and re-use existing Templates (freemarker templates).

      When the page creator drops the Content Display fragment inside a cell of the Collection Display fragment it will be replicated across all cells (just like it happens for any other fragment) and it will display in each cell the appropriate collection item. In order to achieve this, each Content Display fragment will automatically pick the corresponding collection item as the content to display. It should still be possible for the user to use the fragment configuration to select any other content just as if the fragment had been elsewhere. When the user selects another content he should also be able to go back to selecting the corresponding collection item. The proposed way to do that is to show a dropdown when the user clicks on the + icon to select the content in the fragment configuration. The dropdown will have an option called "Collection Item" as well as another option to open the content selection pop-up. This solution is consistent with the existing behavior when selecting the content for mapping, which uses a dropdown to allow quick selection of content already being used in the page.

      After adding the fragment, the user should then be able to choose how the content is displayed using the existing mechanism to choose a template:

      When user drags and drops a "Content Display" fragment

      Then all the collections items are styled by the default associate template (template with same web content structure)

      When user changes the default template for a custom one

      Then all the collections items are styled by the custom template (templates with same web content structure)

      See mock up in figma

       

      Test Scenarios

      Test Scenarios Test Strategy Kind of test Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd ? (unit or integration) Could it be covered by POSHI?
      The Web Content Articles of collection are displayed using Default Template when add a Content Display to Collection Display Smoke Manual No No Yes
      The Blogs Entries of collection are displayed using Full Content when add a Content Display to Collection Display Sanity Manual No No Yes
      The documents of collection are displayed using Abstract when add a Content Display to Collection Display Sanity Manual No No Yes
      Can display Web Content Articles of collection using custom template when add a Content Display to Collection Display Smoke Manual No No Yes
      The Web Content Articles of collection are displayed normally when enable Live Sanity Manual No No Yes

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              manoel.cyreno Manoel Cyreno
              Reporter:
              tarik.demnati Tarik Demnati (Inactive)
              Engineering Assignee:
              SE Support
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master