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

Permission limitations based on the subtree should be removed when dependent location removed

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: High High
    • Resolution: Unresolved
    • Affects Version/s: 1.7.5, 1.12.0
    • Fix Version/s: Customer request
    • Component/s: Permissions
    • Labels:
      None

      Description

      The behaviour of managing permission limitations based on subtree should be changed.

      Current behaviour (in 1.7.5):
      1. Create content structure, for e.g.: /Home/Folder 1/Folder 2/Folder 3 (as location ids: 1/2/55/56/57)
      2. Set permission limitation, for e.g.: content/edit to subtree 1/2/55/56/57
      3. Remove Folder 3 (location id: 57).
      4. Previously created permission limitation is still the same: content/edit | 1/2/55/56/57

      Current behaviour (in 1.12):
      1. Create content structure, for e.g.: /Home/Folder 1/Folder 2/Folder 3.
      2. Set permission limitation, for e.g.: content/edit to subtree /Home/Folder 1/Folder 2/Folder 3.
      3. Remove Folder 3.
      4. Previously created permission limitation will be: content/edit | /Home/Folder 1/Folder 2
      5. In fact, (you can check in database table ezpolicy_limitation_value) limitation is still set for Folder 3. There is another ticket for change it in Platform UI.

      In legacy, 5.4.x, behaviour was a bit different. When you removed the location on which permission limitation was based, then this limitation was automatically removed.

        Issue Links

          Activity

          No workflow transitions have been executed yet.

            People

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

              Dates

              • Created:
                Updated: