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
    Apologies Parthian, you are right, the wiki is not on line with the snippet code and &jsJquery and &jsMooTools are not parameters that can be changed in the snippet call. They can be only changed in the default.config.php file or by initializing a new value in a custom config file. I will update the wiki to precise these elements.

    [EDIT] To take into account &jsJquery replace the line 403 of the current snippet.ajaxSearch.tx by:
        $cfg['jsJquery'] = isset($jsJquery) ? $jsJquery : (isset($__jsJquery) ? $__jsJquery : $dcfg['jsJquery']);



    I’m not exactly sure why but I presume that all references to $(somefunction) no longer work as the jQuery has been remapped to require $jq(somefunction).
    Regarding jquery, with the next release of AS (1.9), I will update the js file (and I will use $jq(function) if needed. For the moment AS 1.8.4 runs with the previous release of jquery. You can change that by updating and modifying the js file.

      • 22704
      • 42 Posts
      coroico

      Grand. We got there in the end. I think if I’d mentioned the Wiki earlier it would have been easier all round.

      Have a good long think about my use of $jq(function). This was a workaround to a special situation. Why not have a chat with some other MODx Gurus to come up with an approach for all snippets that include jQuery code. Particularly in the case where the QM is included. And update some Wiki or Docs as appropriate with the best noConflict advice for MODx.

      Regards

      Parthian