Details

    • Similar Issues:
      Show 5 results 

      Description

      Steps to reproduce:
      1) Create a structure with a field and set it to "not searchable".
      2) Create an article with that structure; enter 'title' for the title and 'foobar' for the previously created field.
      3) Search for 'foobar'
      Expected behavior: The article is not found.
      Actual behavior: The article is found.

        Activity

        Hide
        Daniel Reuther added a comment -

        The root cause for this behavior is that the JournalIndexer indexes an article's complete content (in addition to the individual fields that are indexed as well).

        Show
        Daniel Reuther added a comment - The root cause for this behavior is that the JournalIndexer indexes an article's complete content (in addition to the individual fields that are indexed as well).
        Hide
        Michael Saechang added a comment -

        Committed on:
        6.0.x GIT ID: 1b6401a7e92f2a0fdd0d58db544bbf266106fffb.
        6.1.x GIT ID: 3d46c63ebd6233433eef18a52b0bf9f28a8a30ad.
        6.2.x GIT ID: 3f75fd6d035075905983b63074b19ad9d4e3ae33.

        Show
        Michael Saechang added a comment - Committed on: 6.0.x GIT ID: 1b6401a7e92f2a0fdd0d58db544bbf266106fffb. 6.1.x GIT ID: 3d46c63ebd6233433eef18a52b0bf9f28a8a30ad. 6.2.x GIT ID: 3f75fd6d035075905983b63074b19ad9d4e3ae33.
        Hide
        Pani Gui (Inactive) added a comment - - edited

        FAILED Manual Testing following the steps in the description.

        Reproduced on:
        Tomcat 6.0 + MySQL 5. 6.0.12 EE.
        Tomcat 7.0 + MySQL 5. 6.1.10 EE.

        Web content is searchable via structure even though the structure fields as non-searchable.

        Fixed on:
        Tomcat 7.0 + MySQL 5. 6.1.x EE GIT ID: abe28822b902480b1d9b330618089decfe0a8f17.
        Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: a5da61c883c1a0ac5972a978dbcd0a230f85a28b.

        Web content can't be searched if the structure fields as non-searchable.

        Failed on:
        Tomcat 6.0 + MySQL 5. 6.0.x EE GIT ID: 404230204c6cd0906073a68b0b215760bfb12a11.

        Web content still can be searched control panel web content search. It works correctly on Search portlet.

        Show
        Pani Gui (Inactive) added a comment - - edited FAILED Manual Testing following the steps in the description. Reproduced on: Tomcat 6.0 + MySQL 5. 6.0.12 EE. Tomcat 7.0 + MySQL 5. 6.1.10 EE. Web content is searchable via structure even though the structure fields as non-searchable. Fixed on: Tomcat 7.0 + MySQL 5. 6.1.x EE GIT ID: abe28822b902480b1d9b330618089decfe0a8f17. Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: a5da61c883c1a0ac5972a978dbcd0a230f85a28b. Web content can't be searched if the structure fields as non-searchable. Failed on: Tomcat 6.0 + MySQL 5. 6.0.x EE GIT ID: 404230204c6cd0906073a68b0b215760bfb12a11. Web content still can be searched control panel web content search. It works correctly on Search portlet.
        Hide
        Daniel Reuther added a comment -

        There is a major flaw in the current fix (6.2.x) and it will probably need to be rolled back.

        I guess it might take a few days until a new one is ready.

        Show
        Daniel Reuther added a comment - There is a major flaw in the current fix (6.2.x) and it will probably need to be rolled back. I guess it might take a few days until a new one is ready.
        Hide
        Daniel Reuther added a comment -

        Essentially, the real problem here is the description of the drop-down boxes; they're not meant for influencing the searchability of a field but the "individual indexation".

        That is, searchable fields should be indexed separately while non-searchable fields should only be part of the the complete article content.

        Long story short, this is not a bug.

        Show
        Daniel Reuther added a comment - Essentially, the real problem here is the description of the drop-down boxes; they're not meant for influencing the searchability of a field but the "individual indexation". That is, searchable fields should be indexed separately while non-searchable fields should only be part of the the complete article content. Long story short, this is not a bug.
        Hide
        Corne added a comment -

        The description neither changed in later versions.
        So as translators we should fix this in our language files then?

        Show
        Corne added a comment - The description neither changed in later versions. So as translators we should fix this in our language files then?

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              2 years, 4 weeks, 6 days ago

              Development

                Structure Helper Panel