Return to doc.sitecore.com

  Config file changes in Sitecore CMS and DMS 7.2 rev. 160123 compared to CMS and DMS 7.2 rev. 151021

This update requires you to make changes to the following files:

Some small changes (whitespaces, quotes, apostrophes) were fixed in the following files:

Depending on the database you are using, you should also update the appropriate files:

Sitecore solution configured to use MS SQL Server:

Sitecore solution configured to use Oracle:

The following configuration files have been added.

If you use the Lucene search provider:

If you use the Solr search provider:

You can download the clean configuration files for Sitecore CMS and DMS 7.2 rev. 160123:

Configuration file changes

The following changes have been made to the configuration files in Sitecore CMS 7.2 rev. 160123 (Update-6) compared to the configuration files in /App_Config/Commands.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack 2).

Changes in Commands.config

  1. In the <configuration> section, add the following node (you can place it anywhere in the section):

 

  <command name="item:cloneitemwithoutsubitems" type="Sitecore.Shell.Framework.Commands.CloneWithoutSubItems,Sitecore.Kernel" />

 

Changes in MimeTypes.config

  1. Remove or comment out the <mediaType> node:

 

  <mediaType extensions="htm,html,stm"><mimeType>text/html</mimeType></mediaType>

 

Changes in Sitecore.Buckets.config

  1. In the <commands> section, add the following node (you can place it anywhere in the section):

 

       <command name="item:addmaster">

 

        <patch:attribute name="type">Sitecore.Buckets.Pipelines.UI.AddMaster, Sitecore.Buckets</patch:attribute>

       </command>

 

  1. In the <processors> section, add the following node (you can place it anywhere in the section):

 

      <uiAddFromTemplate>

 

        <processor mode="on" type="Sitecore.Buckets.Pipelines.UI.AddFromTemplate.SelectItem" method="Execute" />

      </uiAddFromTemplate>

 

Changes in Web.config

  1. In the <events> section, add the following nodes (you can place them anywhere in the section):

 

      <event name="item:cloneAdded"/>

 

      <event name="item:cloneAdded:remote"/>

 

  1. In the <customHandlers> section, add the following node (you can place it anywhere in the section):

 

      <handler trigger="~/temp/" handler="sitecore_temp.ashx"/>

 

  1. At the end of the <uiCloneItems> section, add the following node. Ensure that the new node is the last node in this section.

 

        <processor mode="on" type="Sitecore.Shell.Framework.Pipelines.CloneItems,Sitecore.Kernel" method="RelinkClonedSubtree"/>

 

  1. In the <processors> section, add the following node (you can place it anywhere in the section):

 

      <uiRemoveLanguage>

 

        <processor mode="on" type="Sitecore.Shell.Framework.Pipelines.RemoveLanguage,Sitecore.Kernel" method="Confirm"/>

        <processor mode="on" type="Sitecore.Shell.Framework.Pipelines.RemoveLanguage,Sitecore.Kernel" method="CheckCloneItems"/>

        <processor mode="on" type="Sitecore.Shell.Framework.Pipelines.RemoveLanguage,Sitecore.Kernel" method="Execute"/>

      </uiRemoveLanguage>

 

  1. In the <sites><site name="service" … /> section, add the “usePreviousSiteName” attribute:

 

      <site name="service" virtualFolder="/sitecore/service" physicalFolder="/sitecore/service" usePreviousSiteName="true"/>

 

  1. In the <sites> section, add the following node between the sites called "service" and the sites called "modules_shell":

 

      <site name="system_layouts" virtualFolder="/layouts/System" physicalFolder="/layouts/System" usePreviousSiteName="true"/>

 

  1. In the <mediaTypes> section, add the following nodes (you can place them anywhere in the section):

 

        <mediaType name="HTML" extensions="htm,html,stm">

 

          <mimeType>text/html</mimeType>

          <forceDownload>true</forceDownload>

          <sharedTemplate>system/media/unversioned/file</sharedTemplate>

          <versionedTemplate>system/media/versioned/file</versionedTemplate>

        </mediaType>

        <mediaType name="SVG image" extensions="svg">

          <mimeType>image/svg+xml</mimeType>

          <forceDownload>false</forceDownload>

          <sharedTemplate>system/media/unversioned/image</sharedTemplate>

          <versionedTemplate>system/media/versioned/image</versionedTemplate>

          <mediaValidator type="Sitecore.Resources.Media.ImageValidator"/>

          <thumbnails>

            <generator type="Sitecore.Resources.Media.SvgThumbnailGenerator, Sitecore.Kernel"/>

          </thumbnails>

          <prototypes>

            <media type="Sitecore.Resources.Media.SvgMedia, Sitecore.Kernel"/>

          </prototypes>

        </mediaType>

 

  1. In the <settings> section, add the following nodes (you can place them anywhere in the section):

 

      <!--  ALLOW DUPLICATE ITEM NAMES ON THE SAME LEVEL

 

            Specifies whether the duplicate item names are allowed on the same level in the content tree.

            Default value: true

      -->

      <setting name="AllowDuplicateItemNamesOnSameLevel" value="true"/>

 

      <!--  CONTENT EDITOR - RENDER ITEM HELP AS HTML

            Specifies whether help information defined in the Item Help section should be treated as an HTML markup.

            If set to false, then the item help information will be encoded before it is rendered.

            If set to true, then the item help information will be cleared of JavaScript code and then rendered as is.

            Default value: false.

            Please note: setting this value to true is unsafe, because it will then be possible to inject any HTML tags (like iframe) and CSS into Sitecore.

      -->

      <setting name="ContentEditor.RenderItemHelpAsHtml" value="false"/>

 

      <!--  CONTENT EDITOR SORT LANGUAGES

            Indicates whether the Content Editor show languages in the language selection dropdown

            in the same order as /sitecore/system/Languages child items.

            Default value: false

      -->

      <setting name="ContentEditor.SortLanguages" value="false"/>

 

      <!--  ITEM CLONING - DELETE CLONES WITH ORIGINAL ITEM

            Specifies whether item clones should be deleted when the original item is deleted.

            If true, when the original item is deleted all its clones are deleted and not just uncloned.

            Default value: false

      -->

      <setting name="ItemCloning.DeleteClonesWithOriginalItem" value="false"/>

 

      <!--  ITEM CLONING - FORCE UPDATE - CHANGE TEMPLATE

            Specify whether clones should be updated automatically when a different template is selected for the original item.

            Note: If true, all the clones of the original item are updated automatically.

            Default value: false

      -->

      <setting name="ItemCloning.ForceUpdate.ChangeTemplate" value="false"/>

 

      <!--  ITEM CLONING - RELINK CLONED SUBTREE

            Indicates that after cloning an item tree structure, all the internal links inside the cloned structure should be re-linked to point to the items in the cloned sub-tree.

            When the setting value is false, the links in the cloned structure will still link to the items in the original structure.

            Default value: false

      -->

      <setting name="ItemCloning.RelinkClonedSubtree" value="false"/>

 

  1. In the <handlers> section, between the "sitecore_icon.ashx" and "sitecore_feed.ashx" handlers, add the following node:

 

      <add verb="*" path="sitecore_temp.ashx" type="Sitecore.Resources.TempRequestHandler, Sitecore.Kernel" name="Sitecore.TempRequestHandler"/>

 

  1. In the <httpHandlers> section, between the "sitecore_icon.ashx" and the "sitecore_feed.ashx" handlers, add the following node:

 

      <add verb="*" path="sitecore_temp.ashx" type="Sitecore.Resources.TempRequestHandler, Sitecore.Kernel"/>

 

Changes in Sitecore.Analytics.config

  1. In the description of the “ANALYTICS MAX QUEUE SIZE” setting, add the following note:

 

            Note: To avoid system overloading make sure that total amount of simultaneously processed rows is less than Analytics.MaxQueueSize

 

                  Analytics.Automation.BatchSize * Analytics.Automation.Threads < Analytics.MaxQueueSize

 

  1. Change the comment and the value for "Analytics.Automation.BatchSize" setting to the following:

 

      <!--  ANALYTICS AUTOMATION BATCH SIZE

 

            Defines the number of records that should be processed in a batch.

            Note: This value should be equal to 1-2% of the Analytics.MaxQueueSize value.

            Default: 100

      -->

      <setting name="Analytics.Automation.BatchSize" value="100" />

 

  1. Change the description for “ANALYTICS AUTOMATION INTERVAL” setting to the following:

 

            Defines how often Sitecore should check if there are Engagement Automation rows ready for processing.

 

  1. In the description of the “ANALYTICS AUTOMATION LOCK EXPIRATION” setting, add the following note:

 

            Note: The time value should be enough to process the Analytics.Automation.BatchSize rows.

 

  1. In the description of the “ANALYTICS AUTOMATION THREADS” setting, add the following note:

 

            Note: Recommended value is the amount of allocated cores on your server.

 

 

  1. In the end of <httpRequestProcessed> section, add the following processor:

 

        <processor type="Sitecore.Analytics.Pipelines.HttpRequest.SetPreviousSiteName,Sitecore.Analytics" />