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

As an editor, I would like to remove all content locations in one go

    Details

    • Type: Story Story
    • Status: Backlog
    • Priority: High High
    • Resolution: Unresolved
    • Affects Version/s: 2.1.0, 1.13.2, 1.7.7
    • Fix Version/s: Customer request
    • Component/s: None
    • Labels:
      None

      Description

      Currently, as well as in old eZ Publish, it is not possible to remove all content locations in one go. If the content has more than one location, and the user moves it to the trash, then in fact only that particular one location is moved to trash (removed if user cleans trash).

      This is very uncomfortable and time consuming for the editors working on the content in the customer's installation.

      Note from the customer:

      With a note to its prioritization, it is worth remembering that it is seemingly small deficiencies like these which undermine the quality of the entire eZ Platform user experience, meaning that any new features won't impress upon our users that this is a quality, enterprise, product.

        Activity

        Hide
        Sylvain Guittard added a comment -

        It makes sense from the user perspective.
        Sławomir Uchto Maciej Kobus Andrzej Longosz is there any blocker from the API perspective?

        Show
        Sylvain Guittard added a comment - It makes sense from the user perspective. Sławomir Uchto Maciej Kobus Andrzej Longosz is there any blocker from the API perspective?
        Hide
        Andrzej Longosz added a comment -

        It's not supported by the API out of the box, but can be achieved by either adding a dedicated API to TrashService or by several API calls.

        Please take into the account that:

        • Published Content must have at least one Location. AFAICS TrashService will remove Content if the last Main Location is trashed. However when deleting Location via LocationService, the result is unknown (TBH expected some sort of check, but I didn't investigate it too deeply)
        • Removing a Location that contains Children is not possible, therefore such API call might result in an error on an entire transaction because of just one Location with Children.

        The above are not blockers, but need to be considered when implementing it, thus might impact Story Points.

        Show
        Andrzej Longosz added a comment - It's not supported by the API out of the box, but can be achieved by either adding a dedicated API to TrashService or by several API calls. Please take into the account that: Published Content must have at least one Location. AFAICS TrashService will remove Content if the last Main Location is trashed. However when deleting Location via LocationService, the result is unknown (TBH expected some sort of check, but I didn't investigate it too deeply) Removing a Location that contains Children is not possible, therefore such API call might result in an error on an entire transaction because of just one Location with Children. The above are not blockers, but need to be considered when implementing it, thus might impact Story Points.

          People

          • Assignee:
            Unassigned
            Reporter:
            Kamil Madejski
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: