Is this really the version you are looking for? Kentico Xperience 9 Documentation is no longer updated. Use the switcher in the header to choose your product version.
Hotfixes allow you to fix problems in your installation of Kentico. You can download hotfix packages and view the list of fixed bugs on the Kentico DevNet portal (opens in a new tab).
If you have the source code version of Kentico, please see Hotfix Instructions - Kentico 9 Source Code.
Note
Hotfixes are not tested for all possible scenarios, so you may experience issues after applying the hotfix.
Always back up your project files and database before applying a hotfix.
You can only apply the hotfix to complete Kentico projects that use the standard folder structure (the solution file, GlobalAssemblyInfo.cs, the CMS and Lib sub-folders). If you run your website as a deployment of the CMS folder, you need to hotfix the original complete project and then create a new deployment.
By default, the installer places the hotfix into the C:\Program Files\Kentico\<version>\Hotfix<version> folder.
For more information, see Kentico Hotfix and Upgrade Utility.
If you cannot access your web project directly (for example when the project is located on a remote hosting server), you can use the Hotfix Utility to create the updated file structure and then upload them to your web project location.
Navigate to the location where you installed the hotfix (C:\Program Files\Kentico\<version>\Hotfix<version> folder by default).
Run Hotfix.exe from the command line with the /deploy parameter. Set the parameter value based on the installation type you are using:
This launches the Hotfix Utility, which then creates the files and folders necessary for updating a project running on .NET version 4.5 and saves them into the folder chosen in the first step of the Hotfix Utility wizard.
Additionally, you can provide the /path parameter to specify the location where the application creates the updated files. This way you do not need to set the path in the first step of the Hotfix Wizard. You can supply the /path parameter in two different formats – relative, which represents a folder in the location from which the utility was executed; or absolute, which can be any path to a local disk.
Example: Hotfix.exe /deploy=net45site /path=Deploy
This launches the Hotfix Utility, which then creates a folder named Deploy in the directory from which the utility was executed and copies all files and folders necessary for updating a project running on .NET version 4.5 into that folder.
Once you have the update files ready, take your website offline. You can do this by copying the App_Offline.htm file from the hotfix installation directory into the root of the remote web project.
Upload the update files created by the Hotfix Utility into your remote web project's CMS folder (overwrite the original files).
Important
If you have previously modified some of the Kentico project files (such as web parts or administration interface files), DO NOT OVERWRITE these files. You could lose your modifications.
You need to compare the modified files with the new versions and make appropriate changes manually.
Manually execute the hotfix SQL scripts on your Kentico database.
Bring your website back online (delete the App_Offline.htm file).
For more information, see Kentico Hotfix and Upgrade Utility.
If you cannot access your web project directly (for example when the project is located on a remote hosting server), you can use the Hotfix Utility to create the updated file structure and then upload them to your web project location.
Navigate to the location where you installed the hotfix (C:\Program Files\Kentico\<version>\Hotfix<version> folder by default).
Run Hotfix.exe from the command line with the /deploy parameter. Set the parameter value based on the installation type you are using:
This launches the Hotfix Utility, which then creates the files and folders necessary for updating a project running on .NET version 4.5 and saves them into the folder chosen in the first step of the Hotfix Utility wizard.
Additionally, you can provide the /path parameter to specify the location where the application creates the updated files. This way you do not need to set the path in the first step of the Hotfix Wizard. You can supply the /path parameter in two different formats – relative, which represents a folder in the location from which the utility was executed; or absolute, which can be any path to a local disk.
Example: Hotfix.exe /deploy=net45app /path=Deploy
This launches the Hotfix Utility, which then creates a folder named Deploy in the directory from which the utility was executed and copies all files and folders necessary for updating a project running on .NET version 4.5 into that folder.
Once you have the update files ready, take your website offline. You can do this by copying the App_Offline.htm file from the hotfix installation directory into the root of the remote web project.
Upload the update files created by the Hotfix Utility into your remote web project's CMS folder (overwrite the original files).
Important
If you have previously modified some of the Kentico project files (such as web parts or administration interface files), DO NOT OVERWRITE these files. You could lose your modifications.
You need to compare the modified files with the new versions and make appropriate changes manually.
Manually execute the hotfix SQL scripts on your Kentico database.
Open the project in Visual Studio and build the solution.
Bring your website back online (delete the App_Offline.htm file).
In the case of websites hosted on Microsoft Azure, you need to apply the hotfix to your local copy of the web application and then redeploy.
Run Kentico Hotfix Utility (Hotfix.exe) from the location where you installed the hotfix (C:\Program Files\Kentico\<version>\Hotfix<version> folder by default).
Select the folder containing your local version of the project using the Browse button or type in the path to the project manually.
Use the utility to back up your project files and/or database in case you have not already done so.
Select whether you want to update files, database or both. If your database is hosted on SQL Azure, you need to update it manually.
Click Next to start the hotfix procedure.
After the update finishes, click Next to view any problems that may have occurred and the instructions to solve them.
Open the project’s solution in Visual Studio and rebuild it.
Redeploy the application to Microsoft Azure.
If your website’s database is hosted on SQL Azure, manually execute the hotfix SQL scripts against it.
If your website runs as a separate ASP.NET MVC application (in addition to the Kentico administration application), use the following approach to apply the hotfix:
All users who work with the Kentico administration interface should clear the cache in their browsers after applying the hotfix. Otherwise, some features in the administration interface may not be displayed correctly.
Hotfixes provide bug fixes for all files related to the Kentico installation, which includes the installer and other external utilities, such as Kentico Installation Manager, Kentico Service Manager or the Kentico AD Import Utility.
To update these files and utilities, you need to apply the hotfix to the setup files:
The hotfix makes any required changes to the files in the directory where you installed your Kentico setup files.
Disable running of scheduled tasks (using the Settings -> System -> Scheduled tasks enabled setting).
Open the Continuous integration application in the Kentico administration interface.
Click Serialize all objects.
Wait until the serialization process finishes and then re-enable scheduled tasks.
Note: The change may cause some web parts (including non-inherited ones) to have different ordering of properties in the serialized continuous integration data. You can resolve this issue and ensure alphabetical ordering by manually re-saving the property definitions of the given web parts.
Contact management - When the deletion of inactive contacts took longer than 1 minute, the next run of the Delete inactive contacts scheduled task was not set, and the task did not execute again. To fix the problem, you need to apply hotfix 9.0.50 and then manually execute the scheduled task:
For a full list of bugs covered by the hotfix, open the Hotfixes page (opens in a new tab) on DevNet and click Fixed bugs for the appropriate Kentico version.