We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

mootools conflict

    • 10226
    • 412 Posts
    fruitwerks Reply #1, 18 years, 4 months ago
    I am trying to use slideshow2, a moo based slideshow... now when I modx-ify it, it does not work. A quick look in firebug shows two instances of mootools loading, one being in the manager folder. A quick rename of the moo folder in the manager solves the problem. Even on a linux box where I have never logged into the manager, it appears to load both mootools and bork the slideshow.

    I noticed there are multiple mootools .js’s in the mootools manager folder so I am a bit stumped on how to resolve this. The slideshow requires the beta version of mootools, I am sure that is not helping either. Where / why is modx loading mootools from the manager folder to begin with?

    Thanks!
      • 4310
      • 2,310 Posts
      bunk58 Reply #2, 18 years, 4 months ago
      Are you viewing the page whist logged into the Manager and have QuickEdit enabled?
      If so try viewing the page whist not logged in or try in another browser.
        • 10226
        • 412 Posts
        fruitwerks Reply #3, 18 years, 4 months ago
        I have a the server, a linux machine, and a windows machine handy in front of me. I work in the manager under IETab in FF, and I view the page in FF - I know this can get funky at times, so I tried it on a browser and machine that has never ever logged into this manager before, and I go the same results...

        Just created a new login under linux and ran firefox and firebug - it shows the regular mootools and the manager mootools loading, and the slideshow not working. As I mentioned, I can rename the mootools directory on the server and the slideshow and a single copy of mootools loads - well something still tries to load the manager version of mootools, but it is not found, and firebug simply shows the html.

        So without logging into the manager, modx loads mootools from the manager directory. All I can think of is that I have an AjaxSearch call in the template - is that my culprit?
          • 4310
          • 2,310 Posts
          bunk58 Reply #4, 18 years, 4 months ago
          AjaxSearch has a parameter 
          &addJscript=`1`
          but I’m not sure if that just loads 
          <script type="text/javascript" src="assets/snippets/AjaxSearch/AjaxSearch.js"></script>
          into the <head> or if it adds the mootools.js as well. I have mine set to 
          &addJscript=`0`

          QuickEdit definitely adds it 
          <!-- Start QuickEdit headers -->
<script type="text/javascript" src="manager/media/script/mootools/mootools.js"></script>
          etc.
          Again by default I don’t have call to mootools.js in my template.
          You could try saving the beta version as mootools.js in the 
          manager/media/script/mootools/
          folder and see if it will work okay for the Manager functions
            • 10226
            • 412 Posts
            fruitwerks Reply #5, 18 years, 4 months ago
            &addJscript=`0` fixed the issue, but broke the search - I’m not sure if I want a search feature or not at this time. Does anyone know what I need in mootools (beta) for AjaxSearch to work?

            Thanks All!
              • 4310
              • 2,310 Posts
              bunk58 Reply #6, 18 years, 4 months ago
              Do you still have 
              <script type="text/javascript" src="assets/snippets/AjaxSearch/AjaxSearch.js"></script>
              in the <head>?
              Without it the search doesn’t work.
                • 10226
                • 412 Posts
                fruitwerks Reply #7, 18 years, 4 months ago
                Actually, it was never there, but it is now - and still don’t see it. Could be CSS related, but not one of my worries at the moment.

                Thanks!