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

As a display page template author I can map custom fields for content types that support them

    Details

      Description

      Out of the box Liferay supports creating display page templates for Web Content, Blog Entries and Documents. All of these three content types support custom fields. However, it's currently not possible to map the values of the custom fields so that they are displayed in the display page.

      The goal of this Story is to allow displaying custom field values in display pages. In addition to that, it should also be possible to display the fields when doing the mapping for an specific content item in a Content Page.

      As a result of this story, an API should also be provided for 3rd party developers to easily allow mapping of custom fields for custom content types that also support them. This can be achieved, for example, by providing a CustomFieldDisplayContributorHelper which provides a method that returns the list of InfoDisplayFields

      ---------------------------------
      After talking with the team, update the information:

      Motivation/Context
      Unify the behavior of the custom fields, allowing the user to map it to an editable text in a fragment in a content page.

      Initial setup
      the user can configure the custom field in control panel > configuration > custom field

      Acceptance Criteria
      1. The user can map custom fields to an editable text in a content page
      Given a custom field exists for a specific model (like web content article, blogs, etc)
      Then the user is able to map this custom field in any editable in a content page

      2. The user can map custom fields to an editable text in a page template
      Given a custom field exists for a specific model (like web content article, blogs, etc)
      Then the user is able to map this custom field in any editable in a page template

      3. The user can map custom fields to an editable text in a display content template
      Given a custom field exists for a specific model (like web content article, blogs, etc)
      Then the user is able to map this custom field in any editable in a display page template

      4. Any user can see the value of a custom field that is mapped to an editable text in a content page
      Given the user has mapped a custom field to an editable text in a content page
      Then the user is able to see the value of the custom field when viewing the content page
      and the format of the values will appear correctly

      5. Any user can see the value of a custom field that is mapped to an editable text in a display page template
      Given the user has mapped a custom field to an editable text in a display page template
      Then the user is able see the value of the custom field when viewing the display page template
      and the format of the values will appears correctly

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  7.2.X
                  Master