We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 5811
    • 1,717 Posts
    Repository updated with the version 1.7.0.1 which takes into account of Jako remarks.
    Minor revision, except if you use a <meta name="version" ...>. See previous posts and ajaxSearch_version_17.txt in the zip file.
      • 30552
      • 75 Posts
      Hello,

      I have AjaxSearch 1.6 running on a site, and I have a major problem that I just can’t seem to figure out, and I think it’s caused by the call to AjaxSearch. I created a sample page to illustrate this problem: https://www.npfunds.com/secure-ssl-test-page. If you browse there in Internet Explorer, you get a message that pops up, saying "This page contains both secure and nonsecure items."

      Firefox does not produce this error message. I think I’ve narrowed the problem down to AjaxSearch.js, but from there, I have no idea what to do. I made all the URLs absolute, just in case, but I can’t figure out what would be throwing this error! I don’t think anything is being called from a http:// source. Does anyone have any ideas? I’ve asked the question before, but can’t get anyone to help, so I thought I would bring it to the "official" AjaxSearch forum.

      Thanks.

      (I was afraid trying to install AjaxSearch 1.7 would complicate matter further, but if this is the recommended course of action, I guess I could do that)
        • 13428 ☆ A M B ☆
        • 1,031 Posts
        Quote from: coroico at Jan 16, 2008, 06:41 AM

        Repository updated with the version 1.7.0.1 which takes into account of Jako remarks.

        Only the issue in Safari is left - thanks smiley

        One big problem could be the change of database_connection_charset to utf8. On all installations I have at the same provider (tested just this one) this causes to see every utf8-encoded char retrieved from the database utf8-decoded (at this moment only in the backend in snippets/chunks/template vars/documents etc.)

        * Server Version: 5.0.27-standard
        * Protokoll-Version: 10
        * MySQL-Zeichensatz: UTF-8 Unicode (utf8)
        * Zeichensatz / Kollation der MySQL-Verbindung: utf8_unicode_ci

        All Databases/Tables/Fields have the collation utf8_unicode_ci.
          • 3177
          • 137 Posts
          I could not get this snippet to work. In the end I solved it by patching the snippet.ajaxSearch.inc.php file in the section "//establish results page". There I had to add a slash "/" in front of the "[" in the value of variable $searchAction.
          Is this a bug or is it something in my configuration that I need that slash there?

          On the site, the User Friendly URL’s are enabled. Probably has something to do with that?

          Hope you can help me out here, because I don’t really like patching this file. (Have to remember this in upgrades...)

          Thanks,

          Bert Catsburg
            • 5811
            • 1,717 Posts
            In the end I solved it by patching the snippet.ajaxSearch.inc.php file in the section "//establish results page". There I had to add a slash "/" in front of the "[" in the value of variable $searchAction.
            Is this a bug or is it something in my configuration that I need that slash there?

            When this possible issue occurs ? After the search when you are displaying results on a landing_page ?
            Could you give me:
            - you snippet call (search page & landing or moreResults page)
            - and url to your search page (on your site or at minimum a catch of the url called)
            - your browser type
            - your connection charset database
            - the version of ajaxSearch you use
              • 5811
              • 1,717 Posts
              @jako :

              Only the issue in Safari is left
              whick kind of issue is it ? You can’t load the search page ? You have javascript errors or some some strange display of charcters due to UTF-8 ?
                • 13428 ☆ A M B ☆
                • 1,031 Posts
                Quote from: coroico at Jan 16, 2008, 05:06 PM

                Only the issue in Safari is left
                which kind of issue is it
                utf8-decoded chars (only in Safari Mac/Windows - in IE/FF/Opera they are utf8-encoded).

                  • 5811
                  • 1,717 Posts
                  in the ajaxSearch mod or with the non-ajaxSearch mode (FLEX) ? did it run before with the 1.6 delivered with Modx0.9.6.1 ?
                    • 13428 ☆ A M B ☆
                    • 1,031 Posts
                    Quote from: coroico at Jan 16, 2008, 05:17 PM

                    in the ajaxSearch mod or with the non-ajaxSearch mode (FLEX) ?
                    Only in ajax-mode.

                    did it run before with the 1.6 delivered with Modx0.9.6.1 ?
                    Sorry, did not made this update before. Now it is installed. But I have a few other installations with AjaxSearch not set to ajax.

                    Could test it tomorrow - now I have to sleep. Thanks for your help.

                      • 3177
                      • 137 Posts
                      Hello,

                      Problem: Had to patch snippet.ajaxSearch.inc.php by adding slashes in from of the results page section.

                      Reacting on Coroico and his request for more info on 16-jan 16:59 (reply #422)

                      - The Snippet call:
                      [!AjaxSearch? &AS_showResults=`1` &AS_showForm=`1` &AS_landing=`60` &ajaxSearch=`0` &showMoreResults=`60` &parents=`2` !]
                      - The url to the search page
                      The url to the search page is chem2.themarketingshop.nl. In the Dutch section, hit the "Zoeken" button
                      at the top. This website is in development, so please do not repost it as an URL. (We don’t want
                      this development site to turn up on the Google index)
                      - Browser is Firefox on WinXP, but problem reproduces on IE on WinXP and Firefox on OS-X. So, it’s browser
                      independant.
                      - The connection charset database. $database_connection_charset = ’latin1’; (Taken from the config.inc.php)
                      When I do a phpmyadmin export of the file, I get the following CREATE DATABASE command back:
                      CREATE DATABASE `chem2` DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci;
                      So, this seems to be in sync.
                      - I use the version 1.7 of the ajaxSearch on a MODX 0.9.6.1 environment.


                      Thanks in advance for your support,

                      Bert Catsburg
                      TheMarketingShop.nl

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