We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 33372
    • 1,611 Posts
    Definitely sounds like an installation problem. Doublecheck that you have the correct versions of the snippet and all files and make sure that the templates.inc.php file in assets/snippets/AjaxSearch/includes exists and is not corrupted. AS should create a default search form for you if it’s installed properly.
      "Things are not what they appear to be; nor are they otherwise." - Buddha

      "Well, gee, Buddha - that wasn't very helpful..." - ZAP

      Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      make sure the snippet is called uncached... [!AjaxSearch? ... !]
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 10449
        • 956 Posts
        Quote from: ZAP at Mar 06, 2008, 12:50 PM

        Doublecheck that you have the correct versions of the snippet and all files and make sure that the templates.inc.php file in assets/snippets/AjaxSearch/includes exists and is not corrupted. AS should create a default search form for you if it’s installed properly.

        It’s version 1.7.0.2
        The local folder-contents and the remote dir-contents are identical.
        I always use the uncached snippet call syntax.

        I DID get a version warning when I first tired it though - not sure why. I just uncommented those few lines.
        I downloaded it from here: http://modxcms.com/AjaxSearch-490.html just yesterday, so I simply ignored the warning.
        I didn’t see any newer versions anywhere...

        o_O
          • 10449
          • 956 Posts
          Here’s more infos: If I re-install the older version (1.6) and run a basic AS call, I see the form, but I get no results.

          If I do "view generated source" via FF, I see the necessary JS has been added. But the spinning icon just keeps on spinning and I don’t get any results whatsoever. There’s tons of content though.

          There is definitely no funky JS anywhere else that could collide with mootools.

          PHP Version 5.2.0-8+etch10
          mySQL Version 5.0.32
          Apache/2.2.3 (Debian)
            • 5811
            • 1,717 Posts
            Not sure but change
            [!AjaxSearch? ajaxSearch=`0` &AS_landing=`249` &moreResultsPage=`249` &showMoreResults=`1` &addJscript=`0` &extract=`0` &AS_showResults=`0`!]
            by:
            [!AjaxSearch? &ajaxSearch=`0` &AS_landing=`249` &moreResultsPage=`249` &extract=`0`!]
            &showMoreResults=`1` &addJscript=`0` are unusefull if you want use the non-ajaxMode. And if you want use the ajax mode &addJscript=`0` means that you load yourself the mootools library. &showMoreResults=`1` have no effects with the non-ajax mode.

            &AS_showResults=`0` is unusefull as you redirect results to the landing page.
              • 5811
              • 1,717 Posts
              A new version of AjaxSearch (Version 1.7.1) is now available in the repository.

              -- CHANGE REQUESTS IMPLEMENTED --

              Advanced search:

              &advSearch [ ’exactphrase’ | ’allwords’ | ’nowords’ | ’oneword’ ]

              - exactphrase : provides the documents which contain the exact phrase
              - allwords : provides the documents which contain all the words
              - nowords : provides the documents which do not contain the words
              - oneword : provides the document which contain at least one word [default]

              In the next version, I will provide a window for the selection of these parameters by the end-user


              Search in hidden documents from menu

              &hideMenu [ 0 | 1 | 2 ]

              - 0 : search only in documents visible from menu
              - 1 : search only in documents hidden from menu
              - 2 : search in hidden or visible documents from menu [default]

              Documents flaged with hidden should only be shown in the result list, if the user wants to.
              http://modxcms.com/forums/index.php/topic,5357.msg144232.html#msg144232]
              Thanks to Toranaga for his contribution.


              - Use the same code between ajax and no ajax mode for the search function. Instanciate a modx object rather than doing direct mysql calls.
              Thanks to Opengeek and SirLancelot for advices

              - With the ajax mode, the complete list of IDs is now hidden in the code source of the page. Only the parents or the documents Ids are visible


              -- ISSUES CORRECTED --

              http://modxcms.com/forums/index.php/topic,5357.msg139525.html#msg139525

              Extract with a % percent character freeze the display of the results output
              Unuseless usage of the decodeURIComponent function in js/ajaxSearch.js (line 162)


              Correction of search with &searchStyle=`relevance`
              Do a full text search (MATCH AGAINST sql statement) in pagetitle, description and content fields. Use LIKE sql statement for others fields.


              -- DEMO SITE --

              Last but not least a demo site is now available at http://www.modx.wangba.fr/

              Be indulgent with the poor design of this site grin, Is it a first draft and it is not the first goal of this site
              And It remains some css issues with IE, not still corrected, so use rather FF.
                • 25663 MODX Staff
                • 12,272 Posts
                Great update and thanks smiley

                Will definitely make it in for 0962.
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                  • 30562
                  • 99 Posts
                  Quote from: coroico at Mar 07, 2008, 07:40 PM

                  A new version of AjaxSearch (Version 1.7.1) is now available in the repository.
                  ...Correction of search with &searchStyle=`relevance`...
                  Hi coroico!
                  My congratulations concerning release of new version AS!

                  I did not understand with the new version for the present. It would be desirable to hear short commentaries concerning the new version.
                  Questions have arisen for me:
                  1. Tell please how is the mechanism of "relevant" search on all words arranged?
                  2. How is the highlighting in relevant search on all words realised?
                  3. I have not seen a russification file. And is it should be?
                    • 5811
                    • 1,717 Posts
                    Hi Traveller

                    1. Tell please how is the mechanism of "relevant" search on all words arranged?
                    See this document : Behind the scene : sql
                    Regarding the "relevant" searchStyle, in doubt, keep the "partial" searchStyle.

                    2. How is the highlighting in relevant search on all words realised?
                    No changes since the 1.7.0.2

                    3. I have not seen a russification file. And is it should be?
                    No change since the version 1.7.0.2. I have begun to implement the changes done by Akots: http://modxcms.com/forums/index.php/topic,18599.msg116964.html#msg116964 But as I got some errors, by lack of time, I didn’t investigate more for the 1.7.1
                      • 30562
                      • 99 Posts
                      Quote from: coroico at Mar 09, 2008, 06:57 PM

                      2. How is the highlighting in relevant search on all words realised?
                      No changes since the 1.7.0.2
                      Correction of highlighting is necessary in case of usage of the landing page of search (non-AS) by search simultaneously all words. Today on this page the quantity of contexts equal to quantity of required terms will be generated. And the one and only context is necessary to display. This context still needs to be isolated accurately that in it there was the greatest quantity of found terms. It is the separate task...

                      This discussion is closed to further replies. Keep calm and carry on.