It is not all that difficult to rule out such conflicts and extension / template developers can be asked for help then on.
Here is a case study:
- Template A loads Mootools library version 1.5.0
- Plugin B loads own Mootools library version 1.2.6
- Module C loads jQuery library version 1.11
- Component D loads jQuery library version 2.1.1
You can detect the problem by checking which extensions cause the problem, here are the steps:
- Publish your installed extensions one by one and reload your site. Repeat the process until you discover which parts are in conflict.
Put jQuerry into no-conflict mode
The jQuery library and all of its plugins are contained within the jQuery namespace. Global objects are stored inside the jQuery namespace, by the way so you shouldn’t get a clash between jQuery and any other library such as prototype.js, MooTools.
Putting jQuery in no-conflict mode immediately after it is loaded onto the page and before you attempt to use jQuery in the page.
Ask for help from extension provider
My site has different issues?