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

Deprecate the locationView action

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2015.09
    • Component/s: Platform stack
    • Labels:
      None

      Description

      Since version 5.0, the view controller has supported both Content and Location as objects you view content from. This create a couple issues, like previewing the first draft of a content using a custom location view controller.

      Having two very similar ways to view content items adds confusion for developers, and doesn't bring much added value.

      The ez_content:viewContent controller actions must accept an optional location id. If it is passed, the location will be available for typehinting (Location $location), and part of the `$params` array. The default content controller must add it to the template as `$location`.

      The UrlAlias router must be updated to use generate `ez_content:viewContent` routes with the location as an argument.
      The ViewConfiguration should as much as possible be converted so that it keeps working without changes, giving developers time to adopt the new approach.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bertrand.dunogier@ez.no Bertrand Dunogier
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: