Summary

The article provides troubleshooting scenarios for the following issues related to site resolving functionality:

• The Navigation bar does not support sites with "virtualFolder" attribute
• The "Final Layout" button becomes disabled
• The "Item not found" page appears when opening the Experience Editor from the Launchpad
• Redirecting to another hostname after changing the language in the Experience Editor
• Incorrect site resolving in the Preview mode
• Users do not have access to restricted pages in the Preview mode

The Navigation bar does not support sites with "virtualFolder" attribute

Description

When configuring a multisite solution by adding extra <site> nodes to the Sitecore.config file, the Navigation bar might not support sites with the specified "virtualFolder" attribute.

Solution

To resolve the issue, proceed as follows:

• For Sitecore XP 8.0.3–8.0.5:
  
  1. Replace the \sitecore\shell\client\Sitecore\ExperienceEditor\Sitecore.ExperienceEditor.js file with this one: Sitecore.ExperienceEditor.js.
  2. Clear the browser cache.
• For Sitecore XP 8.1.0:
  
  1. Replace the \sitecore\shell\client\Sitecore\ExperienceEditor\ExperienceEditor.js file with this one: ExperienceEditor.js.
  2. Clear the browser cache.

The "Final Layout" button becomes disabled

Description

When configuring a multisite solution by adding extra <site> nodes to the Sitecore.config file, the Final Layout button might become disabled.

The issue does not affect Sitecore XP 9.0.0 and later.

Solution

To resolve the issue, proceed as follows:

For Sitecore XP 8.1–8.2:

1. Download and copy the Sitecore.Support.78974.dll assembly into the \bin folder.
2. Download and copy the zSitecore.Support.78974.config file into the \App_Config\Include folder.

The "Item not found" page appears when opening the Experience Editor from the Launchpad

Description

In a multisite solution, the Item not found page might appear when opening the Experience Editor from the Launchpad.

The issue does not affect Sitecore XP 9.0.0 and later.

Solution

To resolve the issue, proceed as follows:

For Sitecore XP 8.0–8.2:

1. Download and copy the Sitecore.Support.88883.101318.dll assembly into the \bin folder.
2. Download and copy the zSitecore.Support.88883.101318.config file into the \App_Config\Include folder.

Redirecting to another hostname after changing the language in the Experience Editor

Description

In a multisite solution, a user might be redirected to another hostname after changing the language in the Experience Editor.

The issue does not affect Sitecore XP 9.1.1 and later.

Solution

To resolve the issue, proceed as follows:

For Sitecore XP 8.0–8.2:

1. Download and copy the Sitecore.Support.88883.101318.dll assembly into the \bin folder.
2. Download and copy the zSitecore.Support.88883.101318.config file into the \App_Config\Include folder.

Incorrect site resolving in the Preview mode

Description

In a multisite solution, when opening a page in the Preview mode from the Content Editor or the Experience Editor (the Page Editor in Sitecore XP 7.5 and earlier), a site might be resolved incorrectly and use the value of the Preview.DefaultSite setting (which is set to "website" by default).

The issue does not affect Sitecore XP 8.1.0 and later.

Solution

To resolve the issue, proceed as follows:

1. Download the patch compatible with the affected product version:
   
   • For Sitecore CMS 6.6.0 Initial Release: Sitecore.Support.321270.321271
   • For Sitecore CMS 6.6.0 Update-1 to Sitecore XP 7.5: Sitecore.Support.321270.321271
   • For Sitecore XP 8.0 and later: Sitecore.Support.321270.321271
2. Copy the Sitecore.Support.321270.321271.dll assembly from the extracted archive into the \bin folder of the website.
3. Copy the Sitecore.Support.321270.321271.config file from the extracted archive into the \App_Config\Include folder of the website.
4. Make the following changes in the \sitecore\shell\Applications\WebEdit\WebEditRibbon.aspx file:
   
   • For Sitecore CMS 6.6.0–7.2 and Sitecore XP 7.5, replace the line
     

     <sc:CodeBeside runat="server" Type="Sitecore.Shell.Applications.WebEdit.WebEditRibbonForm, Sitecore.Client"/>

     with the following line:
     

     <sc:CodeBeside runat="server" Type="Sitecore.Support.Shell.Applications.WebEdit.WebEditRibbonForm, Sitecore.Support.321270.321271"/>

   • For Sitecore XP 8.0 and later, replace the line
     

     <sc:CodeBeside runat="server" Type="Sitecore.Shell.Applications.WebEdit.WebEditRibbonForm, Sitecore.ExperienceEditor"/>

     with the following line:
     

     <sc:CodeBeside runat="server" Type="Sitecore.Support.Shell.Applications.WebEdit.WebEditRibbonForm, Sitecore.Support.321270.321271"/>

   Note: You can use the Preview.ResolveSite setting in the \Website\App_Config\Include\Sitecore.Support.321270.321271.config file for disabling/enabling the patch.

Users do not have access to restricted pages in the Preview mode

Description

When opening a restricted page in the Preview mode, a user cannot access it because the Preview mode works in the context of the extranet\anonymous account.

The issue does not affect Sitecore CMS 7.2 and later.

Solution

To open a restricted page in the Preview mode, try the following alternative approach:

1. In a web browser, enter the name of your website followed by /sitecore into the address bar. For example, http://www.mywebsite.net/sitecore.
2. On the login page, enter your user name and password.
3. Click Log in.

Notes

• Before applying the suggested patches, make sure that the Sitecore solution does not contain .config and .dll files with the same reference numbers.
• Site resolving behavior for multisite solutions can be changed by applying proper configuration settings. For more information, refer to Configuring site resolving logic in multisite solutions.