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

As a Developer I want API to allow removal of the translation from all content object versions

    Details

      Description

      We need to design 1. PHP and 2. REST API changes to allow deleting content object translation without deleting the whole object. And describe the behavior as proposed in the epic.


      Open question is what customers need here.

      What has been reported that they need is:

      • Deleting a translation from all versions of a content (including published version, drafts and archives)
        • This is somewhat in contrast to how versions are treated today in the system, with exception of drafts the system normally don't allow editing/changing versions

      What would make more technically sense:

      • Deleting a translation from a version and return a draft (UI code can handle directly publishing if needed, it can also offer user to delete all prior versions with given language if user really want to wipe out history)

      In both cases should probably throw if user tries to delete last remaining translation, for that content/version deletion is more suitable

      Any input on this is welcome.

        Issue Links

          Activity

          Hide
          Rui Silva (Inactive) added a comment -

          Tested and approved by QA for master, that the removal of translations in a language for all versions of a single content can be removed.

          Show
          Rui Silva (Inactive) added a comment - Tested and approved by QA for master, that the removal of translations in a language for all versions of a single content can be removed.
          Show
          André Rømcke added a comment - Merged: https://github.com/ezsystems/ezpublish-kernel/commit/f0ec2b93a413bf293d6329bb99034d9b120db95c
          Show
          Andrzej Longosz added a comment - PR: https://github.com/ezsystems/ezpublish-kernel/pull/2031
          Hide
          André Rømcke added a comment -
          Show
          André Rømcke added a comment - Specification done, ready for implementation now: https://github.com/ezsystems/ezpublish-kernel/commit/79eb48d89b54acc76f2e22114bff61edf8aa30f3
          Hide
          Andrzej Longosz added a comment -

          As the result of this discussion in Spec PR the meaning and goal of this story gets defined to allowing removal of the translation from all the Versions of a single Content Object.

          There is a follow-up story EZP-27508 which covers removal of a translation from a single Version, thus creating a Content Draft.

          Show
          Andrzej Longosz added a comment - As the result of this discussion in Spec PR the meaning and goal of this story gets defined to allowing removal of the translation from all the Versions of a single Content Object . There is a follow-up story EZP-27508 which covers removal of a translation from a single Version, thus creating a Content Draft.
          Hide
          Paul Borgermans added a comment -

          Both options should be possible, they do represent different use cases.

          In the second option the part on "UI code ... can also offer user to delete all prior versions with given language if user really want to wipe out history", is actually a third use case on versions management and I would suggest to keep it out of this language management story

          Show
          Paul Borgermans added a comment - Both options should be possible, they do represent different use cases. In the second option the part on "UI code ... can also offer user to delete all prior versions with given language if user really want to wipe out history", is actually a third use case on versions management and I would suggest to keep it out of this language management story
          Hide
          Andrzej Longosz added a comment -

          WIP Spec PR: https://github.com/ezsystems/ezpublish-kernel/pull/2001
          Right now it meets the needs of both use cases.

          Show
          Andrzej Longosz added a comment - WIP Spec PR: https://github.com/ezsystems/ezpublish-kernel/pull/2001 Right now it meets the needs of both use cases.
          Hide
          Douglas Hammond added a comment -

          For my use case either way would suffice. I would lean towards the second option too as it is more inline with how ez handles content. Second option also would allow you to restore the previous language if you had to by basing new content on that version.

          Show
          Douglas Hammond added a comment - For my use case either way would suffice. I would lean towards the second option too as it is more inline with how ez handles content. Second option also would allow you to restore the previous language if you had to by basing new content on that version.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days, 5 hours
                2d 5h