We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 30562
    • 99 Posts
    more...
      • 5811
      • 1,717 Posts
      Hi traveller,
      The underlined terms are not highlighted, but should highlighted.
      This words: "вдоха", "Вдоха", "ВДОХА " are presented in the different case (or “register”).
      In fact when you search "ВДОХА", ajaxSearch, first convert all the searchterms in minus letters and search in fact "вдоха". And as AjaxSearch do not highlight all the terms of the extract, but only the first. It is not an indexation tool which search and highligth all the terms of a document.
      To understand, go on my personal site and type "voyage" (travel) in the search form. You get some results. Follow the title link of the first result. In the result the search terms appears twice in the text.
      The search results shows one answer in the extract and in the linked page the search term appears many times.
      The goal of the search is to provide the link to the page, not to show all the terms in the extract.

      In the future, perhaps, it could be interesting to add a parameter like &sensitiveCase which take the default value to 0 (Not), but which could also take into account of the letter case.

      The index feature is also planned in the next version, in order to output all the terms of the page, and then jump straight to the extract in the document. But I need some time to think how I could implement that without any performances impact for whose who ask for a simple search feature.

      Assure me "вдоха", "Вдоха", "ВДОХА " all this "registers" means Inhalation wink
        • 30562
        • 99 Posts
        Hi coroico!

        Quote from: coroico at Jan 13, 2008, 03:19 PM

        AjaxSearch do not highlight all the terms of the extract, but only the first.
        Really? It’s so badly. sad
        Dos the second and subsequent highlighting in results occur only thanking by highligth plugin on the fly?

        Quote from: coroico at Jan 13, 2008, 03:19 PM

        The search results shows one answer in the extract and in the linked page the search term appears many times.
        You have not absolutely understood me.
        There is an example (analogue of piece_2.jpg), but for an English word "MODx".
        In that example for searchterm "modx" all words are highlighted in results of search: "modx", "MoDx", "mOdX"...
        Here so!
        That is Russian and French “is discriminated” concerning highlighting of search results in the mismatching case of searchterm ! sad

        Quote from: coroico at Jan 13, 2008, 03:19 PM

        In the future, perhaps, it could be interesting to add a parameter like &sensitiveCase which take the default value to 0 (Not), but which could also take into account of the letter case.
        How are about concerning implementation periods?
          • 13428 ☆ A M B ☆
          • 1,031 Posts
          Maybe there is an issue in ajaxSearch.js (Version 1.7)

          Line 40: exit;

          should be

          Line 40: return;




            • 5811
            • 1,717 Posts
            You are right Jako !
            This is not related to the post of Traveller but it’s better to exit with the return statement instead of exit.
            Not sure that it has an impact (only in case of use of depreacated version). I will correct with the next relase.
              • 13428 ☆ A M B ☆
              • 1,031 Posts
              snippet.ajaxSearch.inc.php, Line 313:
              There is a tab at the end of the line (and maybe as strange line-ending) – uploaded with a Mac with Cyberduck and binary-coding this causes an empty line that was only displayed in IE (not in Firefox and Safari).

              ajaxSearch.php, Line 53ff
              ’utf8_general_ci’ => ’UTF-8’,
              should be added

              german.inc.php, Line 16
              $_lang[’as_resultsFoundTextMultiple’] = ’%d Ergebnisse gefunden für "%s".’;

              And a two problems I can’t solve by myself:
              - Safari does not display the proper UTF8-chars in the popup. Firefox does the thing.
              - The Version-Checking of the ajaxSearch.js does not work in IE.

              And a very big problem
              - The search does not work in IE shocked

              Giving up ...
                • 5811
                • 1,717 Posts
                snippet.ajaxSearch.inc.php, Line 313:
                There is a tab at the end of the line (and maybe as strange line-ending) – uploaded with a Mac with Cyberduck and binary-coding this causes an empty line that was only displayed in IE (not in Firefox and Safari).
                Ok I will check it and remove it for the next delivery.

                ajaxSearch.php, Line 53ff
                ’utf8_general_ci’ => ’UTF-8’,
                should be added
                Here we speak about a mapping between the connexion charset of the database and the html page. We don’t speak of the collation. utf8 is enougth.

                german.inc.php, Line 16
                $_lang[’as_resultsFoundTextMultiple’] = ’%d Ergebnisse gefunden für "%s".’;
                Ok, I will correct this typo (für instead of fürr) in the last delivery.


                And a two problems I can’t solve by myself:
                - Safari does not display the proper UTF8-chars in the popup. Firefox does the thing.
                Which version of safari do you use it ? here a post about Safari, not sure that is the same trouble.

                - The Version-Checking of the ajaxSearch.js does not work in IE.
                Tested with IE6 and IE7. I don’t know how you get this issue. You can redo the same test on my site. try chine or voyage as search words

                And a very big problem
                - The search does not work in IE
                Tested with IE6 and IE7. Find enclosed an image of this test and the results on my own site. Again, I don’t know how you get this issue.

                If you want some help, could you give us more informations. Many thanks.
                  • 5811
                  • 1,717 Posts
                  @ All
                  The wiki documentation of AjaxSearch 1.7 is now available at http://wiki.modxcms.com/index.php/AjaxSearch

                  Thanks for your help to improve it (typo and lack of understanding)
                    • 20289
                    • 958 Posts
                    Wow, thats the one i have been waiting for, thanks... keep up a good work :-]
                      [img]http://i10.tinypic.com/52c4eir.gif[/img][/td]
                      [td][Wiki] [Persian support forum]
                      [SVN] [RTL SVN Branch] [bugs] [FishEye+Crucible] [Learn MODx!] | [My Google Code]
                      [font=tahoma][برای دسترسی به راهنمای فارسی به [url=http://www.modxcms.ir]
                      • 5811
                      • 1,717 Posts
                      @jako - The search 1.7 does not work in IE

                      One nigth later ... I think that the troubles regarding IE and may be Safari explained in your previous post have been corrected since this post .
                      If in your js/ajaxSearch.js file you have the line:
                      const _base = 'assets/snippets/ajaxSearch/';

                      you need to change const by var :
                      var _base = 'assets/snippets/ajaxSearch/';
                      or download again the AjaxSearch170 zip file from the repository

                      Thanks for your feedback about your troubles

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