Avoid conflicts when loading multiple versions of jQuery

By default, Sitefinity CMS uses a built-in copy of the jQuery library. In some cases you may require a different version of jQuery to support a JavaScript library written for a specific version. However, simply including a second version of jQuery may cause unexpected conflicts.

NOTE: To check the current version of jQuery, use the $.fn.jquery property.

To correctly include a version of jQuery that is different than the built-in version, you need to use the jQuery.noConflict() method to wrap your custom logic in a function scope and avoid conflicts:

After loading a second version of jQuery, calling the jQuery.noConflict(true) method restores the globally scoped jQuery variables to those of Sitefinity’s built-in jQuery library. In the code above, the variable jq14 is passed to a function scope. Inside that function scope, Sitefinity CMS version of jQuery is overridden and any code placed in the scope accesses the jQuery version you loaded.

For more information, see jQuery's documentation jQuery.noConflict.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Get started with Integration Hub | Sitefinity Cloud | Sitefinity SaaS

This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.

Web Security for Sitefinity Administrators

This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?