← Return to doc.sitecore.com

  Config file changes in Sitecore CMS and DMS 7.2 rev. 141226 compared to CMS and DMS 7.2 rev. 140526
Print this page (opens in new window) Print

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

The clean configuration files for Sitecore CMS and DMS 7.2 rev. 141226 can be downloaded using the following links:

Changes to Web.config


The following changes have been made to the Web.config file of Sitecore CMS 7.2 rev. 141226 (Update-3) as compared to the Web.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

  1. In the <sitecore> section add the following node after <events> node:
    <!-- EVENT SETTINGS
        Here is a list of settings for different event types.
        -->
        <eventSettings>
          <!-- SAVED ITEM REMOTE SETTINGS
          The settings that control the item:saved:remote event.
          -->
          <savedItemRemoteSettings type="Sitecore.Events.Settings.SavedItemRemoteSettings, Sitecore.Kernel">
            <!-- INCLUDE FIELDS
                 This setting allows you to specify which fields should be serialized when the item:saved:remote event is triggered
                 and the EventQueue.SavedItemRemote.SerializeAllFields setting is set to 'false'.
            -->
            <!--<include hint="list:IncludeField">
              <Text>{A60ACD61-A6DB-4182-8329-C957982CEC74}</Text>
            </include>-->
            <!-- INCLUDE TEMPLATES
                 This setting allows you to serialize all the fields in a template when the item:saved:remote event is triggered
                 and the EventQueue.SavedItemRemote.SerializeAllFields setting is set to 'false'.
                 The "includeBaseTemplates" attribute allows you to specify whether the fields in the parent templates should also be serialized.
            -->
            <!--<include hint="raw:IncludeTemplate">
              <Standard_Template id="{1930BBEB-7805-471A-A3BE-4858AC7CF696}" includeBaseTemplates="true" />
            </include>-->
            <!-- EXCLUDE FIELDS
                 This setting allows you to specify which fields shouldn't be serialized when the item:saved:remote event is triggered
                 and the EventQueue.SavedItemRemote.SerializeAllFields setting is set to 'true'.
            -->
            <!--<exclude hint="list:ExcludeField">
              <Text>{A60ACD61-A6DB-4182-8329-C957982CEC74}</Text>
            </exclude>-->
            <!-- EXCLUDE TEMPLATES
                 This setting allows you to exclude all the fields in a template from being serialized when the item:saved:remote event is triggered
                 and the EventQueue.SavedItemRemote.SerializeAllFields setting is set to 'true'.
                 The "includeBaseTemplates" attribute allows you to specify whether the fields in the parent templates should also be excluded.
            -->
            <!--<exclude hint="raw:ExcludeTemplate">
              <Sample_Item id="{76036F5E-CBCE-46D1-AF0A-4143F9B557AA}" includeBaseTemplates="false" /> 
            </exclude>-->
          </savedItemRemoteSettings>
        </eventSettings>
  2. In the <scheduling> section, add following agent (after “Sitecore.Tasks.HtmlCacheClearAgent” agent):
    <!-- Agent to remove expired Client authentication tickets  -->
          <agent type="Sitecore.Tasks.CleanupAuthenticationTicketsAgent" method="Run" interval="04:00:00" />
  3. In the <settings> section, add the following setting (between the “EventQueue.PersistStampMaxAge” and “FastQueryDescendantsDisabled” settings):
    <!-- EVENT QUEUE SAVED ITEM REMOTE SERIALIZE ALL FIELDS
               This setting allows you to specify which fields should be serialized when the item:saved:remote event is triggered.
               There are two options:              
               1) Set this setting to 'true' and place all the fields that you would not like to serialize in the 'ExcludeField' list.
               2) Set this setting to 'false' and place all the fields that you would like to serialize in the 'IncludeField' list.
               Default value: true.
          -->
          <setting name="EventQueue.SavedItemRemote.SerializeAllFields" value="true" />
  4. In the <settings> section, add the following setting (between the “ProcessHistoryCount” and “Publishing.AutoScheduleSmartPublish” settings):
    <!--  PROCESSING - MAX DEGREE OF PARALLELISM
                This setting defines the maximum number of locks that can be stored in the LockSet collection that controls parallel execution.
                The classes that use the LockSet collection and are affected by the setting: DataEngine, SQLDataProvider, IndexingProvider,
                SQLServerClientDataStore, SQLServerDataProvider, SqlProxyDataProvider, SQLLinkDatabase, Pipeline, SqlRolesInRolesProvider.
               
                The optimal value for this setting depends on your solution and on the CPU capacity of the server.
                We highly recommend that you perform tests with the expected load before you change this setting in a production environment.
               
                Default value: 256
          -->
          <setting name="Processing.MaxDegreeOfParallelism" value="256" />
  5. In the <settings> section, add the following setting (between the “RecycleBinActive” and “Rendering.ImagesAsXhtml” settings):
    <!--  RENDERING - HTML ENCODED FIELD TYPES
                Specifies a pipe-separated list of field types that should be HTML encoded when rendered by the <renderField> pipeline.
                Default value: text|single-line text
          -->
          <setting name="Rendering.HtmlEncodedFieldTypes" value="text|single-line text" />

Changes to App_Config\Include\Sitecore.ContentSearch.config


The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.config file of Sitecore CMS 7.2 rev. 141226 (Update-3) as compared to the App_Config\Include\Sitecore.ContentSearch.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

  1. In the <events> section, add the following nodes (you can add it at any place in the section, but in a clean Sitecore installation the new nodes are placed in the end of the section, after "indexing:end:remote" event):
    <event name="publish:end:remote">
            <handler type="Sitecore.ContentSearch.Events.PublishingEventHandler, Sitecore.ContentSearch" method="OnFullPublishEndRemoteHandler"/>
          </event>
          <event name="publish:end">
            <handler type="Sitecore.ContentSearch.Events.PublishingEventHandler, Sitecore.ContentSearch" method="OnFullPublishEndHandler"/>
          </event>
          <event name="publish:end">
            <handler type="Sitecore.ContentSearch.Events.PublishingEventHandler, Sitecore.ContentSearch" method="OnPublishHandler"/>
          </event>
          <event name="publish:end:remote">
            <handler type="Sitecore.ContentSearch.Events.PublishingEventHandler, Sitecore.ContentSearch" method="OnPublishRemoteHandler"/>
          </event>
          <event name="indexing:updateditem">
            <handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="UpdateIndexTimestampHandler"/>
          </event>
          <event name="indexing:deleteitem">
            <handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="UpdateIndexTimestampHandler"/>
          </event>
          <event name="indexing:deletegroup">
            <handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="UpdateIndexTimestampHandler"/>
          </event>
          <event name="indexing:end">
            <handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="UpdateIndexTimestampDirectHandler"/>
          </event>
          <event name="indexing:committed">
            <handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="UpdateIndexTimestampDirectHandler"/>
          </event>
          <event name="indexing:end:remote">
            <handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="IndexEndedRemoteHandler"/>
          </event>
          <event name="indexing:end:remote">
            <handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="UpdateIndexTimestampDirectHandler"/>
          </event>
          <event name="packageinstall:starting">
            <handler type="Sitecore.ContentSearch.Events.PackagingEventHandler, Sitecore.ContentSearch" method="OnPackageInstallStartingHandler"/>
          </event>
          <event name="packageinstall:poststep:starting">
            <handler type="Sitecore.ContentSearch.Events.PackagingEventHandler, Sitecore.ContentSearch" method="OnPackagePostStepInstallStartingHandler"/>
          </event>
          <event name="packageinstall:items:ended">
            <handler type="Sitecore.ContentSearch.Events.PackagingEventHandler, Sitecore.ContentSearch" method="OnPackageInstallItemsEndHandler"/>
          </event>
          <event name="packageinstall:ended">
            <handler type="Sitecore.ContentSearch.Events.PackagingEventHandler, Sitecore.ContentSearch" method="OnPackageInstallerEndHandler"/>
          </event>

Changes to App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config


The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.2 rev. 141226 (Update-3) as compared to the App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.2 rev. 140526 (Update-2).

  1. In the <analyzer> section, remove the following node, at the end of the section:
    <mapEntry type="Sitecore.ContentSearch.LuceneProvider.Analyzers.PerExecutionContextAnalyzerMapEntry, Sitecore.ContentSearch.LuceneProvider">
                      <param hint="executionContext" type="Sitecore.ContentSearch.CultureExecutionContext, Sitecore.ContentSearch">
                        <param hint="cultureInfo" type="System.Globalization.CultureInfo, mscorlib">
                          <param hint="name">th-TH</param>
                        </param>
                      </param>
                      <param desc="analyzer" type="Sitecore.ContentSearch.LuceneProvider.Analyzers.DefaultPerFieldAnalyzer, Sitecore.ContentSearch.LuceneProvider">
                        <param desc="defaultAnalyzer" type="Lucene.Net.Analysis.Th.ThaiAnalyzer, Lucene.Net.Contrib.Analyzers">
                          <param hint="version">Lucene_30</param>
                        </param>
                      </param>
                    </mapEntry>
  2. In the <fieldTypes> section, change the type of fieldTypeName="number" from:
    type="System.Int32"
    to:
    type="System.Double"
    After the applied change fieldTypeName="number" node should look like:
    <fieldType fieldTypeName="number"                             storageType="NO" indexType="TOKENIZED" vectorType="NO" boost="1f" type="System.Double"   settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider" />