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

path_identification_string is changed in multisite setup

    XMLWordPrintable

Details

    Description

      Editing an object in multisite setup using a frontend editing, when multiple sites are located under the same root node, causes problems while accessing the object from admin interface. This is because path_identification_string is shorten when using the frontent editing.

      Steps to reproduce

      Steps to reproduce:
      1. Create a folder "Websites" under the usual root node (NodeID 2). In my case it becomes NodeID 169.
      2. Create a frontpage "web1" as a subnode of the Website node. In my case it becomes NodeID 184.
      3. Please note the original path_identification_path of the frontpage in database:

      mysql> select contentobject_id, node_id, path_string, path_identification_string  from ezcontentobject_tree where node_id  = 184;
      +------------------+---------+---------------+----------------------------+
      | contentobject_id | node_id | path_string   | path_identification_string |
      +------------------+---------+---------------+----------------------------+
      |              183 |     184 | /1/2/169/184/ | websites/web1              |
      +------------------+---------+---------------+----------------------------+
      1 row in set (0.00 sec)
      

      3. In settings/siteaccess/WEB1/content.ini.append.php set:

      [NodeSettings]
      RootNode=184
      

      4. In settings/siteaccess/WEB1/site.ini.append.php

      [SiteSettings]
      IndexPage=/content/view/full/184
      RootNodeDepth=3
      DefaultPage=/content/view/full/184
      

      5. Go to frontpage http://YOURDOMAIN/WEB1 and edit the frontpage
      6. Please note that original path_identification_string is changed now:

      mysql> select contentobject_id, node_id, path_string, path_identification_string  from ezcontentobject_tree where node_id  = 184;
      +------------------+---------+---------------+----------------------------+
      | contentobject_id | node_id | path_string   | path_identification_string |
      +------------------+---------+---------------+----------------------------+
      |              183 |     184 | /1/2/169/184/ | websites/                  |
      +------------------+---------+---------------+----------------------------+
      1 row in set (0.00 sec)
      

      7. Go back to the administrator interface and check URL of the frontpage node. Please note the URL if invalid and does not allow you to access the node in the same way as you can access other nodes in the system.
      8. Click on the "cog wheel" next to the node name and choose Edit from the popup menu. Republish the node.
      9. Note that the correct path_identification_string is back:

      mysql> select contentobject_id, node_id, path_string, path_identification_string  from ezcontentobject_tree where node_id  = 184;
      +------------------+---------+---------------+----------------------------+
      | contentobject_id | node_id | path_string   | path_identification_string |
      +------------------+---------+---------------+----------------------------+
      |              183 |     184 | /1/2/169/184/ | websites/web1              |
      +------------------+---------+---------------+----------------------------+
      1 row in set (0.01 sec)
      

      Attachments

        Activity

          People

            unknown unknown
            2b274289-6c7c-4b95-a70d-ca6c4a846602@accounts.ibexa.co j h
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: