--- title: Hotfix Instructions - Kentico 8 --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). 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](http://devnet.kentico.com/download/hotfixes). > **Info:** If you have the source code version of Kentico, please see [Hotfix Instructions - Kentico 8 Source Code](https://docs.kentico.com/k8/installation/hotfix-instructions-kentico-8/hotfix-instructions-kentico-8-source-code.md). > **Note:** **Note** > > Hotfixes are not tested for all possible scenarios, so you may experience issues after applying the hotfix. > > Always **backup your project files and database** before applying a hotfix. ## Table of Contents ## Applying the hotfix to web site projects ### Local installation 1. If your system stores virtual objects on the file system (due to enabled [Deployment mode](https://docs.kentico.com/k8/deploying-websites/deployment-mode-for-virtual-objects.md) or source control options), return the files to the database. You can re-enable deployment mode or source control after you apply the hotfix. 2. Run **Kentico Hotfix Utility (Hotfix.exe)** from the location where you installed the hotfix. 3. Select your project installation folder using the **Browse** button or type in the path to the project manually. 4. Use the application to back up your project files and/or database if you haven’t already done so. 5. Select whether you want to update files, database or both. It is recommended to update both the project files and the database. 6. Choose a method of taking the project offline and back online. 7. Click **Next** to start the update procedure. 8. After the update finishes, click **Next** to view any problems that may have occurred and the instructions to solve them. For more information, see [Kentico Hotfix and Upgrade Utility](https://docs.kentico.com/k8/external-utilities/kentico-hotfix-and-upgrade-utility.md). ### Remote installation If you cannot access your web project directly (e.g. 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.  1. Run **Hotfix.exe** from the command line with the **/deploy** parameter. Set the parameter value based on the installation type you’re using: - **net40site** - web site project using .NET version 4.0 - **net45site** - web site project using .NET version 4.5\ Example: _Hotfix.exe /deploy=net40site_ This launches the Hotfix Utility, which then creates the files and folders necessary for updating a project running on .NET version 4.0 and saves them into the folder chosen in the first step of the Hotfix Utility wizard. Additionally, you can provide the **/path** parameter, which tells the application where to create the file structure. This way you won’t have 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=net40site /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.0 into that folder. 2. 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. 3. Upload the update files created by the Hotfix Utility into your remote web project (overwrite the original files). > **Note:** **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. 4. Manually execute the hotfix SQL scripts on your Kentico database. - If you do not use separated databases - run the **Hotfix\_separated.sql**and **Hotfix\_default.sql** script files located in the **SQL** folder of your hotfix installation directory. We recommend running the files in the described order. - If you use [separated databases](https://docs.kentico.com/k8/on-line-marketing-features/contact-management/separating-the-contact-management-database.md) - run the **Hotfix\_separated.sql** script file on the separated database and **Hotfix\_default.sql** on your main database. The script files are located in the **SQL** folder of your hotfix installation directory. 5. Bring your website back online (delete the **App\_Offline.htm** file). ## Applying the hotfix to web application projects ### Local installation 1. If your system stores virtual objects on the file system (due to enabled [Deployment mode](https://docs.kentico.com/k8/deploying-websites/deployment-mode-for-virtual-objects.md) or source control options), return the files to the database. After you apply the hotfix, re-enable deployment mode or source control and rebuild the project. 2. Run **Kentico Hotfix Utility (Hotfix.exe)** from the location where you installed the hotfix. 3. Select your project installation folder using the **Browse** button or type in the path to the project manually. 4. Use the application to back up your project files and/or database if you haven’t already done so. 5. Select whether you want to update files, database or both. It is recommended to update both the project files and the database. 6. Choose a method of taking the project offline and back online. 7. Click **Next** to start the update procedure. 8. After the update finishes, click **Next** to view any problems that may have occurred and the instructions to solve them. 9. Open the project solution in Visual Studio and build the solution. For more information, see [Kentico Hotfix and Upgrade Utility](https://docs.kentico.com/k8/external-utilities/kentico-hotfix-and-upgrade-utility.md). ### Remote installation If you cannot access your web project directly (e.g. 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.  1. Run **Hotfix.exe** from the command line with the **/deploy** parameter. Set the parameter value based on the installation type you’re using: - **net40app** - web site project using .NET version 4.0 - **net45app** - web site project using .NET version 4.5\ Example: _Hotfix.exe /deploy=net40app_\ This launches the Hotfix Utility, which then creates the files and folders necessary for updating a project running on .NET version 4.0 and saves them into the folder chosen in the first step of the Hotfix Utility wizard. Additionally, you can provide the **/path** parameter, which tells the application where to create the file structure. This way you won’t have 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=net40app /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.0 into that folder. 2. 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. 3. Upload the update files created by the Hotfix Utility into your remote web project (overwrite the original files). > **Note:** **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. 4. Manually execute the hotfix SQL scripts on your Kentico database. - If you do not use separated databases - run the **Hotfix\_separated.sql**and **Hotfix\_default.sql** script files located in the **SQL** folder of your hotfix installation directory. We recommend running the files in the described order. - If you use [separated databases](https://docs.kentico.com/k8/on-line-marketing-features/contact-management/separating-the-contact-management-database.md) - run the **Hotfix\_separated.sql** script file on the separated database and **Hotfix\_default.sql** on your main database. The script files are located in the **SQL** folder of your hotfix installation directory. 5. Open the project in Visual Studio and build the solution. 6. Bring your website back online (delete the **App\_Offline.htm** file). ## Applying the hotfix to Windows Azure In the case of websites hosted on Windows Azure, you need to apply the hotfix to your local copy of the web application and then redeploy. 1. Run **Kentico Hotfix Utility (Hotfix.exe)** from the location where you installed the hotfix. 2. Select the folder containing your local version of the project using the **Browse** button or type in the path to the project manually. 3. Use the application to back up your project files and/or database in case you haven’t already done so. 4. Select whether you want to update files, database or both. If your database is hosted on SQL Azure, you need to update it manually. 5. Click **Next** to start the update procedure. 6. After the update finishes, click **Next** to view any problems that may have occurred and the instructions to solve them. 7. Open the project’s solution in Visual Studio and rebuild it. 8. Redeploy the application to Windows Azure. 9. If your website’s database is hosted on SQL Azure, manually execute the hotfix SQL scripts against it. - If you do not use separated databases - run the **Hotfix\_separated.sql**and **Hotfix\_default.sql** script files located in the **SQL** folder of your hotfix installation directory. We recommend running the files in the described order. - If you use [separated databases](https://docs.kentico.com/k8/on-line-marketing-features/contact-management/separating-the-contact-management-database.md) - run the **Hotfix\_separated.sql** script file on the separated database and **Hotfix\_default.sql** on your main database. The script files are located in the **SQL** folder of your hotfix installation directory. ## Updating setup files and external utilities This hotfix contains bug fixes for all the files in the Kentico installation. This includes the Web Installer with its associated files and external utilities, such as Kentico Installation Manager or Kentico Service Manager. In order to update these files and utilities, you need to launch the Hotfix utility with an additional parameter - **/setuppath** - which specifies the location where you installed Kentico (typically the _Program Files_ folder). When launched with the parameter, the Hotfix utility offers the option of updating the setup files in the **Change confirmation** step. Example: _Hotfix.exe /setuppath=\*\*"c:\Program Files (x86)\Kentico\8.0"_ launches the Hotfix utility, which then tries to update all original files in the default installation directory. ## Additional notes and workarounds ### General - Custom skin styling - If you use skin files to style tables in the administration interface or on the live site (for example in [Reporting](https://docs.kentico.com/k8/configuring-kentico/working-with-system-reports.md) tables), replace the **asp:GridView** control with **cms:UIGridView**. ### Hotfix 8.0.1 - Geolocation - [geolocation](https://docs.kentico.com/k8/on-line-marketing-features/contact-management/working-with-contacts/using-geolocation-for-contacts.md) might not have worked properly when using the **Publish** function in Visual Studio to publish the website to a server (including Windows Azure). To fix this issue: 1. In the Solution Explorer in Visual Studio, navigate to the **CMS/App\_Data/CMSModules/WebAnalytics/MaxMind/GeoLiteCity.dat** file. 2. Set the file's Build action to **Content**. ### Hotfix 8.0.4 - Groups - hotfix 8.0.4 overwrites the URL of the **View** tab in the editing interface of [group](https://docs.kentico.com/k8/community-features/groups.md) forum groups. If you use custom content for this tab, you need to reconfigure the given UI element after you apply the hotifx. ### Hotfix 8.0.5 - Scheduled tasks - to ensure that the Windows service for executing [scheduled tasks](https://docs.kentico.com/k8/configuring-kentico/scheduling-tasks.md) works correctly, apply hotfix 8.0.5 and use the [Kentico Service Manager](https://docs.kentico.com/k8/external-utilities/kentico-service-manager.md) utility to reinstall the scheduler service. ### Hotfix 8.0.6 - Macros - if you experience problems with [macro rules](https://docs.kentico.com/k8/macro-expressions/writing-macro-conditions/building-conditions-using-macro-rules.md) not working correctly after you [re-sign macros](https://docs.kentico.com/k8/macro-expressions/macro-troubleshooting/working-with-macro-signatures.md) in the system, apply hotfix 8.0.6. To fix the broken expressions, you need to add the macro rules again into the given fields. You can find the problems using the **System -> Macros -> Report** interface (enable the **Report problems** option). ### Hotfix 8.0.9 - Macros - re-signing macros after applying hotfix 8.0.6 caused macros inside field validation rules to become invalid. Applying hotfix 8.0.9 fixes both the macro re-signing process and all occurrences of broken field validation macros. ### Hotfix 8.0.10 - After applying hotfix 8.0.10 on _**web application**_ projects, you need to manually include the following new files into the **CMSApp** project in Visual Studio: - CMSScripts\CMSModules\AdminControls\DocumentsGrid.js - CMSScripts\CMSModules\CMS\GridActions.js - CMSScripts\CMSModules\CMS.Blogs\BlogsGrid.js - CMSScripts\CMSModules\CMS.EventManager\EventsGrid.js - CMSScripts\CMSModules\CMS.MessageBoards\MessageBoardsGrid.js ### Hotfix 8.0.12 - After applying hotfix 8.0.12 on _**web application**_ projects, you need to open Visual Studio and manually include the following files: **CMSApp** project: - CMSModules\Groups\Tools\Group\_Edit\_CustomFields.aspx - CMSModules\Groups\Tools\Group\_Edit\_CustomFields.aspx.cs - CMSModules\Groups\Tools\Group\_Edit\_CustomFields.aspx.designer.cs**CMSApp\_AppCode** project: - Old\_App\_Code\CMSModules\Groups\GroupEditTabsExtender.cs ### Hotfix 8.0.14 - Passwords - after applying hotfix 8.0.14, form fields using the **Password** [form control](https://docs.kentico.com/k8/custom-development/developing-form-controls.md) validate input according to the [password policy](https://docs.kentico.com/k8/securing-websites/designing-secure-websites/securing-user-accounts-and-passwords/password-strength-policy-and-its-enforcement.md) settings in **Settings -> Security & Membership -> Passwords**. If you wish to create a password field that does not enforce the password policy, use the **Encrypted password** or **Form password** form controls. ### Hotfix 8.0.15 - E-commerce - The **ShoppingCartContainsAllOfProducts** and **ShoppingCartContainsAnyOfProducts** [macro methods](https://docs.kentico.com/k8/macro-expressions/macro-syntax.md) were added, and can be used to check whether multiple products were added to the shopping cart. You can use the methods to create a variation of the default _Shopping cart contains product_ Order discount macro rule, which does not work for more than one product. ### Hotfix 8.0.19 - Facebook integration - Hotfix 8.0.19 provides an update for the **Facebook comments** web part, which allows enforcement of a specific URL protocol to avoid separation of comment threads. To import the new version of the web part: 1. Apply hotfix 8.0.19. 2. Open the **Sites** application. 3. Click **Import site or objects**. 4. Import the _FacebookComments\_WebPart_ package (select the appropriate version for your web project type) and overwrite the original web part. ### Hotfix 8.0.21 - Web analytics - After applying hotfix 8.0.21, the system is able to log the **Referrals** and **Referring sites** statistics with query string parameters preserved in the URLs. To enable this behavior, use the **CMSWebAnalyticsRemoveReferralQuery** web.config key and set it to ‘false’. The system then no longer aggregates **Referrals** and **Referring sites** from the same source with different query string parameters into a single URL. ## Fixed bugs For a full list of bugs covered by the hotfix, open the [Hotfixes page](http://devnet.kentico.com/download/hotfixes) on DevNet and click **Fixed bugs** for the appropriate Kentico version.