Feedback
Did this article resolve your question/issue?

   

Article

How to update Sitefinity to hotfix, internal build or a patch

« Go Back

Information

 
TitleHow to update Sitefinity to hotfix, internal build or a patch
URL NameHow-to-update-Sitefinity-to-hotfix-internal-build-or-a-patch
Article Number000177922
EnvironmentProduct: Sitefinity
Version: 5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x, 12.x, 13.x, 14.x
OS: All supported OS versions
Database: All supported Microsoft SQL Server versions
Question/Problem Description
How to update Sitefinity to a Hotfix or a Patch?
How to update to Hotfixes and Patches?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution

An update to a Hotfix or a Patch has the following effects
    - Sitefinity code is modified to fix the issue
    - No database schema changes are made. The database schema is not updated, no new column, no modified columns, no removed columns or tables. The version of the database will be incremented to the version of the Hotfix or a Patch.

Option 1: Update using the Project Manager

1. Download the Hotfix or Patch from your account after logging to http://sitefinity.com go to Account Overview -> Products & Subscriptions -> select Sitefinity CMS -> click Download installer and other resources and to Sitefinity. On this page change the version dropdown to the version required.
User-added image

for Patches switch the tab to Internal builds (see screenshot below).
User-added image

NOTE: the Patches can only download a single version which is the latest released patch for a given Sitefinity version. It contains all fixes from previous Sitefinity patches on the same version. Only the latest patch can be downloaded. In case the patch that is fixing a problem is 11.2.6921, but the latest available patch is 11.2.6932 download it as it contains all fixes from the lower patch versions.

2. After downloading the project manager (it is named ProjectManager_ followed by the number of the corresponding version) Import the project in the newly downloaded Project Manager. For more information on how to use the project manager refer to Sitefinity documentation, Work with Sitefinity CMS Project Manager https://www.progress.com/documentation/sitefinity-cms/work-with-sitefinity-cms-project-manager .
3. Upgrade the project
- open SitefinityCMS.exe this opens Sitefinity CMS Project Manager. The Project manager has three buttons "Create a New Project", "Import a Project" and "Actions". In this case use "Import a Project" and select the radio button option "Open from the project folder". Navigate to the folder of the site which is to be upgraded and click "Done".

NOTE: When the Upgrade button is grayed out in project manager the imported site has a version higher or the same as the version of the project manager. For example:
- using Sitefinity project manager with version 10.0.6400.0 to import a site with version 10.0.6411.0 will have grayed out upgrade button because the site has a higher version than the project manager.
- using Sitefinity project manager with version 10.0.6400.0 to import a site with version 9.2.6228.0 will not have grayed out upgrade button. )


4. right click on the project and select Upgrade

5. Wait for the upgrade to occur, there will be a progress indicator. After the upgrade actions complete. Start the site.

Option 2: Update using NuGet Packages

1. Capture the exact build number of the Hotfix or Patch you need to install.
2. Add the Sitefinity nuget server into the nuget package sources in Visual studio referring on the information in this documentation article: Sitefinity documentation, Sitefinity CMS NuGet packages repository https://www.progress.com/documentation/sitefinity-cms/sitefinity-cms-nuget-packages-repository
Note: refer to the "How to use Sitefinity NuGet Packages" section of the Sitefinity NuGet package repository http://nuget.sitefinity.com/#/home in order to be able to get NuGets from Sitefinity NuGet server.

3. Install the Telerik.Sitefinity.All NuGet package with the required version from the Sitefinity NuGet packages repository. An example NuGet package install comment for a specific version is below:

​Install-Package Telerik.Sitefinity.All -Version 10.1.6521.0

4. Build the project.
5. Run the project.
 
Workaround
Notes
Sitefinity patches are provided as per the bug fixing policy and are available for Sitefinity Enterprise license holders. Patches are created for up to one major version back from the current latest version and contain one or more bug fixes.

Progress Article(s):
 Difference between HotFix and Internal Build
 Where to find the hot fix / internal builds for download

References to Other Documentation:
Sitefinity Developer Network, Welcome http://www.sitefinity.com/developer-network/forums/internal-builds/welcome-2043e465c702
Sitefinity Documentation, Sitefinity CMS NuGet packages repository https://www.progress.com/documentation/sitefinity-cms/sitefinity-cms-nuget-packages-repository
Sitefinity Documentation, Work with Sitefinity CMS Project Manager https://www.progress.com/documentation/sitefinity-cms/work-with-sitefinity-cms-project-manager
Sitefinity, Bug Fixing Policy http://www.sitefinity.com/editions/bug-fixing-policy
Last Modified Date12/3/2021 11:56 AM
Attachment 
Files
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.