We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27376
    • 576 Posts
    Quote from: kylej at Jan 26, 2007, 08:21 PM

    do you have quickedit enabled? if the prototype/scriptaculous libraries are included it will cause conflicts with the script. is this a live site I can take a look at?
    That was exactly it! I just tried logging out (to get rid of quickedit) and it works! Thanks a bunch!

    btw, I have a development version running over here (link removed). The CSS still needs a little work, and I’m starved for content right now, but the search is working! smiley

    Thanks again!

    EDIT: So I guess this will be a conflict until MODx completely converts to mootools huh?
      • 26868
      • 15 Posts
      After some tests I’ve a small preleminary result, but I can not really explain why it works :

      in line 147 or AjaxSearch.php I changed :
              if ($needsConvert) {
                  $result = mb_convert_encoding($result, "UTF-8");
              } 

      to
              if ($needsConvert) {
                  $result = mb_convert_encoding($result, "UTF-8");
              } else {
                  $result = utf8_decode($result);
              }


      So to make it work I had to decode utf8. It’s strange because all my site it utf-8 encoded..

      I’ve also figured out a new *encoding* problem : when writing articles with modx, the content are not the same for titles, longtitles, etc... and content, because modx uses FCKEditor for the content and FCK *html encodes* special chars.
      Ajax Search (and probably all olders versions of search snippets) does not search html encoded chars.
      Example : the word : écoute is stored in the database : &eacutecoute...
        • 26693
        • 23 Posts
        Nice work with this, loving the gentle move over to mootools and object orientation that modx is taking. I have one question about this, which version of mootools is it dependent upon?

        Until yesterday mootools revision 83 was the one available on the site and you had to get very lost on the site several times before finding the development version, version 1 was just released and changes the way mootools works slightly, will this search be compatible with mootools 1 from the beginning (as with SmoothGallery and Slightbox) or will a slight rewrite have to be done (as with Slimbox, which is killed by the changes from rv.83 => version 1)?

        With mootools based snippets and stuff becoming more available i can start to move away from prototype on the front end of sites, however once someone is logged into the manager everything revolving around mootools breaks due to the quick edit snippet, which is scary enough for me when i forget why everything is broken, but for a non-internet savvy client it will simply put them off entirely when nothing appears to work and they dont know why. Is the developer of the quick edit (bloody awesome functionality by the way) still around to update and covert it over to mootools? or is this coming anyway due to the move to OO and mootools?

          • 15987
          • 786 Posts
          I just tried it with mootools 1.0 and it works fine. There may still be some issues with safari, but I have no way of testing that and am not sure. Quickedit is getting the mootools makeover as well, so hopefully we can get rid of all of the conflicts.
            • 26693
            • 23 Posts
            Quote from: kylej at Jan 29, 2007, 08:57 PM

            I just tried it with mootools 1.0 and it works fine. There may still be some issues with safari, but I have no way of testing that and am not sure. Quickedit is getting the mootools makeover as well, so hopefully we can get rid of all of the conflicts.

            Decided to check myself and yes it does indeed work fine with version1 in FF2.0. IE6 and 7 both give a js error, Element.protoype.FireEvent is null or not an object, but the script functions. Note: this could be because I’m using the very packed mootools and it does sometimes cause odd errors for no reason.

            Got a mac here too and it works fine in FF on the mac, but in Safari it simply reloads the page with the search bar on (using default snippet call) or if i use the ’sample’ one [!AjaxSearch? &AS_showResults=`0` &AS_landing=`17` &showMoreResults=`1` &moreResultsPage=`17`!] it loads up page id17. I’m not sure how to give you a better idea of what is breaking it in safari.
              • 25663 MODX Staff
              • 12,272 Posts
              FYI, Mootools 1.0 official release (full, compressed build) was committed to SVN tonight, along with a version of QuickEdit that works in Safari/Fx and IE. smiley
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 15987
                • 786 Posts
                I can’t get get the error you are describing in IE7 or IE6, I’m using the fully packed version 1.0 as well. Do you have other js stuff on that page that may be causing this. I’m surprised that the search would still work if it is giving that error.

                If anyone could help troubleshoot the safari issue I would appreciate it since I do not have access to a Mac.
                  • 34017
                  • 898 Posts
                  ryan, did you say there is a quickedit version that is using mootools 1.0? Is there anyway to obtain this?

                  Thanks,
                  Chuck
                    Chuck the Trukk
                    ProWebscape.com :: Nashville-WebDesign.com
                    - - - - - - - -
                    What are TV's? Here's some info below.
                    http://modxcms.com/forums/index.php/topic,21081.msg159009.html#msg1590091
                    http://modxcms.com/forums/index.php/topic,14957.msg97008.html#msg97008
                    • 25663 MODX Staff
                    • 12,272 Posts
                    It’s been committed to the internal 095dev branch, and should be merged to trunk soon.
                      Ryan Thrash, MODX Co-Founder
                      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                      • 26693
                      • 23 Posts
                      Oddly enough this morning i can’t replicate the error either, I have not changed any of the js files on my site at all... quite a mystery, only thing i can think of is the error remaining on the page after logging out of the manager through the quick edit function on the page. However i can’t get the error to appear when logged in either, the joys of web development wink

                      Ryan in order to use the new quick edit will I have to take the entire trunk version or will I be able to just pull out the quickedit module and replace it? Thinking once that is up then there is nothing preventing me from going the whole cow and removing proto/scriptaculous from this site altogether.