XMLWordPrintable

    Details

    • Type: Epic
    • Status: Deploy
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Pollux
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      Content item view

      Description

      This epic covers the most important content items viewing features.

      Currently eZ Platform does not have any standard/base templates people can reuse and build upon, besides Design/Theming system (#EZP-22948), documented and supported Core modules are needed to accomplish this.

      For customer websites, Demo UI and Admin UI, there should be a set of Content views (the "content module") with views and standard templates.

      Other related topics:

      • Content: view, search, list (powered by name query), relations (/embed), download* and content edit (if possible reusing content type work, should be own epic (EZP-24339))
      • Location: view, list, tree (planned to be handled by content views with option to provide location id as optional context)
      • Users: profile, list (todo: create separate epic for this)

      Requirements for the Content view view (aka "action"):

      • Need to primary be referred by Content Id, optionally location id (hence change needed on content view)

      Related:

      • For listing: EZP-24225 Content list view including"Named Query"

      A few already exists in both DemoBundle and AdminBundle, and can potentially be moved to CoreBundle and made generic.

      * at least download must be backported to 5.4 as well.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bertrand.dunogier@ez.no Bertrand Dunogier
                Reporter:
                andre.romcke@ez.no André Rømcke
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: