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

As an Editor, I want to be able to assign a section to a subtree

    Details

      Description

      Currently, it is possible to assign a section to the chosen Content only, but not to the whole subtree.
      It was possible to do using the Legacy Admin.

        Issue Links

          Activity

          Hide
          Sylvain Guittard added a comment -

          I just rechecked eZ Publish, eZ Publish v1 and there is an inconsistency. On eZ Publish, when you assign a section, you assign the section to a subtree not to a single content object. Bringing this feature to the product will also simplify the interface and the way of managing sections.
          ping Inaki Juaniz-Velilla

          Show
          Sylvain Guittard added a comment - I just rechecked eZ Publish, eZ Publish v1 and there is an inconsistency. On eZ Publish, when you assign a section, you assign the section to a subtree not to a single content object. Bringing this feature to the product will also simplify the interface and the way of managing sections. ping Inaki Juaniz-Velilla
          Hide
          Bertrand Dunogier added a comment - - edited

          We should be able to add that to the SectionService. The things to look out for are:

          • It must be added to REST as well
          • expiring persistence & HTTP cache when this happens
          • performances if the subtree is very large
          • permissions (what if the user doesn't have permissions on the whole subtree ?)
          Show
          Bertrand Dunogier added a comment - - edited We should be able to add that to the SectionService . The things to look out for are: It must be added to REST as well expiring persistence & HTTP cache when this happens performances if the subtree is very large permissions (what if the user doesn't have permissions on the whole subtree ?)
          Hide
          Sylvain Guittard added a comment -
          Show
          Sylvain Guittard added a comment - ping Sławomir Uchto Andrzej Longosz for review
          Hide
          Andrzej Longosz added a comment -

          performances if the subtree is very large

          So this can be solved in the same way as copying subtree - with a limit. Given the performance issues are similar in case of any bulk operation on a subtree, as I've said on copy subtree PR I think we could consider a common setting for that, e.g. subtree_operations.limit. WDYT?

          permissions (what if the user doesn't have permissions on the whole subtree ?)

          I think it should behave in the same way like LocationService::copySubtree does - if a user doesn't have permissions to any Content in a Subtree, then the API throws UnauthorizedException.

          We should be able to add that to the SectionService

          +1, suggested spec:

          /**
           * @param \eZ\Publish\API\Repository\Values\Content\Location $subtree
           * @param \eZ\Publish\API\Repository\Values\Content\Section $section
           */
          public function assignSectionToSubtree(Location $subtree, Section $section);
          

          Show
          Andrzej Longosz added a comment - performances if the subtree is very large So this can be solved in the same way as copying subtree - with a limit. Given the performance issues are similar in case of any bulk operation on a subtree, as I've said on copy subtree PR I think we could consider a common setting for that, e.g. subtree_operations.limit . WDYT? permissions (what if the user doesn't have permissions on the whole subtree ?) I think it should behave in the same way like LocationService::copySubtree does - if a user doesn't have permissions to any Content in a Subtree, then the API throws UnauthorizedException . We should be able to add that to the SectionService +1, suggested spec: /** * @param \eZ\Publish\API\Repository\Values\Content\Location $subtree * @param \eZ\Publish\API\Repository\Values\Content\Section $section */ public function assignSectionToSubtree(Location $subtree , Section $section );
          Hide
          Sylvain Guittard added a comment - - edited

          Andrzej Longosz Bertrand Dunogier
          I don't think this operation will require the same amount of resources as copy operation. Copy is basically create content items.
          Regarding the permissions, we will follow the same scenarios as described in the admin panel for section/assign policies. In case of some sub-items where the user cannot perform a section change we will display a notification

          Lars Eirik Rønning
          It's planned for 2.4. Finalizing specs for one of the next sprints

          Show
          Sylvain Guittard added a comment - - edited Andrzej Longosz Bertrand Dunogier I don't think this operation will require the same amount of resources as copy operation. Copy is basically create content items. Regarding the permissions, we will follow the same scenarios as described in the admin panel for section/assign policies. In case of some sub-items where the user cannot perform a section change we will display a notification Lars Eirik Rønning It's planned for 2.4. Finalizing specs for one of the next sprints
          Show
          Adam Wójs added a comment - PR: https://github.com/ezsystems/ezplatform-admin-ui/pull/798
          Show
          Barbara Grajczyk added a comment - PR merged: https://github.com/ezsystems/ezplatform-admin-ui/commit/83f0d94b99674492c243650501dabbe5caca34e9

            People

            • Assignee:
              Unassigned
              Reporter:
              Sylvain Guittard
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile