Uploaded image for project: 'Skin Intranet'
  1. Skin Intranet
  2. SKININTRA-78

SearchService switch form full-text criteria to title-or-full-text criteria

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 1.1.2, 1.2.0
    • None
    • None
    • None
    • 4.6 M6

      It will be good to allow to switch easily from 

      user.input.criterion.common$wording$textfield$1 to user.input.criterion.common$titleorwording$textfield$1

      in stylesheets/search.xsl. 

      Either dynamically or through template param

          [SKININTRA-78] SearchService switch form full-text criteria to title-or-full-text criteria

          The name of global search field is now in a XSL variable "searchInputName" you can override in search.xsl

          <!-- +
                   | Name of global search text field :
                   | * use "user.input.criterion.common$wording$textfield$1" if global search service if configured with "Full text" criteria
                   | * use "user.input.criterion.common$titleorwording$textfield$1" if global search service if configured with "Title or full text" criteria
                   + -->
              <xsl:variable name="searchInputName">user.input.criterion.common$wording$textfield$1</xsl:variable>
          

          Laurence Aumeunier added a comment - The name of global search field is now in a XSL variable "searchInputName" you can override in search.xsl <!-- + | Name of global search text field : | * use "user.input.criterion.common$wording$textfield$1" if global search service if configured with "Full text" criteria | * use "user.input.criterion.common$titleorwording$textfield$1" if global search service if configured with "Title or full text" criteria + --> <xsl:variable name="searchInputName">user.input.criterion.common$wording$textfield$1</xsl:variable>

            laurence Laurence Aumeunier
            ogehin Olivier Gehin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: