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

As a API User I want to modify draft locations for workflow use

    Details

    • Story Points:
      2

      Description

      Given I want to use workflows my content is not necessarily published straight away, and in case of approval workflows my editor might change the locations of my draft before publishing it.

      Technical implications:

      For reference here is old version of legacy schema (note: at least eznode_assignment.remote_id has become varchar in between):
      http://doc.ez.no/schemadoc/tables/ezcontentobject_tree.html
      http://doc.ez.no/schemadoc/tables/eznode_assignment.html

        Issue Links

          Activity

          Hide
          André Rømcke added a comment - - edited

          Possible new API:
          (Just examples, should be modeled with Christian Bacher)

          • A. Add <LocationDraft> = Location(Draft)Service->loadLocationDrafts( VersionInfo ), and <LocationDraft[]> = Location(Draft)Service->loadLocationDraftChildren( Location $location, $offset = 0, $limit = -1 );
          • B. Add loadLocationChildren( <Location:parent>, <int:offset>, <int:offset>, <bool|null:draft> ), make loadLocations() behavior depend on if ContentInfo is published or not (or change it to also accept VersionInfo), and make loadLocation() also check drafts by pushing the dual handling to SPI or the legacy storage engine. In this case Location(Draft)->id needs to be documented to make it clear id changes on publishing.

          #A would keep a clear separation in API, #B would make them somewhat consistent but somewhat separated

          Show
          André Rømcke added a comment - - edited Possible new API: (Just examples, should be modeled with Christian Bacher ) A. Add <LocationDraft> = Location(Draft)Service->loadLocationDrafts( VersionInfo ), and <LocationDraft[]> = Location(Draft)Service->loadLocationDraftChildren( Location $location, $offset = 0, $limit = -1 ); B. Add loadLocationChildren( <Location:parent>, <int:offset>, <int:offset>, <bool|null:draft> ), make loadLocations() behavior depend on if ContentInfo is published or not (or change it to also accept VersionInfo), and make loadLocation() also check drafts by pushing the dual handling to SPI or the legacy storage engine. In this case Location(Draft)->id needs to be documented to make it clear id changes on publishing. #A would keep a clear separation in API, #B would make them somewhat consistent but somewhat separated

            People

            • Assignee:
              Unassigned
              Reporter:
              André Rømcke
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified