Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-27974

As a v2 editor I want to set the default sort parameter for sub-items table in the Details content view tab

    XMLWordPrintable

Details

    • Sprint 5
    • 2

    Description

      Description

      In eZ Platform, the user can define the order of the children when viewing a container (frontend side).
      Example:

      News (Folder with sort order publication date / desc)
      |  |_ Article (2017/06/10)
      |  |_ Article (2017/05/22)
      Brochures (Folder with sort order priority / asc)
         |_ Brochure (priority 10)
         |_ Brochure (priority 20)
      

      Technical

      For a specific location, the editor can define the sort order of the sub-items. This sort order is "attached" to the location of the content item.
      In case of multiple locations for the same content object, the sort order can be different.

      By default the two dropdown lists display the default sort order defined at the Content Type level.

      IMPORTANT

      The sort order information (location) will be used when the user loads the location.

      • If the user clicks on table headers in order to change the order of the sub-items (table ordering), the sort order (location) defined previously does not apply anymore.
      • If the user refreshes the page, the sort order (location) is used again.

      Label change

      Having default in the labels might be confusing for the user. Here are the new labels
      BEFORE

      Sub-items default ordering
      Default listing of sub-items by 
      

      AFTER

      Sub-items sorting order
      Order by
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            supriya.bhargava-obsolete@ibexa.co Supriya Bhargava (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: