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

Search Not working correctly after decoupling from Persistence

    Details

      Description

      Since Search functionality was decoupled from Persistence, that it has stopped working correctly. This comes as a regression of the functionality tested at EZP-23403, which worked before.
      Steps to reproduce (ids are for reference only):

      1. Install an independent Solr setup according to the steps on the attached file solrConf.v3.md;

      2. Access legacy admin and go to Content Structure;

      3. Create the following content structure inside "Home":

      TREE        | LOCATION ID |
      FolderA     | 83          |
      » FolderB   | 83/84       | 
      »» FolderB1 | 83/84/86    |
      FolderC     | 85          |
      

      3. Go now to Users;

      4. Create the following user group structure inside user groups root:

      TREE             | CONTENT ID | LOCATION ID |
      User Group A     | 79         | 87          |
      » User Group B   | 79/80      | 87/88       |
      »» User Group B1 | 79/80/81   | 87/88/89    |
      User Group C     | 82         | 90          |
      

      5. Index all created content on Solr;

      TESTING CONTENT:

      6. Using public API or whatever method, move content at location 84 (FolderB) into location 85 (FolderC);

      7. Use Search for finding contents based on Subtree criterion (using as criterion the subtree of location root 83, FolderA, now empty inside).
      Only content of location id 83 itself, FolderA, should be found now, but it won't. FolderB and FolderB1 will still be returned as search results as well.

      8. Use search for finding contents based on Subtree criterion (using as criterion the subtree of location root 85, FolderC, now with the other contents nested in it).
      Both contents of location ids 84 and 86 (FolderB and FolderB1) should be returned, but they won't.

      TESTING USER GROUPS:

      9. Using public API or whatever method, move user group at location 80 (User Group B) into location 82 (User Group C);

      10. Use Search for finding contents based on Subtree criterion (using as criterion the subtree of location root 87, User Group A, now empty inside).
      Only User Group of location id 87 itself, User Group A, should be found now, but it won't. User Group B and User Group B1 will still be returned as search results as well.

      11. Use search for finding contents based on Subtree criterion (using as criterion the subtree of location root 90, User Group C, now with the other User Groups nested in it).
      Both User Groups of location ids 88 and 89 (User Group B and User Group B1) should be returned, but they won't.

      Use the attached bundle for testing, if needed.
      Usage examples:

      Access:
      http://<your_virtual_host>/ezp23403move/location/84/85
      moves content at location 84 into location 85.

      Access:
      http://<your_virtual_host>/ezp23403find/location/83
      returns contents found on subtree of location id 83

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Rui Silva (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 5 hours, 40 minutes
                5h 40m