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

When editing in frontend siteaccess using PathPrefix and RootNode route will display parent node_id instead of correct node_id

    Details

      Description

      While testing EZP-23725, I've found out that after publishing the "News" folder, using the frontpage will break the

      content:
          tree_root:
              location_id: 142
      

      setting.

      Steps:

      1. On the admin interface, create folder A
      2. Inside folder A, create folder B
      3. Take note of folder's B node_id
      4. In ezpublish.yml, on the default site access, add
      content:
      tree_root:
      location_id: node_id
      5. Access to your site frontpage
      6. Login
      7. Edit "Folder" B and publish it
      8. Instead of displaying folder B it will display folder A

      Workaround
      1. Login into admin interface
      2. Edit folder B and publish it

        Issue Links

          Activity

          Pedro Resende (Inactive) created issue -
          Pedro Resende (Inactive) made changes -
          Field Original Value New Value
          Description While testing [EZP-23725], I've found out that after publishing the "News" folder, using the frontpage will break the

          {code}
          content
          While testing [EZP-23725], I've found out that after publishing the "News" folder, using the frontpage will break the

          {code}
          content:
              tree_root:
                  location_id: 142
          {code}

          setting.

          Steps:

          1. On the admin interface, create folder A
          2. Inside folder A, create folder B
          3. Take note of folder's B node_id
          4. In ezpublish.yml, on the default site access, add
          content:
              tree_root:
                  location_id: node_id
          5. Access to your site frontpage
          6. Login
          7. Edit "Folder" B and publish it
          8. Instead of displaying folder B it will display folder A

          *Workaround*
          1. Login into admin interface
          2. Edit forlder B and publish it
          Labels QA
          Pedro Resende (Inactive) made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Pedro Resende (Inactive) made changes -
          Link This issue discovered while testing EZP-23725 [ EZP-23725 ]
          Pedro Resende (Inactive) made changes -
          Link This issue blocks EZP-23725 [ EZP-23725 ]
          Pedro Resende (Inactive) made changes -
          Summary Ehen editing in frontend siteaccess using PathPrefix and RootNode route will display parent node_id instead of correct node_id When editing in frontend siteaccess using PathPrefix and RootNode route will display parent node_id instead of correct node_id
          Joao Inacio (Inactive) made changes -
          Description While testing [EZP-23725], I've found out that after publishing the "News" folder, using the frontpage will break the

          {code}
          content:
              tree_root:
                  location_id: 142
          {code}

          setting.

          Steps:

          1. On the admin interface, create folder A
          2. Inside folder A, create folder B
          3. Take note of folder's B node_id
          4. In ezpublish.yml, on the default site access, add
          content:
              tree_root:
                  location_id: node_id
          5. Access to your site frontpage
          6. Login
          7. Edit "Folder" B and publish it
          8. Instead of displaying folder B it will display folder A

          *Workaround*
          1. Login into admin interface
          2. Edit forlder B and publish it
          While testing [EZP-23725], I've found out that after publishing the "News" folder, using the frontpage will break the

          {code}
          content:
              tree_root:
                  location_id: 142
          {code}

          setting.

          Steps:

          1. On the admin interface, create folder A
          2. Inside folder A, create folder B
          3. Take note of folder's B node_id
          4. In ezpublish.yml, on the default site access, add
          content:
              tree_root:
                  location_id: node_id
          5. Access to your site frontpage
          6. Login
          7. Edit "Folder" B and publish it
          8. Instead of displaying folder B it will display folder A

          *Workaround*
          1. Login into admin interface
          2. Edit folder B and publish it
          André Rømcke made changes -
          Epic Link EZP-24117 [ 44189 ]
          Joao Inacio (Inactive) made changes -
          Fix Version/s Customer request [ 11018 ]
          Joao Inacio (Inactive) made changes -
          Status Confirmed [ 10037 ] InputQ [ 10001 ]
          Show
          Joao Inacio (Inactive) added a comment - PR: https://github.com/ezsystems/ezpublish-legacy/pull/1148
          Joao Inacio (Inactive) made changes -
          Status InputQ [ 10001 ] Development [ 3 ]
          Assignee Joao Inacio [ joao.inacio@ez.no ]
          Joao Inacio (Inactive) made changes -
          Status Development [ 3 ] Development Review [ 10006 ]
          Bertrand Dunogier made changes -
          Assignee Joao Inacio [ joao.inacio@ez.no ] Jérôme Vieilledent [ jerome.vieilledent@ez.no ]
          Hide
          Bertrand Dunogier added a comment -

          Jerome will investigate joao's and andre's ways, and provide his conclusions.

          Show
          Bertrand Dunogier added a comment - Jerome will investigate joao's and andre's ways, and provide his conclusions.
          André Rømcke made changes -
          Status Development Review [ 10006 ] Development Review done [ 10028 ]
          Hide
          André Rømcke added a comment - - edited

          Closing as duplicate of EZP-23725, moving that one back to InputQ

          Show
          André Rømcke added a comment - - edited Closing as duplicate of EZP-23725 , moving that one back to InputQ
          André Rømcke made changes -
          Assignee Jérôme Vieilledent [ jerome.vieilledent@ez.no ]
          Status Development Review done [ 10028 ] Closed [ 6 ]
          Resolution Duplicate [ 3 ]
          André Rømcke made changes -
          Resolution Duplicate [ 3 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          André Rømcke made changes -
          Status Reopened [ 4 ] Closed [ 6 ]
          Resolution Duplicate [ 3 ]
          André Rømcke made changes -
          Workflow eZ Engineering Scrumban Workflow [ 66398 ] EZ* Development Workflow [ 85762 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 85762 ] EZEE Development Workflow [ 124662 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Confirmed Confirmed
          3m 28s 1 pedro.resende@ez.no 09/Mar/15 1:09 PM
          Confirmed Confirmed InputQ InputQ
          5h 2m 1 joao.inacio@ez.no 09/Mar/15 6:11 PM
          InputQ InputQ Development Development
          40s 1 joao.inacio@ez.no 09/Mar/15 6:12 PM
          Development Development Development Review Development Review
          6d 17h 7m 1 joao.inacio@ez.no 16/Mar/15 11:20 AM
          Development Review Development Review Development Review done Development Review done
          7d 6h 50m 1 André Rømcke 23/Mar/15 6:10 PM
          Development Review done Development Review done Closed Closed
          10s 1 André Rømcke 23/Mar/15 6:10 PM
          Closed Closed Reopened Reopened
          11s 1 André Rømcke 23/Mar/15 6:10 PM
          Reopened Reopened Closed Closed
          32s 1 André Rømcke 23/Mar/15 6:11 PM

            People

            • Assignee:
              Unassigned
              Reporter:
              Pedro Resende (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: