Print

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

• /Web.config
• /App_Config/Include/Sitecore.Buckets.config
• /App_Config/Include/Sitecore.ContentSearch.config

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

• Web.config 
• Sitecore.Buckets.config 
• Sitecore.ContentSearch.config 

Changes to the Web.config file

The following changes have been made to the Web.config file of Sitecore CMS 7.0 rev. 140120 (Update-4) as compared to the Web.config file of Sitecore CMS 7.0 rev. 131127 (Update-3).

Note: The following steps are related to issues merged from 6.6 Update-7, so you do not need to make these changes if your solution was upgraded to CMS 7.0 from 6.6 Update-7 or later (but you should still update the other 7.0 configuration files as described later in this document):

1. In the <switchingProviders><roleManager> section, add the following two attributes ignoredUserDomains="" and allowedUserDomains="" to the provider with providerName="sql". This step is optional, you can skip it unless you plan to use these attributes.
   
   <provider providerName="sql" storeFullNames="true" wildcard="%" domains="*" ignoredUserDomains="" allowedUserDomains="" />
2. In the <switchingProviders><profile> section, add the following attribute ignoredDomains="" to the provider with providerName="sql". This step is optional, you can skip it unless you plan to use this attribute.
   
   <provider providerName="sql" storeFullNames="true" wildcard="%" domains="*" ignoredDomains="" />
3. In the <settings> section, add the following setting, before the "Indexing.UpdateInterval " setting:
   
   <!--  INDEXING DISABLE DATABASE CACHES
         Indicates whether or not to populate database caches with data retrieved during indexing.
         If true, Sitecore indexes every version and language of the items as usual, but does not cache this item data in the database
         caches. This can reduce the amount of memory used for cached data and improve performance, especially in solutions with a large
         number of items, versions, and languages.
         If false, Sitecore indexes every version and language of the items and caches the item data in the database caches.
         Default value: false
   -->
   <setting name="Indexing.DisableDatabaseCaches" value="false" />
4. In the <settings> section, add the following setting, before the "Languages.AutoRemoveItemData" setting:
   
   <!--  LANGUAGES ALWAYS STRIP LANGUAGE
         This setting specifies if the StripLanguage processor in the <preprocessRequest> pipeline will parse and remove languages from
         the URL, even when the languageEmbedding attribute of the linkProvider is set to "never". You should only change this setting
         to "false" if the default behavior causes problems in your solution.
         Default value: true
   -->
   <setting name="Languages.AlwaysStripLanguage" value="true" />
5. In the <settings> section, add the following setting, before the "Login.DisableChangePassword" setting:
   
   <!--  LOGIN DISABLE AUTOCOMPLETE
         If true, an autocomplete="off" attribute is added on the Sitecore login forms on the /sitecore/login/default.html and
         /sitecore/admin/login.html pages. This is useful, for example, if you don’t want user names to be disclosed when editors
         log into Sitecore on shared/public computers.
         Default value: false
   -->
   <setting name="Login.DisableAutoComplete" value="false" />
6. In the <settings> section, add the following setting, after the "Login.DisablePasswordRecovery" setting:
   
   <!--  LOGIN DISABLE REMEMBER ME
         If true, Sitecore disables the "Remember me" checkbox on the login page.
         Default: false
   -->
   <setting name="Login.DisableRememberMe" value="false" />
7. Note: The following steps should only be performed if you have configured your solution to use the Sitecore serialization event handlers which automatically serialize item changes. If you are using these event handlers, you must add two event handlers to the configuration. Add the following event handler to the <event name="item:copied"> node:
   
   <event name="item:copied">
     <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemCopied"/>
   </event>
   
   
   And add the following event handler to the <event name="item:renamed"> node:
   
   
   <event name="item:renamed">
     <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemRenamed"/>
   </event>

Changes to the Sitecore.Buckets.config

The following changes have been made to the Sitecore.Buckets.config file of Sitecore CMS 7.0 rev. 140120 (Update-4) as compared to the Sitecore.Buckets.config file of Sitecore CMS 7.0 rev. 131127 (Update-3):

1. In the <databases> section, add a new node for the core database (you can add it at any place in the section, but in a clean Sitecore installation the new node is placed before the node with the master database):
   
   <database id="core" singleInstance="true" type="Sitecore.Data.Database, Sitecore.Kernel">
     <Engines.DataEngine.Commands.AddFromTemplatePrototype>
       <obj type="Sitecore.Buckets.Commands.AddFromTemplateCommand, Sitecore.Buckets" />
     </Engines.DataEngine.Commands.AddFromTemplatePrototype>     
   </database>

Changes to the Sitecore.ContentSearch.config

The following changes have been made to the Sitecore.ContentSearch.config file of Sitecore CMS 7.0 rev. 140120 (Update-4) as compared to the Sitecore.ContentSearch.config of Sitecore CMS 7.0 rev. 131127 (Update-3):

1. In the <settings> section, add the following setting (you can add it at any place in the section, but in a clean Sitecore installation the new node is placed before the “ContentSearch.ParallelIndexing.Enabled" setting):
   
   <!--  INDEXING DISABLE DATABASE CACHES
         Indicates whether or not to populate database caches with data retrieved during indexing.
         If true, Sitecore indexes every version and language of the items as usual, but does not cache this item data in the database
         caches. This can reduce the amount of memory used for cached data and improve performance, especially in solutions with a large
         number of items, versions, and languages.
         If false, Sitecore indexes every version and language of the items and caches the item data in the database caches.
         Default value: false
   -->
   <setting name="ContentSearch.Indexing.DisableDatabaseCaches" value="false"/>
2. In the <settings> section , replace the following node:
   
   <!--  PARALLEL INDEXING CORE LIMIT
         Restrict parallel indexing to a certain number of cores.
         ('0' = no limit.)
   -->
   <setting name="ContentSearch.ParallelIndexing.LimitCores" value="3" />
   
   
   with:
   
   
   <!--  PARALLEL INDEXING MAX THREAD LIMIT
         This setting allows you to limit the number of threads used for indexing operations when parallel indexing is enabled.
         If the value is set to 0, there is no limit to the number of threads.
         Default value: 3
   -->
   <setting name="ContentSearch.ParallelIndexing.MaxThreadLimit" value="3" />