Did this article resolve your question/issue?



Upgrading the version of jQuery

« Go Back


TitleUpgrading the version of jQuery
URL Nameupgrading-the-version-of-jquery
Article Number000134239
EnvironmentProduct: Sitefinity
Version: 7.x, 8.x, 9.x, 10.x, 11.x, 12.x,13.x
OS: All supported OS versions
Database: All supported Microsoft SQL Server versions
Question/Problem Description
Is it possible to upgrade the version of jQuery used by Sitefinity?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number

The jQuery version used in Sitefinity has been upgraded to 3.4.1 in Sitefinity 13.0. Upgrade to Sitefinity 13.0 to use jQuery version 3.4.1.

For Sitefinity versions up to and including 12.2


  • Classic Interface:

Upgrading the JQuery version that Sitefinity uses is not recommended. Upgrading the version leads to issues with the backend functionality of the Website. An example of a malfunction can be viewed in Progress Article:  Backend page editor buttons not working

  • New Interface: 

Sitefinity 11.0 comes with a partially redesigned backend, administrative UI. This UI is based on the latest versions of Angular (instead of jQuery). With its delivery, the utilization of jQuery is significantly reduced, but not eliminated. 


Changing the jQuery version for the Frontend of the site can be done by updating the references in the main layout file or master page file. Layout files (*.cshtml) represent the base page templates for MVC-based pages. Master pages (*.master) represent the base page templates for WebForms-based pages. Changing the version in those may lead to some of the built-in Sitefinity widgets not working as expected. This is a list of built-in MVC widgets that rely on jQuery:

  • All form field controls and the Form widget
  • Calendar
  • Comments
  • Image gallery
  • Language selector
  • Lists
  • Login form
  • Login status
  • Navigation
  • Profile
  • Registration
  • Search
  • Video gallery
When using one of the above widgets and trying to upgrade the jQuery version the respective widget templates need to be updated to ensure compatibility. For information on modifying built-in widget templates refer to Sitefinity Documentation, Create and edit widget templates

Note: A conflict with the embedded version of jQuery and the custom jQuery version might occur, as Sitefinity will inject the default jQuery version for some built-in widgets on the page. This can cause problems and errors in the javascript and the way to avoid it is to use the following approach: Sitefinity documentation,  Avoid conflicts when loading multiple versions of jQuery,
Since Sitefinity 13.0 the default jQuery version is 3.4.1:
Progress Telerik, Sitefinity CMS 13.0.7300 (Official Release)

References to Other Documentation:
Sitefinity documentation,  New content editing experience and the classic interface 
Last Modified Date11/20/2020 6:53 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.