We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 29902
    • 72 Posts
    I want only to search in pagetitle on our page, but SimpleSearch are not paying any attention to the &docFields=`pagetitle`. Is this a bug? How can I fix it so it only searches in what stands in the &docFields parameter?

    The SimpleSearch version is 1.6.1

    The MODX Revo is 2.2.8

    [[!SimpleSearch? &ids=`12` &idType=`parents` &containerTpl=`containerTplOwnTrips` &tpl=`tplOwnTrips` &depth=`1` &includeTVs=`1` &noResultsTpl=`` &docFields=`pagetitle` &perPage=`1000`]]
      ...I believed it was Friday...
      • 27106
      • 147 Posts
      David Walker Reply #2, 13 years ago
      These are the words no-one ever wants to hear, but ... it works fine for me.
      My call:
      [[!SimpleSearch? &tpl=`tplSimpleSearchBasic` &containerTpl=`tplSimpleSearchContainerBasic` &hideMenu=`2` &docFields=`pagetitle` &exclude=`2,3`]]

      If it makes you feel any better, I cannot get &fieldPotency to work at all.

      Using MODX Revolution 2.2.6-pl (traditional), mySQL 5.1.67 and SimpleSearch 1.6.1 [ed. note: shorewalker last edited this post 13 years ago.]
        David Walker
        Principal, Shorewalker DMS
        Phone: 03 8899 7790
        Mobile: 0407 133 020
        • 45448
        • 1 Posts
        Had the same prob smiley BUT!!!!! i have got solution.
        In your admin control panel go to - SimpleSearch - properties - docFields - ....

        But i guess the parameters you will mention here will work for all SimpleSearch calls in your site

        Good luck smiley

        PS Sorry for my not correct English (not my native language)
          • 33976 ☆ A M B ☆
          • 571 Posts
          No solution to the reported problem here, since it's working as expected on my side, but just to write a note about fieldPotency parameter (since i had some "issue" with it) :

          the way it currently works is it sorts per "page"... let me try to explain.
          Per default, you get 10 results per page, those results are the first resources that match the query (sorted per ID, ASC, if you did not specify sortBy parameter).
          To "ease" the sorting, only those resources are sorted (else the whole matched resources would have to be sorted each time, ie. when changing page).

          This means that if on page 3 you have a resource with higher "rank", it unfortunately won't be displayed on page 1...

          Hope that makes sense