Don't load JQuery on the front-end for QM+ if you're already loading JQuery for something else.
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.
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.
-
- 239 Posts
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?
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