CHunky Universe of Vigourous Astonishing SHarepoint :)
In SharePoint 2010 if CMSSiteManager.js library is loaded besides jQuery, then much of stuff stops working. The reason is that the dollar sign ($) is used in cmssitemanager.js as well which conflicts with jQuery. Mostly it appears on pages where you load jQuery and have an image library with thumbnails. To avoid this, just replace all $ with jQuery in your custom scripts. A more crazy situation is when avoiding $ isn’t enough. It is when you load jQuery to page head automatically on all pages. The Asset picker (AssetPortalBrowser.aspx) invokes $ itself and gets with jQuery in conflict without you write a single line of custom javascript code. You usually get the following error:
Uncaught TypeError: Cannot set property 'display' of undefined
Or in IE:
Unable to set value of the property 'display': object is null or undefined
I found a good solution in Brad Curtis’ blog. Run in your script:
jQuery.noConflict()
Brad Curtis creates an additional script file. But it is okay to have this line in your javascript file, so long you load this every time jQuery is loaded. So put this before your javascript code:
// this puts jquery into no conflict mode //which will remedy conflicts caused by jQuery when used // with certan publishing features jQuery.noConflict();
If you use jQuery.noConflict, the dollar sign ($) is not available anymore! So replace all $ with jQuery. (Unless it is inside modules… another time about that…)
Thanks to Steve’s comment. Please consider to use closures where you pass jQuery as a parameter
(function($) {
//do your jQuery stuff
$(".selector").show();
}
)(jQuery);
Please, keep in mind, the $ in cmssitemanager.js has nothing to do with jQuery, unfortunately it uses the same variable name. The issue applies for SharePoint 2013, too.
 | Holger Küsgens on JSGrid Basics |
 | roshanjv on JSGrid Basics |
 | Filippo Bertuzzi on Export any web part from a Sha… |
| Filippo Bertuzzi on Export any web part from a Sha… |
 | Ben on Export any web part from a Sha… |
 | Fred on Export Any Web Part using a… |
| Fred on Export any web part from a Sha… |
 | Jasveer Singh on Publishing Visio diagrams as h… |
 | Syed Shoaib Adil on Make javascript code work with… |
 | Tess on PowerShell: Copy an entire doc… |
VulaCV - Чăвашла вулаттаракан сайт
And going crazy doing it
My view and thoughts on Productivity and more.
and everything in between
It is a good place to share some SharePoint stories and development practices.
Nikander & Margriet on SharePoint
Blog site of founder, RealActivty - Paul J. Swider
Egyptian & Vodafoner - Senior SharePoint Consultant
Office 365, SharePoint, OnePlace Solutions & Life's Other Little Wonders
Me and My doings!
By Mohit Vashishtha
Erfarenheter, synpunkter och raljerande om Scrum från Jimmy Janlén
SharePoint for everyone
Ryan Dennis is a SharePoint Solution Architect with a passion for SharePoint and PowerShell
The Vision for a Future of Clarity
Treacle tarts for great justice
JavaScript, Web Apps and SharePoint
I don’t like to use the noConflict method. This leads to confusion and is unobvious to use.
I would suggest create a closure function that have a local $ parameter :
this code:
$(function(){
$(“.someclass”).hide();
});
would become :
(function($){
$(function(){
$(“.someclass”).hide();
});
})(jQuery);
This case, there’s no conflict, because the local $ parameter is fed by the actual jQuery object.
HTH
steve
Thanks Steve! That’s correct. Today I would use a closure function for this. When I wrote this blog post for 1,5 years ago, I was quite new to javascript. Appreciate the heads up.
One of my pal highlight me that this construct should be enhanced like this :
var myjQuery = jQuery.noConflict(true);
(function($){
$(function(){
$(“.someclass”).hide();
});
})(myjQuery);
Without the noConflict call, jQuery will work, but the original SP’s $ won’t be restored to its correct value.
hth
Hi there! The issue you’re describing a fix for is causing no end of grief on our internal SharePoint site. With the solution you found from Brad Curtis — when I see the asset picker having these issues — I don’t see any other scripts using jQuery. Only cmssitemanager.js is making use of $(… stuff. Do I then need to find the cmssitemanager.js file and apply the fix within that? Many thanks!
Hi, you should never alter the built-in javascript files in SharePoint. What you should do is to use closures in your code, like Steve (above) says.
That’s cool, thanks. The closures method is a lot tidier too 🙂 So what might you suggest I do when getting this error but do not have additional / custom jQuery code running on the page? Or must there be something I can’t see lurking in there? Would appreciate any thoughts 🙂
@Matthew E Cornish: I think you misunderstood the issue. in the Sharepoint javascript file, the use of $ is not jquery, but a specific SharePoint object. And this is the root cause of the issue, because when a custom code want to use the $ alias of jQuery, it’s not jQuery, but the custom SP object. Either @Anatoly’s or mine solution will actually ensure that calls to $ will be on the jQuery object, and not the SP one.
Pingback: Does Sharepoint 2013 really have a jquery conflict with $? | Question and Answer