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

QuickManager QM conflict with jQuery

    • 29201
    • 239 Posts
    TAIYO Reply #1, 11 years ago
    I've been able to fix the jQuery conflicts with QM on other builds but can't seem to crack this one. Right now I can get QM+ 1.5.5 to work with the modal window (this is one of the biggest features that keeps me with with Evo) but it jacks up my main navigation menu as seen http://cl.ly/image/0r1o3M0f3B3M.

    Here's the javascript i'm calling

            <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js" type="text/javascript"></script>
	<script src="./includes/plugin/slider/jquery.flexslider-min.js" type="text/javascript"></script>
	<script src="./includes/plugin/prettyphoto/js/jquery.prettyPhoto.js" type="text/javascript"></script>
	<script src="./includes/plugin/jsocial/jquery.jsocial.js" type="text/javascript"></script>
	<script src="./includes/js/plugins.library.js" type="text/javascript"></script>	
	<script src="./includes/js/init.js" type="text/javascript"></script>


    and here's my QM configuration:

    http://cl.ly/image/0I2d0F3b1p2f

    My URL: http://era.taiyoagency.com/

    I've experimented with with referencing jquery1.9.1.min.js via QM without success and even 1.10. Not sure what else to try.

    Can anyone offer any help?

    Thank!
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      sottwell Reply #2, 11 years ago
      Don't load JQuery on the front-end for QM+ if you're already loading JQuery for something else.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 29201
        • 239 Posts
        TAIYO Reply #3, 11 years ago
        Hi Susan and thanks! When I switch Load in Front End to false it breaks my navigation menu http://cl.ly/image/2p1f0W1K0Z3s and it fails to load the Modal window when editing a page from QM...instead it takes you straight to the Manager.
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          sottwell Reply #4, 11 years ago
          Does your menu work if you disable QM+? Generally, what I always did was to get the menu working, then load QM without loading its own version of JQuery.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 29201
            • 239 Posts
            TAIYO Reply #5, 11 years ago
            Yes menu works with QM+ disabled.

            I can get everything working with the following QM configuration:

            http://cl.ly/image/260y0P1h0w1T

            ...except the subnavigation gets stuck after mouse over on a top tier element as seen here:

            http://cl.ly/image/1C1b3k2G2u0p [ed. note: taiyo1578 last edited this post 11 years ago.]
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              sottwell Reply #6, 11 years ago
              If you have one version of JQuery loaded in your template (for the menu) and have QM+ loading its own version of JQuery it will cause problems.
                Studying MODX in the desert - http://sottwell.com
                Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                Join the Slack Community - http://modx.org
                • 29201
                • 239 Posts
                TAIYO Reply #7, 11 years ago
                Ok. I'm using Google's jquery in the TPL: <script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js" ></script>

                ...shouldn't I be able to tell QM+ to reference the same file or same version of Google's script stored locally? I would think that would not conflict?

                  • 28042 ☆ A M B ☆
                  • 24,524 Posts
                  sottwell Reply #8, 11 years ago
                  If you are loading a JQuery library in your template then it's already there for QM+ to use. It's possible that QM+ has a problem with JQuery 1.11, you might try loading the Jquery Migrate plugin, which helps in compatibility problems. https://github.com/jquery/jquery-migrate/#readme
                    Studying MODX in the desert - http://sottwell.com
                    Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                    Join the Slack Community - http://modx.org
                    • 29201
                    • 239 Posts
                    TAIYO Reply #9, 11 years ago
                    I spent a half hour trying different combinations with the migrate code in the template.

                    I placed 

                    <script src="http://code.jquery.com/jquery-1.9.0.js"></script>
<script src="http://code.jquery.com/jquery-migrate-1.2.1.js"></script>


                    at the end of js as seen here: http://cl.ly/image/1m270C2v0v2y

                    and I experimented with not loading jQuery in the front end and got various errors in the console which I'm afraid I'm not much good at debugging.

                    Here's a few of the errors I see:

                    http://cl.ly/image/2I232g3v1P1D