Uploaded image for project: 'Alfresco One Platform'
  1. Alfresco One Platform
  2. ACE-5782

Search Manager - "Site" filter property not working

    Details

      Description

      Search Manager "Site" filter property not working.

      Steps to reproduce

      1. Login to Share as a user who has Search Manager permissions
      2. Perform a Search
      3. Click the Search Manager button
      4. Add a new search filter called Location using the Site filter property
      5. Save it.
      6. Perform a new search

      Expected - the new location filter is available listing all the sites that contain results matching the searched for term
      Actual - the location filter is not displayed

      Notes for investigation: In TS Test the property was "SITE" and the facets on the results included the location filter for sites. After updating the filter in the Search Manager the property is displayed as "Site" the Search Results page has now stopped including the location filter created.

      https://tstest.alfresco.com/share/page/dp/ws/faceted-search-config

        Attachments

        1. ACE-5782.docx
          388 kB
        2. ACE5782.png
          ACE5782.png
          80 kB
        3. ACE-5782.png
          ACE-5782.png
          80 kB
        4. ACE-5782-MNT-15457-Fix.docx
          2.45 MB
        5. Facet for site created before 201701GA.png
          Facet for site created before 201701GA.png
          331 kB
        6. Facet for site created with 201701GA.png
          Facet for site created with 201701GA.png
          327 kB
        7. FixedVersion.png
          FixedVersion.png
          218 kB
        8. search_manager_prior to 5.2.png
          search_manager_prior to 5.2.png
          405 kB
        9. search_manager.png
          search_manager.png
          438 kB

          Issue Links

            Activity

            Hide
            ahealey Andy Healey added a comment -

            SHA-2020 is possibly also a result of the underlying problem

            Show
            ahealey Andy Healey added a comment - SHA-2020 is possibly also a result of the underlying problem
            Hide
            ddraper David Draper [X] (Inactive) added a comment - - edited

            This issue has been caused by a change in behaviour shown when listing the available facets. See this screenshot of the JSON response and compare the longqname response for both "site" and "tag"... you'll see that "tag" has a correct longqname of just "TAG" but site now has a fully qualified name and as a result the facets are not requested correctly.

            The list of available facets are requested by the search manager in order to allow the user to select what is faceted on. There have been no changed in the UI - this bug has been introduced by breaking changes in this API

            cc Jamal Kaabi-Mofrad In case he has any insight into this change

            Show
            ddraper David Draper [X] (Inactive) added a comment - - edited This issue has been caused by a change in behaviour shown when listing the available facets. See this screenshot of the JSON response and compare the longqname response for both "site" and "tag"... you'll see that "tag" has a correct longqname of just "TAG" but site now has a fully qualified name and as a result the facets are not requested correctly. The list of available facets are requested by the search manager in order to allow the user to select what is faceted on. There have been no changed in the UI - this bug has been introduced by breaking changes in this API cc Jamal Kaabi-Mofrad In case he has any insight into this change

              People

              • Assignee:
                closedissues Closed Issues
                Reporter:
                ahealey Andy Healey
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: