Details

    • Type: Story Story
    • Status: Closed
    • Priority: High 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.

        Issue Links

          Activity

          Hide
          Bertrand Dunogier added a comment -

          Doc still needed...

          Show
          Bertrand Dunogier added a comment - Doc still needed...
          Hide
          Rui Silva (Inactive) added a comment -

          QA is not able to test this without proper documentation explaining how to use content_view now for viewing locations too.
          Sending back.

          Show
          Rui Silva (Inactive) added a comment - QA is not able to test this without proper documentation explaining how to use content_view now for viewing locations too. Sending back.
          Hide
          Bertrand Dunogier added a comment -

          Okay, this can stay in the doc column in the meanwhile.

          Short: if a location view uses a custom template AND a custom controller, it won't be converted to content view. Executing it should generate a deprecation message.

          Show
          Bertrand Dunogier added a comment - Okay, this can stay in the doc column in the meanwhile. Short: if a location view uses a custom template AND a custom controller, it won't be converted to content view. Executing it should generate a deprecation message.
          Hide
          Bertrand Dunogier added a comment -

          https://doc.ez.no/display/TECHDOC/Content+view updated to only mention content and not location.

          Show
          Bertrand Dunogier added a comment - https://doc.ez.no/display/TECHDOC/Content+view updated to only mention content and not location.
          Hide
          Rui Silva (Inactive) added a comment -

          Tested and approved by QA for master.

          Show
          Rui Silva (Inactive) added a comment - Tested and approved by QA for master.

            People

            • Assignee:
              Unassigned
              Reporter:
              Bertrand Dunogier
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: