Known issues for Sitecore 8.1

  • Detailed below are the known issues with the Sitecore® Experience Platform™ 8.1.

    For all Sitecore Experience Platform documentation, please visit the Sitecore Documentation Site.

    For information about availability of the fixes for the mentioned known issues, please refer to the Release Notes of the future Sitecore Experience Platform releases.

    Note: This is not a complete list of known issues related to Sitecore 8.1. For additional known issues, please refer to:

    • The confirmation dialog that indicates that an item to be deleted has clones does not appear when deleting an item with clones in the Content Editor.
    • The autocomplete feature in the search interface does not work when using the SOLR search provider from version 4.10.
    • Enabling the SwitchMasterToWeb.config causes a duplicate setting from the Sitecore.Analytics.Tracking.config (75316)
      • This can be worked around by commenting out the “<setting name="Analytics.DefaultDefinitionDatabase" value="master" />” line from the Sitecore.Analytics.Tracking.config file.
    • If your site implementation makes use of Adobe Flash or Adobe Shockwave, you must review the security configuration.
      • The ‘AllowScriptAccess’ attribute specifies the level of script access that a child SWF control has relative to its parent.  By default, this is set to ‘always’.  To apply additional security measures, it is advisable to change the ‘AllowScriptAccess’ attribute from “always” to “sameDomain”.  This will configure the player to only load child files from the same domain as its parent.
    • [Fixed in Sitecore 8.1 Update-1] Clicking the Edit related item buttons opens the wrong language version. (432902, 50086)
    • [Fixed in Sitecore 8.1 Update-1] The page is not refreshed after deleting using the EditFrame command. (351106, 49440)
    • [Fixed in Sitecore 8.1 Update-1] The page is not refreshed after removing datasource item via EditFrame. (387856, 49497)
    • [Fixed in Sitecore 8.1 Update-1] The <h1> tag is added to the title field when you edit an item with the Edit command. (389855, 49502)
    • [Fixed in Sitecore 8.1 Update-1] The Before and After properties of a FieldRender are added to the field value on save. (318619, 94934)
    • [Fixed in Sitecore 8.1 Update-1] The Edit Component Properties command does not properly handle simultaneous editing. (389967, 49503)
    • [Fixed in Sitecore 8.1 Update-1] The placeholder path of a child component is not updated when moving its parent component. (356895, 49453)
    • [Fixed in Sitecore 8.1 Update-1] The [No text in the field] watermark disappears in some cases. (390673, 51577, 62249, 355773, 49451)
    • [Fixed in Sitecore 8.1 Update-1] The page is not refreshed after removing the current version. (71803)
    • DeploymentManager.DeployAll does not deploy to the previous definition tables.(62806)
    • The XDB.Enabled setting does not disable validation link of the Tracking field. (369849, 73165)
    • The SPEAK 2.0 TabControl fails to render tabs appropriately in inconsistent situations. Refreshing the page often resolves the issue. (68589)
    • The SPEAK 2.0 TabControl may throw a process binding error in some very specific configurations. (63928, 59576, 64578)
    • Renderings that use lazy loaded tabs (IsLazyLoaded=true) in the SPEAK 2.0 TabControl must have the PlaceholderKey set to Page.Body, while renderings that use non-lazy loaded tabs (IsLazyLoaded=false) must have the PlaceholderKey left blank. (54808)
    • The SPEAK 2.0 TabControl ignores the IsHidden property on individual tabs. (64955)
    • [Fixed in Sitecore 8.1 Update-1] Renderings are not removed from a placeholder through the Remove component button in the FXM Experience Editor. (72796)
    • Publishing a WFFM form from the FXM Experience Editor does not publish all related items of the form. To publish all form items the user has to publish the appropriate placeholder item in the Marketing Control Panel. (72914)
    • [Fixed in Sitecore 8.1 Update-1] The Save button in not enabled in FXM application in some cases. (72030, 72577, 68866, 65081)
    • The external sites list is empty in the FXM application after opening Experience Editor in debug mode. (60962)
    • When using Chrome, pie charts will sometimes have to be clicked twice when using the drill down capability. (59793)
    • Content testing is not supported in Live mode. Live mode is when the website is run directly from the master database. (28434)
    • When a page test has been saved and you return to the test through the list of draft test, the Pages to test against section will be empty. (73297)
    • Path Analyzer will attempt to rebuild data for all maps after the launch of the Sitecore 8.1 installation. If the XDB is not empty, it may cause an unnecessary rebuild. For more information please refer to the kb article.
    • Path Explorer visualization does not work in the Google Chrome web browser due to their deprecation of Silverlight.
    • Map filter field does not support the following conditions for interaction segmentation. (447869, 447706)
      • Where the ID of the page event is specific value
      • Where the name of the page event compares to specific value
    • Maps are constructed daily based on UTC. Customer specific time zones are not supported. (612)
    • If the default website site map folder has been deleted, then any site maps that are created from the branch template will have unexpected tokens inside Filter field. (1743, 1698)
    • The Re-deploy button for restored map is hidden in Marketing Control Panel until that map is unprotected. (1745)
    • Tree Definition updates possible race conditions when multiple processing servers are used. (1734)
    • The Contacts visited this path list may show incorrect contacts for some paths. (1752)
    • The Page Analyzer is not shown when opening it from the Path Explorer in fullscreen mode. This error occurs only in the Mozilla Firefox web browser. (1759)
    • Some paths in some cases are shown out of visible area in the Page Analyzer. (748)
    • The Segmented list counts do not update when list sources are changed. (72961)
    • Excessive memory use may be encountered when setting a high SearchMaxResults number in a SOLR environment. (53384)
    • When using Internet Explorer 10, a dialog may appear when selecting an Engagement Plan that allows the user to close the browser tab. User should select No to avoid tab closure, or use a different browser. (48238)
    • Due to a SPEAK javascript issue, pages within the application may require reloading. (53384)

Applies to:

CMS 8.1+

October 20, 2015
December 10, 2015


  • CMS,
  • DMS,
  • Experience Editor,
  • Federated Experience Manager,
  • Path Analyzer,
  • Social Connected,