Known Migration Issues

  • Article

This section describes known issues that may occur when migration your sites to Microsoft Commerce Server 2009 R2.

Known Issues for Default Site

  • Existing Master Page Does Not Incorporate the Ribbon Control

  • Query Strings with User ID Cause Errors

  • Product Details Page Renders Exception

  • Wrong Link Displayed in Product Details Page

  • Write Review Page Displays Errors

  • Access Denied While Writing a Review

  • MyAccount left side bar has broken links

  • Logged-in Shopper cannot navigate to MyAccount site – Access Denied given

  • Add New Address is causing a 404

  • Add Credit Card is causing a 404

  • Two Login Links are appearing on top of the page

  • Search does not return any results

  • Unable to add Commerce user as a site collection administrator

  • Store Locator requires manual configuration

  • Store Locator search displays error

  • Connection String Requires Update

  • Store Locator Page does not render correctly

Known Issues for Contemporary Site

  • My Account Page Does Not Display in a Server Farm

  • Existing Master Page Does Not Incorporate the Ribbon Control

  • Ribbon Background Displayed in Wrong Color

  • Ribbon Embedded in Site

  • Master Page Displays Error in SharePoint Designer

  • Query Strings with User ID Cause Errors

  • Product Details Page Renders Exception

  • Wrong Link Displayed in Product Details Page

  • Write Review Page Displays Errors

  • Access Denied While Writing a Review

  • MyAccount left side bar has broken links

  • Logged-in Shopper cannot navigate to MyAccount site – Access Denied given

  • Add New Address is causing a 404

  • Add Credit Card is causing a 404

  • Two Login Links are appearing on top of the page

  • Search does not return any results

  • Unable to add Commerce user as a site collection administrator

  • Checkout Page is not loading and displays a null reference exception

  • Store Locator requires manual configuration

  • Store Locator search displays error

  • Connection String Requires Update

  • Store Locator has wrong layout

  • Store Locator Page does not render correctly

Known Issues for Contemporary Site with Template Pack for SharePoint 2010

  • Missing Reviews and Rating Images

  • MyAccount left side bar has broken links

  • Add New Address is causing a 404

  • Add Credit Card is causing a 404

  • Two Login Links are appearing on top of the page

  • Search does not return any results

  • Unable to add Commerce user as a site collection administrator

  • Checkout Page is not loading and displays a null reference exception

  • Store Locator requires manual configuration

  • Store Locator search displays error

  • Department link is broken.

  • Connection String Requires Update

  • Store Locator Page does not render correctly

My Account Page Does Not Display in a Server Farm

The SharePoint Commerce Services Configuration utility installs all required files for SharePoint Commerce Services deployment on the machine where the utility is run. If you are deploying the Contemporary Site in a SharePoint server farm environment, you must manually copy the “CommerceMyAccount.sitemap” to “MyAccountLeftNavigation.sitemap ” file (deployed on the first node in the farm by the SharePoint Commerce Services Configuration utility) to every node in the server farm to ensure that the My Account page displays correctly on the contemporary site.

The file is located in the C:\inetpub\wwwroot\wss\VirtualDirectories\<port> folder (where port is the port that hosts the contemporary site).

Existing Master Page Does Not Incorporate the Ribbon Control

The existing master page for the default site (CSDefaultSite.Master) does not incorporate the ribbon control. To resolve this issue, you must perform a visual upgrade of your site to the new Microsoft SharePoint 2010 interface if you did not select the visual upgrade option when you installed or upgraded your SharePoint 2010 software.

For SharePoint Server 2010 only, visually upgrading the site overwrites your custom master page setting. You must restore the master page to CSDefaultSite.Master after the visual upgrade to SharePoint 2010.

To visually upgrade a SharePoint site to the SharePoint 2010 interface:

  1. Open a browser and navigate to your SharePoint site as a site collection administrator.

  2. Click Site Actions, and select Site Settings from the drop-down menu.

  3. On the <Site>: Site Settings page, click Visual Upgrade (under Site Collection Administration).

  4. On the Site Collection Administration: Visual Upgrade page, click Update All Sites (in the Apply the New User Interface to All Sites section).

  5. (For SharePoint Server 2010 users only) Return to the Site Settings page (click Site Actions, and select Site Settings from the drop-down menu).

    1. On the Site Settings page, click Master Page (under Look and Feel).

    2. On the Site Master Page Settings page, select CSDefaultSite.master from the drop-down menu (in the Site Master Page section).

    3. Click Ok.

    4. Return to the home page of the SharePoint site and click on My Account.

    5. On the My Account page, click Site Actions, and select Site Settings from the drop-down menu.

    6. On the Site Settings page, click Master Page (under Look and Feel).

    7. On the Site Master Page Settings page, select CSDefaultSite.master from the drop-down menu (in the Site Master Page section).

  6. Click Ok.

You must also modify the CSDefaultSite.Master file to incorporate the ribbon control.

  1. Navigate to the folder that contains the master page for the site you are migrating.

    • For the default site on SharePoint Server 2010, the path is:

      <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServerDefaultSiteResources\MasterPages

    • For the default site on SharePoint Foundation 2010, the path is:

      <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServerDefaultSiteMasterPages\MasterPages

    • For the contemporary site on SharePoint Server 2010, the path is:

      <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServerContemporarySiteResources\MasterPages

    • For the contemporary site on SharePoint Foundation 2010, the path is:

      <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServerContemporarySiteMasterPages\ MasterPages

  2. Open the CSDefaultSite.Master file in a text or XML editor.

    • If you are using SharePoint Server 2010, go to step 3.

    • If you are using SharePoint Foundation 2010, go to step 4.

  3. (For SharePoint Server 2010 users) Modify the CSDefaultSite.Master file as follows: 

    1. Locate the <PublishingSiteAction:SiteActionMenu> element and delete the following snippet:

      <PublishingSiteAction:SiteActionMenu />

      <PublishingWebControls:AuthoringContainer id="authoringcontrols" >

      <PublishingConsole:Console />

      </PublishingWebControls:AuthoringContainer>

    2. Replace the deleted code with the following code snippet:

      <Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="ManageWeb">
<a id="HiddenAnchor" href="javascript:;" style="display:none;"></a>
<div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle">
<SharePoint:SPRibbon ID="SPRibbon1" 
PlaceholderElementId="RibbonContainer"
CssFile="">
<SharePoint:SPRibbonPeripheralContent ID="SPRibbonPeripheralContent1"

Location="TabRowLeft"
CssClass="ms-siteactionscontainer s4-notdlg">
<span class="ms-siteactionsmenu" id="siteactiontd">
<SharePoint:SiteActions  accesskey="<%$Resources:wss,tb_SiteActions_AK%>" id="SiteActionsMenuMain"
PrefixHtml=""
SuffixHtml="" 
MenuNotVisibleHtml="&amp;nbsp;"
>
<CustomTemplate>
<SharePoint:FeatureMenuTemplate ID="FeatureMenuTemplate1" 
FeatureScope="Site"
Location="Microsoft.SharePoint.StandardMenu"
GroupId="SiteActions"
UseShortId="true"
>
<SharePoint:MenuItemTemplate  id="MenuItem_EditPage"
Text="<%$Resources:wss,siteactions_editpage%>"
Description="<%$Resources:wss,siteactions_editpagedescriptionv4%>"
ImageUrl="/_layouts/images/ActionsEditPage.png"
MenuGroupId="100"
Sequence="110"
ClientOnClickhref="javascript:ChangeLayoutMode(false);"
/>
<SharePoint:MenuItemTemplate  id="MenuItem_TakeOffline"
Text="<%$Resources:wss,siteactions_takeoffline%>"
Description="<%$Resources:wss,siteactions_takeofflinedescription%>"
ImageUrl="/_layouts/images/connecttospworkspace32.png"
MenuGroupId="100"
Sequence="120"
/>
<SharePoint:MenuItemTemplate  id="MenuItem_CreatePage"
Text="<%$Resources:wss,siteactions_createpage%>"
Description="<%$Resources:wss,siteactions_createpagedesc%>"
ImageUrl="/_layouts/images/NewContentPageHH.png"
MenuGroupId="200"
Sequence="210"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Page')) { OpenCreateWebPageDialog('~site/_layouts/createwebpage.aspx') }"
PermissionsString="AddListItems, EditListItems"
PermissionMode="All" />
<SharePoint:MenuItemTemplate  id="MenuItem_CreateDocLib"
Text="<%$Resources:wss,siteactions_createdoclib%>"
Description="<%$Resources:wss,siteactions_createdoclibdesc%>"
ImageUrl="/_layouts/images/NewDocLibHH.png"
MenuGroupId="200"
Sequence="220"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('DocLib')) { GoToPage('~site/_layouts/new.aspx?FeatureId={00bfea71-e717-4e80-aa17-d0c71b360101}&amp;ListTemplate=101') }"
PermissionsString="ManageLists"
PermissionMode="Any"
VisibilityFeatureId="00BFEA71-E717-4E80-AA17-D0C71B360101" />
<SharePoint:MenuItemTemplate  id="MenuItem_CreateSite"
Text="<%$Resources:wss,siteactions_createsite%>"
Description="<%$Resources:wss,siteactions_createsitedesc%>"
ImageUrl="/_layouts/images/newweb32.png"
MenuGroupId="200"
Sequence="230"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Site')) { STSNavigate('~site/_layouts/newsbweb.aspx') }"
PermissionsString="ManageSubwebs,ViewFormPages"
PermissionMode="All" />
<SharePoint:MenuItemTemplate  id="MenuItem_Create"
Text="<%$Resources:wss,siteactions_create%>"
Description="<%$Resources:wss,siteactions_createdesc%>"
MenuGroupId="200"
Sequence="240"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('All')) { STSNavigate('~site/_layouts/create.aspx') }"
PermissionsString="ManageLists, ManageSubwebs"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_ViewAllSiteContents"
Text="<%$Resources:wss,quiklnch_allcontent%>"
Description="<%$Resources:wss,siteactions_allcontentdescription%>"
ImageUrl="/_layouts/images/allcontent32.png"
MenuGroupId="300"
Sequence="302"
UseShortId="true"
ClientOnClickhref="~site/_layouts/viewlsts.aspx"
PermissionsString="ViewFormPages"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_EditSite"
Text="<%$Resources:wss,siteactions_editsite%>"
Description="<%$Resources:wss,siteactions_editsitedescription%>"
ImageUrl="/_layouts/images/SharePointDesigner32.png"
MenuGroupId="300"
Sequence="304"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="EditInSPD('~site/',true);"
PermissionsString="AddAndCustomizePages"
PermissionMode="Any"
/>
<SharePoint:MenuItemTemplate  id="MenuItem_SitePermissions"
Text="<%$Resources:wss,people_sitepermissions%>"
Description="<%$Resources:wss,siteactions_sitepermissiondescriptionv4%>"
ImageUrl="/_layouts/images/Permissions32.png"
MenuGroupId="300"
Sequence="310"
UseShortId="true"
ClientOnClickhref="~site/_layouts/user.aspx"
PermissionsString="EnumeratePermissions"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_Settings"
Text="<%$Resources:wss,settings_pagetitle%>"
Description="<%$Resources:wss,siteactions_sitesettingsdescriptionv4%>"
ImageUrl="/_layouts/images/settingsIcon.png"
MenuGroupId="300"
Sequence="320"
UseShortId="true"
ClientOnClickhref="~site/_layouts/settings.aspx"
PermissionsString="EnumeratePermissions,ManageWeb,ManageSubwebs,AddAndCustomizePages,ApplyThemeAndBorder,ManageAlerts,ManageLists,ViewUsageData"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_CommitNewUI"
Text="<%$Resources:wss,siteactions_commitnewui%>"
Description="<%$Resources:wss,siteactions_commitnewuidescription%>"
ImageUrl="/_layouts/images/visualupgradehh.png"
MenuGroupId="300"
Sequence="330"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="GoToPage('~site/_layouts/prjsetng.aspx')"
PermissionsString="ManageWeb"
PermissionMode="Any"
ShowOnlyIfUIVersionConfigurationEnabled="true" />
</SharePoint:FeatureMenuTemplate>
       </CustomTemplate>
    </SharePoint:SiteActions></span>
  </SharePoint:SPRibbonPeripheralContent>
</SharePoint:SPRibbon>
 <div id="notificationArea" class="s4-noti"></div>
   <asp:ContentPlaceHolder ID="SPNavigation" >
      <SharePoint:DelegateControl  ControlId="PublishingConsole" Id="PublishingConsoleDelegate"/>
   </asp:ContentPlaceHolder>
 <div id="WebPartAdderUpdatePanelContainer">
   <asp:UpdatePanel
ID="WebPartAdderUpdatePanel"
UpdateMode="Conditional"
ChildrenAsTriggers="false"
>
     <ContentTemplate>
     <WebPartPages:WebPartAdder ID="WebPartAdder" />
    </ContentTemplate>
    <Triggers>
      <asp:PostBackTrigger ControlID="WebPartAdder" />
     </Triggers>
   </asp:UpdatePanel>
 </div>
 </div>
</Sharepoint:SPSecurityTrimmedControl>

    3. Save your changes and close the file.

  4. (For SharePoint Foundation 2010 users) Modify the CSDefaultSite.Master file as follows:

    1. Locate the line <!-- WSS: Site Action Menu STARTS --> line and delete the code that follows as noted below:

      <!-- WSS: Site Action Menu STARTS -->

      <div class="ms-siteactionsmenu" id="siteactiontd">

      Delete all code here

      </div>

      <!-- WSS: Site Action Menu ENDS -->

    2. Replace the deleted code with the following code snippet:

      <Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="ManageWeb">
<a id="HiddenAnchor" href="javascript:;" style="display:none;"></a>
<SharePoint:DelegateControl ID="DelegateControl1"  ControlId="GlobalNavigation"/>
<div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle">
<div id="s4-ribboncont">
<SharePoint:SPRibbon ID="SPRibbon1"

PlaceholderElementId="RibbonContainer"
CssFile="">
<SharePoint:SPRibbonPeripheralContent ID="SPRibbonPeripheralContent1"

Location="TabRowLeft"
CssClass="ms-siteactionscontainer s4-notdlg">
<span class="ms-siteactionsmenu" id="siteactiontd">
<SharePoint:SiteActions  accesskey="<%$Resources:wss,tb_SiteActions_AK%>" id="SiteActionsMenuMain"
PrefixHtml=""
SuffixHtml=""
MenuNotVisibleHtml="&amp;nbsp;"
>
<CustomTemplate>
<SharePoint:FeatureMenuTemplate ID="FeatureMenuTemplate1" 
FeatureScope="Site"
Location="Microsoft.SharePoint.StandardMenu"
GroupId="SiteActions"
UseShortId="true"
>
<SharePoint:MenuItemTemplate  id="MenuItem_EditPage"
Text="<%$Resources:wss,siteactions_editpage%>"
Description="<%$Resources:wss,siteactions_editpagedescriptionv4%>"
ImageUrl="/_layouts/images/ActionsEditPage.png"
MenuGroupId="100"
Sequence="110"
ClientOnClickhref="javascript:ChangeLayoutMode(false);"
/>
<SharePoint:MenuItemTemplate  id="MenuItem_TakeOffline"
Text="<%$Resources:wss,siteactions_takeoffline%>"
Description="<%$Resources:wss,siteactions_takeofflinedescription%>"
ImageUrl="/_layouts/images/connecttospworkspace32.png"
MenuGroupId="100"
Sequence="120"
/>
<SharePoint:MenuItemTemplate  id="MenuItem_CreatePage"
Text="<%$Resources:wss,siteactions_createpage%>"
Description="<%$Resources:wss,siteactions_createpagedesc%>"
ImageUrl="/_layouts/images/NewContentPageHH.png"
MenuGroupId="200"
Sequence="210"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Page')) { OpenCreateWebPageDialog('~site/_layouts/createwebpage.aspx') }"
PermissionsString="AddListItems, EditListItems"
PermissionMode="All" />
<SharePoint:MenuItemTemplate  id="MenuItem_CreateDocLib"
Text="<%$Resources:wss,siteactions_createdoclib%>"
Description="<%$Resources:wss,siteactions_createdoclibdesc%>"
ImageUrl="/_layouts/images/NewDocLibHH.png"
MenuGroupId="200"
Sequence="220"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('DocLib')) { GoToPage('~site/_layouts/new.aspx?FeatureId={00bfea71-e717-4e80-aa17-d0c71b360101}&amp;ListTemplate=101') }"
PermissionsString="ManageLists"
PermissionMode="Any"
VisibilityFeatureId="00BFEA71-E717-4E80-AA17-D0C71B360101" />
<SharePoint:MenuItemTemplate  id="MenuItem_CreateSite"
Text="<%$Resources:wss,siteactions_createsite%>"
Description="<%$Resources:wss,siteactions_createsitedesc%>"
ImageUrl="/_layouts/images/newweb32.png"
MenuGroupId="200"
Sequence="230"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Site')) { STSNavigate('~site/_layouts/newsbweb.aspx') }"
PermissionsString="ManageSubwebs,ViewFormPages"
PermissionMode="All" />
<SharePoint:MenuItemTemplate  id="MenuItem_Create"
Text="<%$Resources:wss,siteactions_create%>"
Description="<%$Resources:wss,siteactions_createdesc%>"
MenuGroupId="200"
Sequence="240"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('All')) { STSNavigate('~site/_layouts/create.aspx') }"
PermissionsString="ManageLists, ManageSubwebs"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_ViewAllSiteContents"
Text="<%$Resources:wss,quiklnch_allcontent%>"
Description="<%$Resources:wss,siteactions_allcontentdescription%>"
ImageUrl="/_layouts/images/allcontent32.png"
MenuGroupId="300"
Sequence="302"
UseShortId="true"
ClientOnClickhref="~site/_layouts/viewlsts.aspx"
PermissionsString="ViewFormPages"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_EditSite"
Text="<%$Resources:wss,siteactions_editsite%>"
Description="<%$Resources:wss,siteactions_editsitedescription%>"
ImageUrl="/_layouts/images/SharePointDesigner32.png"
MenuGroupId="300"
Sequence="304"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="EditInSPD('~site/',true);"
PermissionsString="AddAndCustomizePages"
PermissionMode="Any"
/>
<SharePoint:MenuItemTemplate  id="MenuItem_SitePermissions"
Text="<%$Resources:wss,people_sitepermissions%>"
Description="<%$Resources:wss,siteactions_sitepermissiondescriptionv4%>"
ImageUrl="/_layouts/images/Permissions32.png"
MenuGroupId="300"
Sequence="310"
UseShortId="true"
ClientOnClickhref="~site/_layouts/user.aspx"
PermissionsString="EnumeratePermissions"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_Settings"
Text="<%$Resources:wss,settings_pagetitle%>"
Description="<%$Resources:wss,siteactions_sitesettingsdescriptionv4%>"
ImageUrl="/_layouts/images/settingsIcon.png"
MenuGroupId="300"
Sequence="320"
UseShortId="true"
ClientOnClickhref="~site/_layouts/settings.aspx"
PermissionsString="EnumeratePermissions,ManageWeb,ManageSubwebs,AddAndCustomizePages,ApplyThemeAndBorder,ManageAlerts,ManageLists,ViewUsageData"
PermissionMode="Any" />
<SharePoint:MenuItemTemplate  id="MenuItem_CommitNewUI"
Text="<%$Resources:wss,siteactions_commitnewui%>"
Description="<%$Resources:wss,siteactions_commitnewuidescription%>"
ImageUrl="/_layouts/images/visualupgradehh.png"
MenuGroupId="300"
Sequence="330"
UseShortId="true"
ClientOnClickScriptContainingPrefixedUrl="GoToPage('~site/_layouts/prjsetng.aspx')"
PermissionsString="ManageWeb"
PermissionMode="Any"
ShowOnlyIfUIVersionConfigurationEnabled="true" />
</SharePoint:FeatureMenuTemplate>
</CustomTemplate>
</SharePoint:SiteActions></span>
</SharePoint:SPRibbonPeripheralContent>
<SharePoint:SPRibbonPeripheralContent

Location="TabRowRight"
ID="RibbonTabRowRight"
CssClass="s4-trc-container s4-notdlg">
<SharePoint:DelegateControl  ID="GlobalDelegate0" ControlId="GlobalSiteLink0" />
<a href="#" tabindex="-1" style="display:none"></a><a href="#" tabindex="-1" style="display:none"></a>
<SharePoint:DelegateControl ControlId="GlobalSiteLink2" ID="GlobalDelegate2" Scope="Farm"  />
<span>
<span class="s4-devdashboard">
<Sharepoint:DeveloperDashboardLauncher
ID="DeveloperDashboardLauncher"
href="javascript:ToggleDeveloperDashboard()"

ImageUrl="/_layouts/images/fgimg.png"
Text="<%$Resources:wss,multipages_launchdevdashalt_text%>"
OffsetX=0
OffsetY=222
Height=16
Width=16 />
</span>
</span>
</SharePoint:SPRibbonPeripheralContent>
</SharePoint:SPRibbon>
</div>
<div id="notificationArea" class="s4-noti">
</div>
<asp:ContentPlaceHolder ID="SPNavigation" >
<SharePoint:DelegateControl  ControlId="PublishingConsole" Id="PublishingConsoleDelegate">
</SharePoint:DelegateControl>
</asp:ContentPlaceHolder>
<div id="WebPartAdderUpdatePanelContainer">
<asp:UpdatePanel
ID="WebPartAdderUpdatePanel"
UpdateMode="Conditional"
ChildrenAsTriggers="false"
>
<ContentTemplate>
<WebPartPages:WebPartAdder ID="WebPartAdder" />
</ContentTemplate>
<Triggers>
<asp:PostBackTrigger ControlID="WebPartAdder" />
</Triggers>
</asp:UpdatePanel>
</div>
</div>
</SharePoint:SPSecurityTrimmedControl>

  5. Save the changes and close the file.

Ribbon Background Displayed in Wrong Color

By default, the ribbon background color is blue. You must modify the DefaultSite.css file to override the Corev4.css to restore the ribbon background color to dark grey (to match the background color of the contemporary site).

You must use Microsoft SharePoint Designer 2010 to modify the cascading style sheet (CSS) for your site.

To change the ribbon background color:

  1. Open the Default zone of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click on Site Actions and select the Edit in SharePoint Designer option.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer 2010 separately and open the Default zone of the site.

  2. In SharePoint Designer 2010, click All Files in the left navigation pane.

  3. On the All Files tab, click Style Library.

  4. On the Style Library tab, right-click on defaultSite.css and select Open.

    The system displays a dialog box asking if you want to check the file out.

  5. Click Yes.

  6. Add the following snippet at the end of the CSS file:

    /*
 ###############################################################
 Override of COREv4.css Styles & Sharepoint Generated Classes 
 ###############################################################
*/
body #s4-ribbonrow
{
 min-height: 0px;
 background-color: #272727;
}

  7. Save your changes and close the file.

  8. Check the file back in (on the Style Library tab, right-click on the defaultSite.css file and select Check In).

Ribbon Embedded in Site

By default, the ribbon control is embedded in the contemporary site container. However, we recommend that you move the ribbon outside of the site container to ensure that the SharePoint 2010 ribbon CSS is not impacted by the Commerce Server 2009 R2 custom skin CSS.

You must use SharePoint Designer 2010 to modify the custom master page for your site.

To move the ribbon control outside of the site container

  1. Open the Default zone of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click on Site Actions and select the Edit in SharePoint Designer option.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer separately and open the Default zone of the site.

  2. In SharePoint Designer, click All Files in the left navigation pane.

  3. On the All Files tab, click _catalogs.

  4. On the _catalogs tab, click masterpage.

  5. Right-click on the CSDefaultSite.master file and select Open.

    The system displays a dialog box asking if you want to check the file out.

  6. Click Yes.

  7. Make sure the following snippet is above the ribbon control:

    <div class="Skin_Page_Container">

  8. Save your changes and close the file.

  9. Check the file back in (on the masterpage tab, right-click on the CSDefaultSite.master file and select Check In).

Master Page Displays Error in SharePoint Designer

When you open the contemporary site master page in SharePoint Designer 2010 for the first time, SharePoint Designer displays an error message. To resolve this issue, you must modify the custom master page.

To resolve master page errors:

  1. Open the Default zone of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click on Site Actions and select the Edit in SharePoint Designer option.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer separately and open the Default zone of the site.

  2. In SharePoint Designer, click All Files in the left navigation pane.

  3. On the All Files tab, click _catalogs.

  4. On the _catalogs tab, click masterpage.

  5. Right-click on the CSDefaultSite.master file and select Open.

    The system displays a dialog box asking if you want to check the file out.

  6. Click Yes.

  7. Remove the following code snippet:

    <meta name="Microsoft Theme" content="Lichen 1011, default">

  8. Save your changes and close the file.

  9. Check the file back in (on the masterpage tab, right-click on the CSDefaultSite.master file and select Check In).

Product Details Page Renders Exception

When you upgrade your site to SharePoint 2010, the Product Details Page throws an exception because it cannot find a native list. To resolve this issue, perform the following procedures by modifying the Reviews and Rating Average Web Part and the Reviews and Rating List Web Part:

  • Capture the XSLT used for the Web Parts

  • Remove the Web Parts from the Product Details page

  • Modify the Web Parts to point to a URL

  • Connection Cannot be made to Product Provider

  • Add The Web Parts Back to the Product Details Page

  • Restore the original XSLT definition for the Web Parts

Capture the XSLT used for the Web Parts

Follow these steps to capture the XSLT information for the Web Parts:

  1. Open the Default zone of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click on Site Actions and select the Edit in SharePoint Designer option.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer separately and open the Default zone of the site.

  2. In SharePoint Designer, click All Files in the left navigation pane.

  3. On the All Files tab, click Pages.

  4. On the Pages tab, right-click on the product.aspx file and select Check Out.

    If you are using SharePoint Server 2010, on the Pages tab:

    1. Right-click on the product.aspx file and select Detach from Page Layout.The system displays a warning message prompting you to confirm that you want to detach the file from page layout.

    2. Click Yes.

      The system displays a confirmation dialog box that the file has been detached.

    3. Click Ok.

    If you are using SharePoint Foundation 2010, on the Pages tab, edit the file to open the page in Code mode

  5. In the product.aspx file, do the following:

    1. Locate the Reviews and Ratings Average Web Part and copy the XSLT code (contained in the XSL property of the Web Part declaration).

    2. Locate the Reviews and Ratings List Web Part and copy the XSLT code (contained in the XSL property of the Web Part declaration).

  6. Re-attach the page and undo the check out.

Remove the Web Parts from the Product Details page

Follow these steps to remove the Web Parts from the Product Details page:

  1. Open the Product Details page in a browser on the Default zone.

  2. Remove all query string parameters from the URL and append only "?contents=1".

  3. Delete the Reviews and Rating Average Web Part and the Reviews and Rating List Web Part.

    1. Return to the Product Details page you opened in step 1.

    2. Check the Reviews and Rating Average Web Part and the Reviews and Rating List Web Part checkbox.

    3. Click Delete.

  4. Click Go Back to Web Part Page.

  5. For SharePoint Server based solutions:

    1. Open the Publish tab.

    2. Click Publish

Modify the Web Parts to point to a URL

Follow these steps to modify the Web Parts, so that they point to a URL and not a GUID:

  1. Open the Default zone of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click on Site Actions and select the Edit in SharePoint Designer option.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer separately and open the Default zone of the site.

  2. In SharePoint Designer, click All Files in the left navigation pane.

  3. On the All Files tab, click catalogs.

  4. On the catalogs tab, click wp.

  5. On the wp tab, right-click on the ProductRatingAverageList.webpart file and select Open.

    The system displays a dialog box asking if you want to check the file out.

  6. Click Yes.

  7. Search for the property ListName (<property name="ListName"…>) and replace the GUID with “/Lists/ProductRatingAverageList”.

  8. Save your changes.

  9. Repeat steps 5 and 6 for the ReviewRatingTemplate.webpart file.

  10. Search for ListName and replace the GUID with "/Lists/ReviewRatingTemplate".

  11. Save your changes.

  12. Check in both Web Part files.

Connection Cannot be made to Product Provider

Follow these steps to connect to the Product Provider:

  1. Navigate to http://[machinename]:[port of default zone]/Pages/Product.aspx?contents=1

  2. Delete the Product Provider web part. The web part displays an error in the list of web part names.

  3. Open SharePoint Designer and load your site.

  4. On the Pages tab, right-click on the product.aspx file and select Check Out.

  5. If you are using SharePoint Server 2010:

    1. Right-click on the product.aspx file and select Detach from Page Layout.The system displays a warning message prompting you to confirm that you want to detach the file from page layout.

    2. Click Yes. The system displays a confirmation dialog box that the file has been detached.

    3. Click OK.

    4. Remove the web part connections from product.aspx. For SPProductProvider remove the ID property.

  6. If you are using SharePoint Foundation 2010:

    1. Edit the file to open the page in Code mode.

    2. Remove the web part connections from product.aspx. Remove instances of <WebPartPages:SPWebPartConnection> (there should be 5).

  7. Save the changes, close the file and check the file back in.

  8. Add the Product Provider to the Product Details page.

    1. Navigate to the Product Details page.

    2. Put the Page in edit mode.

    3. Click Add Web Part in the desired zone.

    4. Select the product provider from the list of web parts.

  9. Reconfigure the Product Provider:

    1. Put the page in edit mode.

    2. Click the down arrow at the top of the Product Provider web part and select Edit the web part from the dropdown menu.

    3. Under the Commerce section of the Editor panel, select the items you want returned along with the product properties (For example, Include Variants)

    4. Click OK to close the editor panel and commit the changes.

  10. Publish the page:

    1. If you are using SharePoint Foundation 2010 click Stop Editing on the ribbon at the top of the page.

    2. If you are using SharePoint Server 2010 click Check In.

  11. Navigate to Site Settings->All Site Content->Pages and from the drop down beside product.aspx, check the file in to propagate your changes to all zones. (Note: For SharePoint Server, you will also need to publish your changes.)

  12. Delete, then add the Image Viewer web part and the Add To Cart web part.

    1. Put the page in edit mode: Click the down arrow at the top of the Image Viewer web part and select Edit the Web Part from the dropdown menu.

    2. Set all the required properties under the Image Viewer Display.

    3. Click OK to close the editor panel and commit the changes.

  13. Publish the page:

    1. If you are using click Stop Editing on the ribbon at the top of the page.

    2. If you are using click Check In.

  14. Navigate to Site Settings->All Site Content->Pages and from the drop down beside product.aspx, check the file in to propagate your changes to all zones. (Note: For SharePoint Server, you will also need to publish your changes.).

  15. Reconnect all the web parts to the product provider that require a connection.

Add the Web Parts back to the Product Details page

Follow these steps to add the modified Web Parts back to the Product Details page:

  1. Open a browser and navigate to the Product Details page of your site.

  2. Click Site Actions, and select Edit Page from the drop-down menu.

  3. Click Check Out in the toolbar to check the file out.

  4. Add the Reviews and Rating Average Web Part and the Reviews and Rating List Web Part.

  5. Connect the Reviews and Rating Average Web Part to the page, as described at https://go.microsoft.com/fwlink/?LinkId=191340. There may be an issue where you receive a JavaScript error when attempting to connect the web part to the product provider. To workaround this problem, immediately click on "Edit the web part" from the drop down and it will now make the connection.

    Note

    There may be an issue where you receive a JavaScript error when attempting to connect the web part to the product provider. To workaround this problem, immediately click on "Edit the web part" from the drop down and it will now make the connection.

  6. Connect the Reviews and Ratings List Web Part to the page, as described at https://go.microsoft.com/fwlink/?LinkId=191341.

    Note

    The procedure in the above link for connecting the Reviews and Ratings List Web Part to the page is incomplete. You must also specify the same information in the Configure Connection Webpage Dialog as you specified for the Reviews and Rating Average Web Part.

    Note

    There may be an issue where you receive a JavaScript error when attempting to connect the web part to the product provider. To workaround this problem, immediately click on "Edit the web part" from the drop down and it will now make the connection.

  7. Save your changes and check the file back in.

Restore the original XSLT definition for the Web Parts

Modify the Web Parts to restore the XSLT definition you captured in the first step.

  1. Open the Product Details page of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click Site Actions and select the Edit in SharePoint Designer option from the drop-down menu.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer separately and open the Default zone of the site.

  2. In SharePoint Designer, click All Files in the left navigation pane.

  3. On the All Files tab, click Pages.

  4. On the Pages tab, right-click on the product.aspx file and select Check Out.

    The system checks the file out.

  5. Open a browser and navigate to the Product Details page of your site.

  6. Click Site Actions and select Edit Page from the drop-down menu.

  7. Scroll down to the Reviews and Ratings Average Web Part and click on the Web Part title.

  8. Click on the small downward arrow to the right of the Web Part title, and select Edit Web Part from the drop-down menu.

    The system opens the Reviews and Ratings Average Rating Web Part editor in the top right-hand side of the page.

  9. In the Web Part editor dialog box, click XSL Editor.

    1. In the Text Editor -- Webpage Dialog window, delete all of the existing XSLT code.

    2. Retrieve the XLST code you captured for the Reviews and Ratings Average Web Part at the beginning of this task, and paste it into the XSLT editor window.

    3. Click Save to close the Text Editor window.

    4. Click Ok to close the Web Part editor window.

  10. Repeat steps 7 through 9 for the Reviews and Ratings List Web Part.

  11. Return to SharePoint Designer and check the Product Details page back in (right-click on the product.aspx file and select Check In).

Query Strings with User ID Cause Errors

  • The usage of ID as a query string parameter causes issues for some site pages. ID is a reserved keyword for SharePoint and should not be used as a query string parameter. To resolve this issue, you must modify certain XSLT definitions.

Modify the XSLT definitions

Perform the following procedure to modify the XSLT definitions to use pid instead of id in the query string parameter.

To modify the XSLT definitions

  1. Open the Default zone of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click on Site Actions and select the Edit in SharePoint Designer option.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer separately and open the Default zone of the site.

  2. In SharePoint Designer, click All Files in the left navigation pane.

  3. On the All Files tab, click Commerce Server Templates.

  4. On the Commerce Server Templates tab, modify each file listed in the table below, as follows:

    1. Click on the folder that contains the file you are modifying (for example, Cart).

    2. On the folder tab, right-click on the file you are modifying (for example, DefaultSite_Cart.xslt) and select Check Out.

    3. Right-click on the file again and select Open.

    4. Replace the query string parameter id with pid at the lines indicated in the table below.

    5. Save your changes and close the file.

    6. On the folder tab, right-click on the file you modified and select Check In. Click Ok in the confirmation dialog box.

      FileDefault SiteContemporary Site
      Cart\DefaultSite_Cart.xsltLine 288Line 308Line 218Line 231
      OrderDetails\DefaultSite_OrderConfirmation.xsltLine 298Line 260
      OrderDetails\DefaultSite_OrderDetails.xsltLine 301Line 262
      CheckOut\DefaultSite_OrderReview.xsltLine 382Line 297Line 323
      SearchTemplates\DefaultSite_ProductCatalog.templateLine 83Line 90Line 75 Line 83
      ProductDetails\DefaultSite_ProductCrossSells.templateLine 43 Line 55Line 43 Line 55
      ProductQuery\DefaultSite_ProductQuery.templateLine 64Line 74Line 64Line 73
      ShopperListDetail\DetailSite_WishListDetail.xsltLine 106Line 106

Wrong Link Displayed in Product Details Page

The Reviews and Ratings Web Part displays a URL link (“View Entries...”) in place of the Review column on the Product Details Page. This link redirects the user to the DispForm.aspx page. To resolve this issue, you must update the Reviews and Ratings list:

  1. Open a browser and navigate to your SharePoint site as a site collection administrator.

  2. Click Site Actions, and select Site Settings from the drop-down menu.

  3. On the Site Settings page, click Site Administration ->Site libraries and lists.

  4. On the Site Settings: Site Libraries and Lists page, click Customize "Reviews and Ratings".

  5. On the Reviews and Ratings > List Settings page, click Review (under the Columns section).

  6. On the List Settings > Change Column page, scroll to the Additional Column Settings area, and set the Append Changes to Existing Text option to No.

  7. Click Ok.

Write Review Page Displays Errors

When you upgrade your site to SharePoint 2010, the Write Review Page displays errors. To resolve this issue, you must update the WriteReview.aspx page:

  1. Navigate to the folder that contains the WriteReview.aspx file.

    If you are migrating the default site:

    • (For SharePoint Foundation 2010 users) Go to <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\WSSCSDefaultSite

    • (For SharePoint Server 2010 users) Go to <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\MOSSCSDefaultSite

    If you are migrating the contemporary site:

    • (For SharePoint Foundation 2010 users) Go to <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\WSSCSContemporarySite

    • (For SharePoint Server 2010 users) Go to <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\MOSSCSContemporarySite

  2. Open the WriteReview.aspx file in a text or XML editor.

  3. Add the following code snippet to the beginning of the file:

    <%@ Import Namespace="Microsoft.SharePoint" %> 
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 
<%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

  4. Locate the line beginning with email.innerHTML and replace the entire line with the following snippet:

     email.innerHTML = email.innerHTML + " " + document.getElementById("ctl00_BodyContainer_CS_Comm_email_not_displayed").innerHTML;

  5. Locate the line beginning with document.getElementById("CS_Comm_stars_instruction").innerHTML and replace the entire line with the following snippet:

    document.getElementById("CS_Comm_stars_instruction").innerHTML = "&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;" + document.getElementById("ctl00_BodyContainer_PlaceHolderMain_CS_Comm_stars_instruction_label").innerHTML;

  6. Update the contents of the <ZoneTemplate> tag. Locate the <ZoneTemplate> tag and replace the content with the following code:

    <ZoneTemplate>
<WebPartPages:DataFormWebPart runat="server" XslLink="/Commerce%20Server%20Templates/WriteReview/DefaultSite_WriteReview.xslt"
IsIncluded="True" NoDefaultStyle="TRUE" ViewFlag="0" Title="Reviews and Ratings"
PartOrder="1" ID="g_b3cefaa7_4b5a_42f2_997c_1b26f46ab12a" __WebPartId="{B3CEFAA7-4B5A-42F2-997C-1B26F46AB12A}"
__MarkupType="xmlmarkup" WebPart="true">
<DataSources>
<sharepoint:spdatasource  datasourcemode="ListItem" useinternalname="true"
selectcommand="&lt;View&gt;&lt;Query&gt;&lt;Where&gt;&lt;Eq&gt;&lt;FieldRef Name=&quot;ContentType&quot;/&gt;&lt;Value Type=&quot;Text&quot;&gt;Item&lt;/Value&gt;&lt;/Eq&gt;&lt;/Where&gt;&lt;/Query&gt;&lt;/View&gt;"
id="Reviews_x0020_and_x0020_Ratings1">
<SelectParameters>
<WebPartPages:DataFormParameter Name="ListItemId" ParameterKey="ListItemId" PropertyName="ParameterValues"
DefaultValue="0" />
<WebPartPages:DataFormParameter Name="ListName" ParameterKey="ListName" PropertyName="ParameterValues"
DefaultValue="Reviews and Ratings" />
</SelectParameters>
<DeleteParameters>
<WebPartPages:DataFormParameter Name="ListItemId" ParameterKey="ListItemId" PropertyName="ParameterValues"
DefaultValue="0" />
<WebPartPages:DataFormParameter Name="ListName" ParameterKey="ListName" PropertyName="ParameterValues"
DefaultValue="Reviews and Ratings" />
</DeleteParameters>
<InsertParameters>
<WebPartPages:DataFormParameter Name="ListItemId" ParameterKey="ListItemId" PropertyName="ParameterValues"
DefaultValue="0" />
<WebPartPages:DataFormParameter Name="ListName" ParameterKey="ListName" PropertyName="ParameterValues"
DefaultValue="Reviews and Ratings" />
</InsertParameters>
<UpdateParameters>
<WebPartPages:DataFormParameter Name="ListItemId" ParameterKey="ListItemId" PropertyName="ParameterValues"
DefaultValue="0" />
<WebPartPages:DataFormParameter Name="ListName" ParameterKey="ListName" PropertyName="ParameterValues"
DefaultValue="Reviews and Ratings" />
</UpdateParameters>
</sharepoint:spdatasource>
</DataSources>
<ParameterBindings>
<ParameterBinding Name="ListItemId" Location="QueryString(ID)" DefaultValue="0"/>
<ParameterBinding Name="ListName" Location="None" DefaultValue="Reviews and Ratings"/>
<ParameterBinding Name="dvt_apos" Location="Postback;Connection"/>
<ParameterBinding Name="UserID" Location="CAMLVariable" DefaultValue="CurrentUserName"/>
<ParameterBinding Name="Today" Location="CAMLVariable" DefaultValue="CurrentDate"/>
</ParameterBindings>
<DataFields>@Title,Summary;@_ModerationComments,Approver Comments;@Review,Review;@Rating,Rating;@FullName,Reviewer;@Location0,Location;@EMail,E-Mail;@ProductLink,ProductLink;@ID,ID;@ContentType,Content Type;@Modified,Modified;@Created,Created;@Author,Created By;@Editor,Modified By;@_UIVersionString,Version;@Attachments,Attachments;@_ModerationStatus,Approval Status;@File_x0020_Type,File Type;@FileLeafRef,Name (for use in forms);@FileDirRef,Path;@FSObjType,Item Type;@_HasCopyDestinations,Has Copy Destinations;@_CopySource,Copy Source;@ContentTypeId,Content Type ID;@_UIVersion,UI Version;@Created_x0020_Date,Created;@FileRef,URL Path;</DataFields>
</WebPartPages:DataFormWebPart>
</ZoneTemplate>

  7. Save your changes and close the file.

  8. Open the Default zone of the site in SharePoint Designer.

    • If you are using SharePoint Server 2010, you can open the Default zone of the site in a browser, then click Site Actions and select the Edit in SharePoint Designer option.

    • If you are using SharePoint Foundation 2010, you must launch SharePoint Designer separately and open the Default zone of the site.

  9. In SharePoint Designer, click All Files in the left navigation pane.

  10. On the All Files tab, click Pages.

  11. Right-click the WriteReview.aspx file and select Reset to Site Definition.

  12. Click Yes in the confirmation dialog box.

  13. (Optional) Open the new WriteReview.aspx file to verify that your changes are present.

  14. Delete the old version of the file (named WriteReview_copy(1).aspx).

Access Denied While Writing a Review

Use the following steps to allow shoppers who visit the contemporary site to add new reviews to the Ratings and Reviews list.

  1. Open a browser and go to the Default zone of the contemporary site.

  2. On the contemporary site home page, click Site Actions, and select Site Settings from the drop-down menu.

  3. On the Site Settings page, click Site Libraries and Lists (under Site Administration).

  4. On the Site Libraries and Lists page, click Customize "Reviews and Ratings".

  5. On the Reviews and Ratings: List Settings page, click Permissions for this list (under Permissions and Management).

  6. On the Permissions Tools tab of the Permissions page, click Stop Inheriting Permissions in the toolbar.

  7. SharePoint displays a warning dialog box.

  8. Click Ok in the warning dialog to confirm that you want to create unique permissions for the SharePoint list.

  9. On the Permission Tools tab, select the Registered Users group and click Edit User Permissions in the toolbar.

  10. In the Edit Permissions window, select the Read and AddItemToList roles, and click Ok.

Missing Reviews and Rating Images

Use SharePoint designer to add the missing images:

  1. Open your site in SharePoint Designer (must be the URL of the default zone)

  2. Click All Files from the left side bar and navigate to RatingImages.

  3. Go to <drive C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\CommerceServer\RatingImages

  4. Drag and drop all images files in the RatingImages directory and put them in the SharePoint Designer folder.

The site map provider used for the left side bar has changed with Commerce Server 2009 R2. Modify the sitemap file as follows:

  1. Navigate to the virtual directory of the Default zone (eg: C:\inetpub\wwwroot\wss\VirtualDirectories\81).

  2. Open MyAccountLeftNavigation.sitemap and replace the token ~/MyAccount with MyAccount.

  3. Repeat on each zone.

Logged-in Shopper Cannot Navigate to MyAccount Site – Access Denied

The user SignedInClient is no longer used in Commerce Server 2009 R2. Delete it and add the new "All Authenticated Users”.

  1. Navigate to the Default zone as an site collection administrator.

  2. Click Site Actions > Site Settings.

  3. Click Users and Permissions->People and Groups.

  4. Click Groups on the left hand side.

  5. Click Registered Users.

  6. Click New > Add New User.

  7. Enter All Authenticated Users and click OK.

  8. Remove the SignedInClient user.

Add New Address is causing a 404

Change the Address Detail URL as follows:

  1. Navigate to the My Address Book page as a site collection administrator.

  2. Edit the web part and go to the Advanced (Commerce) section.

  3. Replace the Address Detail Page URL value with MyAccount/Pages/addressDetail.aspx

  4. Check in your page.

  5. Approve the page so that the change propagates to the other zone:

    1. Click Site Actions > View All Site Content.

    2. Click Pages.

    3. If the Approval Status is set to Draft, click on the drop down beside addressBook and select Publish a major version and press OK.

    4. Select the drop down again beside addressBook and select Approve/Reject.

    5. Select the radio button Approved.. and press OK.

  6. You will now need to modify the Address Detail Web Part by first clicking on My Address Book on the left hand side and changing the token addressBook.aspx to addressDetail.aspx in the URL manually:

    1. Edit the page, then edit the Address Detail Web Part.

    2. Go to the Advanced (Commerce) section and change the On Completion, go to URL to MyAccount/Pages/AddressBook.aspx.

    3. Check in your page.

    4. Perform the step for the addressDetail page to have the changes propagated to the other zones.

Add Credit Card is causing a 404

Change the Credit Card Detail URL as follows:

  1. Navigate to the My Credit Card page as a site collection administrator.

  2. Edit the web part and go to the Advanced (Commerce) section.

  3. Replace the Credit Card Detail Page URL value with MyAccount/Pages/creditCardDetail.aspx.

  4. Check in your page.

  5. Approve the page so that the change propagates to the other zone:

    1. Click Site Actions > View All Site Content.

    2. Click Pages.

    3. If the Approval Status is set to Draft, click on the drop down beside creditCards and select Publish a major version and press OK.

    4. Select the drop down again beside creditCards and select Approve/Reject.

    5. Select the radio button Approved.. and press OK.

  6. Modify the Credit Card Detail Web Part:

    1. Click My Credit Cards on the left hand side, then change the token creditCards.aspx to creditCardDetail.aspx in the URL manually.

    2. Edit the page, then edit the Credit Card Detail Web Part.

    3. Go to the Advanced (Commerce) section and change the On Completion, go to URL to MyAccount/Pages/creditCards.aspx.

    4. Change the Address Detail page URL to MyAccount/Pages/addressDetail.aspx.

    5. Checkin your page.

    6. Repeat Step 5 to propogate the changes.

Two Login Links are appearing on top of the page

Use SharePoint Designer 2010 to remove the extra link.

  1. Launch SharePoint Designer and then go to your site's default zone.

  2. Click All Files from the left side bar and navigate to “_catalogs/masterpage”

  3. Click CSDefaultSite.master and click on Edit File.

  4. Delete the following entry:

    <asp:LoginStatus ID="CurrentUsersStatus" ToolTip="Login / Logout" LogoutAction="Redirect" LogoutPageUrl="/_layouts/signout.aspx"/>

  5. If you are using SharePoint Server 2010, approve the master page to propagate it to the other zones:

    1. Click on Site Actions

    2. Click on Site Settings

    3. Click on Master Pages and Page Layouts

    4. Click on the dropdown menu beside CSDEFaultSite.master and select "Approve/Reject"

    5. Select Approved and click OK.

  6. If you are using SharePoint 2010:

    1. Navigate to the appropriate page layouts folder:

    • Solution Storefront path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServerStorefrontSiteResources\PageLayouts

    • Contemporary path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServerContemporarySiteResources\PageLayouts

    • Default path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\WSSCSDefaultSite

    1. Edit the file cart.aspx. Remove the following line:

      <asp:LoginStatus ID="CurrentUsersStatus" ToolTip="Login / Logout" LogoutAction="Redirect" LogoutPageUrl="/_layouts/signout.aspx"/>

    2. Edit the file checkout.aspx. Remove the following line:

      <asp:LoginStatus ID="CurrentUsersStatus" ToolTip="Login / Logout" LogoutAction="Redirect" LogoutPageUrl="/_layouts/signout.aspx"/>

  7. Save and close.

Search Does Not Return Results

To address this known issue, assign an indexing server. Perform the following steps:

  1. Navigate to Central Admininistration.

  2. Click Application Management.

  3. Click Manage Content Databases.

  4. Select the appropriate web application.

  5. Select the appropriate content database.

  6. Select a Search Server and then click OK.

  7. Verify the crawl log. If the log indicates that it was unsuccessful in crawling your site, the crawl happened when the site was not working. Re-crawl your site when you are able to navigate to your site successfully. To do this, perform the following steps:

    1. Navigate to Central Admin.

    2. Click Application Management.

    3. Click Manage Service Applications.

    4. Click Search Service Application.

    5. Click Content Sources on the side bar.

    6. Click Start All Crawls.

    7. Wait for the system to complete the crawl.

  8. Login as a site collection administrator and perform a search.

  9. Open the search page in edit the page so you can edit the search results web part by doing the following:

    1. Click Edit Web Part on the search results web part.

    2. For the No Results XSL Template, select the correct template (eg: NotFound).

    3. For the Tab 1 Template, select the correct template (eg: ProductCatalog).

    4. For the Tab 2 Template, select the correct template (eg: SiteContent).

    5. Check in and publish your changes to propagate you changes to the other zones.

Unable to Add Commerce User as Site Collection Administrator

To address this known issue, add the membership provider in the Web.config of the SharePoint Central Administration site. To do this, perform the following steps:

  1. Navigate to the virtual directory of Central Administration, and then open the Web.config file (eg: C:\inetpub\wwwroot\wss\VirtualDirectories\[port])

  2. Locate the node configuration/configSections, and then add the following configuration section:

    <sectionGroup name="microsoft.commerce">
      <sectionGroup name="client">
        <section name="CommerceOperationServices" type="Microsoft.Commerce.Configuration.CommerceOperationServiceConfiguration, Microsoft.Commerce, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      </sectionGroup>
</sectionGroup>

  3. Locate the node configuration, and then add the following configuration section:

    Note

    Replace [WebAppGuid] with your Web application GUID.

    <microsoft.commerce>
    <client>
      <CommerceOperationServices>
        <CommerceOperationService name="IOperationService_[WebAppGuid]_Internet" mode="Service" clientEndpointName="Foundation_[WebAppGuid]_Internet" />
      </CommerceOperationServices>
    </client>
</microsoft.commerce>

  4. Locate the node configuration/system.serviceModel, and then add the following configuration section:

    Note

    Replace [WebAppGuid] with your Web application GUID, [MachineName] with the actual machine name and [Port] with the actual port.

    <client>
      <endpoint name="Foundation_[WebAppGuid]_Internet" address="http://[MachineName]:[Port]/Foundation/foundationservice.svc" binding="wsHttpBinding" bindingConfiguration="wsHttp" contract="Microsoft.Commerce.IOperationService" behaviorConfiguration="CommerceLocalOnlyBehavior">
        <identity>
          <servicePrincipalName />
        </identity>
      </endpoint>
    </client>
<bindings>
      <wsHttpBinding>
        <binding closeTimeout="00:20:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" maxReceivedMessageSize="1048576" name="wsHttp">
          <readerQuotas maxDepth="100" maxBytesPerRead="65535" />
        </binding>
      </wsHttpBinding>
    </bindings>
<extensions>
      <behaviorExtensions>
        <add name="commerceLocalOnlyBehavior" type="Microsoft.Commerce.CommerceLocalOnlyBehavior, Microsoft.Commerce, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      </behaviorExtensions>
    </extensions>
    <behaviors>
      <endpointBehaviors>
        <behavior name="CommerceLocalOnlyBehavior">
          <commerceLocalOnlyBehavior />
        </behavior>
      </endpointBehaviors>
    </behaviors>

  5. Locate the node configuration/system.web/membership/providers and remove any providers that start with UPM. If you cannot find the nodes configuration/system.web/membership/providers, you must create them yourself.

  6. Add the following provider:

    Note

    Replace [WebAppGuid] with your Web application GUID.

    <add name="CS_[WebAppGuid]_Internet" type="Microsoft.Commerce.Portal.Common.CommerceSharePointCentralAdminMembershipProvider, Microsoft.Commerce.Portal.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" enablePasswordReset="true" requiresQuestionAndAnswer="true" membershipUserModelName="UserProfile" logonNameProperty="Email" operationServiceName="IOperationService_[WebAppGuid]_Internet" passwordLockoutPeriod="5" passwordFormat="Hashed" PasswordStrengthRegularExpression="^(?=.*\d)(?=.*[a-z])(?=.*[A-Z]).{6,50}$" requiresApproval="false" />

Checkout#Checkout Page is not loading and displays a null reference exception

This error occurs on systems that ran Commerce Server 2009 Template Pack, then upgraded to SharePoint 2010. Commerce Server 2009 Template Pack has created its own versions of some user controls required by the web parts that have been deployed to the 14 hive. Those user controls do not get upgraded as part of the web parts upgrade.

The user control Billing.ascx is used by the CheckOut web part in the Commerce Server 2009 Template Pack. During the upgrade to SharePoint 2010 you must update Billing_Contempory.ascx with the changes added to Billing.ascx to avoid a null reference exception.

Update Billing_Contempory.ascx:

  1. Open windows explorer and navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\CommerceServer

  2. Open Billing.ascx with Visual Studio

  3. Open Billing_Contemporary.ascx with Visual Studio

  4. Copy the contents of Billing.ascx and replace Billing_Contemporary.ascx.

  5. Save the Billing_Contemporary.ascx

  6. Perform an IISRESET

Store Locator requires manual configuration

Following migration to Commerce Server 2009 R2, perform the following procedures to configure the Store Locator.

Update the Profile Database

Execute the following script in the profile database of the site you want to migrate:

CREATE TABLE [dbo].[StoreLocatorConfig](
[i_config_id] [int] NOT NULL,
[u_key] [nvarchar](255) NULL,
[u_access_id] [nvarchar](255) NULL,
[u_data_source_name] [nvarchar](255) NULL,
[u_service_url] [nvarchar](255) NULL,
[u_spatial_service_url] [nvarchar](255) NOT NULL,
[i_keyindex] [int] NULL,
[u_user_id_changed_by] [nvarchar](50) NULL,
[dt_date_last_changed] [datetime] NULL DEFAULT GETDATE(),
[dt_date_created] [datetime] NULL DEFAULT GETDATE()
) ON [PRIMARY]

GO
ALTER TABLE [dbo].[StoreLocatorConfig] WITH NOCHECK ADD 
CONSTRAINT [PK_StoreLocatorConfig] PRIMARY KEY  CLUSTERED 
(
[i_config_id]
)  ON [PRIMARY] 
GO
//Create a new record in this table with your BingMap Key.
INSERT INTO [StoreLocatorConfig]
           ([i_config_id]
           ,[u_key]
           ,[u_access_id]
           ,[u_data_source_name]
           ,[u_service_url]
           ,[u_spatial_service_url]
           ,[i_keyindex]
           ,[u_user_id_changed_by]
           ,[dt_date_last_changed]
           ,[dt_date_created])
VALUES(1,
'<Insert BingMap Key Here>',
null,
null, 
'http://dev.virtualearth.net/REST/v1', 
'http://spatial.virtualearth.net/', 
1, 
null, 
GETDATE(), 
GETDATE())

Update the Profile Schema

Complete the following steps to update the profile schema.

  1. Open Commerce Server Manager

  2. Under Global Resources, expand the Profile Resource of the Site you want to migrate.

  3. Right-Click the Profile Catalog node, choose Export Profile Schema and then select a location/file.

  4. Open the Profile Schema xml file you just exported with an editor (like NotePad our Visual Studio for example).

  5. Remove the Profile Node under the Catalog node.

    < Profile name="VirtualEarthConfig" ... />

  6. Replace the node with the following :

    <Profile name="StoreLocatorConfig" displayName="Store Locator Configuration" description="Store Locator Configuration">
      <Attribute name="KeyIndex" displayName="KeyIndex" description="Key index for encryption" value="KeyIndex"/>
      <Group name="GeneralInfo" displayName="General Information" description="General Information Group">
        <Property name="config_id" displayName="Configuration Id" description="Configuration Id" propType="NUMBER" isRequired="1" isSearchable="1" isUpdatable="0" keyDef="PRIMARYJOIN">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.i_config_id"/>
          <Attribute name="MinValue" displayName="Minimum Value" description="Minimum value of this property value" value="1"/>
          <Attribute name="MaxValue" displayName="Maximum Value" description="Maximum value of this property value" value="10"/>
          <Attribute name="IsRestricted" displayName="Is Property Restricted" description="Indicates that this property requires an elevated priviledge level in order to perform an update." value="1"/>
        </Property>
        <Property name="key" displayName="Key" description="The Store Locator Key." propType="STRING">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.u_key"/>
          <Attribute name="MinLength" displayName="Minimum Length" description="Minimum length of this property value" value="1"/>
          <Attribute name="MaxLength" displayName="Maximum Length" description="Maximum length of this property value" value="255"/>
          <Attribute name="IsRestricted" displayName="Is Property Restricted" description="Indicates that this property requires an elevated priviledge level in order to perform an update." value="0"/>
        </Property>
        <Property name="accessId" displayName="AccessId" description="The Store Locator Access Id." propType="STRING">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.u_access_id"/>
          <Attribute name="MinLength" displayName="Minimum Length" description="Minimum length of this property value" value="1"/>
          <Attribute name="MaxLength" displayName="Maximum Length" description="Maximum length of this property value" value="255"/>
          <Attribute name="IsRestricted" displayName="Is Property Restricted" description="Indicates that this property requires an elevated priviledge level in order to perform an update." value="0"/>
        </Property>
        <Property name="data_source_name" displayName="Data Source Name" description="The data source name." propType="STRING">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.u_data_source_name"/>
          <Attribute name="MinLength" displayName="Minimum Length" description="Minimum length of this property value" value="1"/>
          <Attribute name="MaxLength" displayName="Maximum Length" description="Maximum length of this property value" value="255"/>
          <Attribute name="IsRestricted" displayName="Is Property Restricted" description="Indicates that this property requires an elevated priviledge level in order to perform an update." value="0"/>
        </Property>
        <Property name="service_url" displayName="Service Url" description="The url for the Service." propType="STRING" isRequired="1">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.u_service_url"/>
          <Attribute name="MaxLength" displayName="Maximum Length" description="Maximum length of this property value" value="255"/>
          <Attribute name="IsRestricted" displayName="Is Property Restricted" description="Indicates that this property requires an elevated priviledge level in order to perform an update." value="0"/>
          <Attribute name="MinLength" displayName="Minimum Length" description="Minimum length of this property value" value="1"/>
        </Property>
        <Property name="spatial_service_url" displayName="Spatial Services Url" description="The url for the Spatial Service." propType="STRING" isRequired="1">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.u_spatial_service_url"/>
          <Attribute name="MaxLength" displayName="Maximum Length" description="Maximum length of this property value" value="255"/>
          <Attribute name="IsRestricted" displayName="Is Property Restricted" description="Indicates that this property requires an elevated priviledge level in order to perform an update." value="0"/>
          <Attribute name="MinLength" displayName="Minimum Length" description="Minimum length of this property value" value="1"/>
        </Property>
      </Group>
      <Group name="ProfileSystem" displayName="Profile System" description="Profile System Group">
        <Property name="KeyIndex" displayName="Key Index" description="Key index for encryption" propType="NUMBER" isActive="0">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.i_keyindex"/>
          <Attribute name="MinValue" displayName="Minimum Value" description="Minimum value of this property value" value="1"/>
          <Attribute name="MaxValue" displayName="Maximum Value" description="Maximum value of this property value" value="2"/>
        </Property>
        <Property name="user_id_changed_by" displayName="Changed By" description="ID of the user that last changed this record." propType="STRING">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.u_user_id_changed_by"/>
          <Attribute name="MinLength" displayName="Minimum Length" description="Minimum length of this property value" value="0"/>
          <Attribute name="MaxLength" displayName="Maximum Length" description="Maximum length of this property value" value="50"/>
        </Property>
        <Property name="date_last_changed" displayName="Date Last Changed" description="Date that this record was last changed" propType="DATETIME" isSearchable="1">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.dt_date_last_changed"/>
        </Property>
        <Property name="date_created" displayName="Date Created" description="Date that this record was created" propType="DATETIME" isSearchable="1">
          <DataRef idref="UPM_SQLSource.StoreLocatorConfig.dt_date_created"/>
        </Property>
      </Group>
    </Profile>

  7. Remove the node under Catalog\DataSources

    <DataObject name="VirtualEarthConfig" ... />

  8. Replace the node with the following :

    <DataObject name="StoreLocatorConfig" displayName="Store Locator Configuration">
        <DataMember name="i_config_id" displayName="i_config_id" memberType="NUMBER" isIndexed="1" isPrimaryKey="1" isRequired="1"/>
        <DataMember name="u_key" displayName="u_key" memberType="STRING"/>
        <DataMember name="u_access_id" displayName="u_access_id" memberType="STRING"/>
        <DataMember name="u_data_source_name" displayName="u_data_source_name" memberType="STRING"/>
        <DataMember name="u_service_url" displayName="u_spatialservice_url" memberType="STRING"/>
        <DataMember name="u_spatial_service_url" displayName="u_spatial_service_url" memberType="STRING"/>
        <DataMember name="dt_date_created" displayName="dt_date_created" memberType="DATETIME"/>
        <DataMember name="dt_date_last_changed" displayName="dt_date_last_changed" memberType="DATETIME"/>
        <DataMember name="u_user_id_changed_by" displayName="u_user_id_changed_by" memberType="STRING"/>
        <DataMember name="i_keyindex" displayName="i_keyindex" memberType="NUMBER"/>
      </DataObject>

  9. Save the file.

  10. Import Profile Schema.

    1. Open Commerce Server Manager.

    2. Right click the Profile Catalog node.

    3. Set the Profile Connection String of the SQL Source node.

    4. Choose Import Profile Schema and select the snippet you just updated.

  11. Perform an IISReset to force Profile Schema changes to take effect.

Store Locator search displays error

The system displays the message Address field or Zip/Postal Code field needs to have a value for Store Locator searches even when values are entered.

To resolve this issue, you must modify the custom master page to add a JavaScript reference.

  1. Open the Default zone of the site in SharePoint Designer.

  2. If you are using Microsoft SharePoint Server 2010:

    1. open the default zone of the site in a browser

    2. click Site Actions and select the Edit in SharePoint Designer option

  3. If you are using Microsoft SharePoint Foundation 2010:

    1. launch SharePoint Designer

    2. open the default zone of the site.

  4. Click All Files in the left navigation pane of SharePoint Designer.

  5. Click _catalogs in the All Files tab.

  6. Click masterpage in the _catalogs tab.

  7. Right-click on the CSDefaultSite.master file and select Open.

    The system displays a dialog box asking if you want to check the file out.

  8. Click Yes.

  9. Add a new script element as the last child of the head element.

    If the site uses HTTPS, add

    <script type="text/javascript" src="https://ajax.microsoft.com/ajax/jQuery/jquery-1.3.2.js">

    If the site does not use HTTPS, add

    <script type="text/javascript" src="https://ajax.microsoft.com/ajax/jQuery/jquery-1.3.2.js">

  10. Save your changes and close the file.

  11. Check the file back in (on the masterpage tab, right-click on the CSDefaultSite.master file and select Check In).

The Department link are broken on the product details page following site migration. To resolve this issue, update the department page by completing the following steps:

  1. Determine if CSDepartmentLink.ascx file exists. Navigate to the SharePoint ControlTemplates folder, <SP Hive>\TEMPLATE\CONTROLTEMPLATES and search for the file.

  2. If the CSDepartmentLink.ascx file is missing, create it with the following snippet

    <%@ Control Language="C#" AutoEventWireup="true" %>
<asp:Repeater ID="Repeater1" runat="server" DataSourceID="SiteMapDS">
    <ItemTemplate>
        <div class="mscs-categoryItem"><a href="<%# DataBinder.Eval(Container.DataItem, "Url") %>"><%# DataBinder.Eval(Container.DataItem, "Title") %></a></div>
    </ItemTemplate>
</asp:Repeater>

  3. If the CSDepartmentLink.ascx file is present, edit the Department Page from the SP SiteTemplates folder.

    <SP Hive>\TEMPLATE\SiteTemplates\MOSSCSContemporarySite\departments.aspx

    Or

    <SP Hive>\TEMPLATE\SiteTemplates\WSSCSContemporarySite\departments.aspx

    1. Add a Register tag.

      <%@ Register TagName="departmentLink" TagPrefix="CommerceServer" Src="~/_controltemplates/CSDepartmentLink.ascx" %>

    2. Replace the Repeater control

      <CommerceServer:departmentLink ID="deptLink" runat="server"/>

    3. Save the file

  4. Perform an IISReset to force the changes to take effect.

Connection String Requires Update

After running site migration,, Store Locator does not work and throws an exception During the process of migration, the connection string changes and needs to be updated. To do this, perform the following steps:

  1. Select Commerce Server Manager-> Global Resources-> Profiles-> Profile Catalog-> Data Sources, right-click the data source you want to change (siteName_Profile) then click Properties.

  2. In the <data source> Properties dialog box, select the Partitions tab, select the partition and click Edit

  3. In <partitions> Properties, click Edit

  4. Under the Connection tab, do the following:

    1. Select a server name from the drop-down list, or type the location of the server where the database you want to access is located

    2. Enter information required to logon to the server

    3. Select the database, siteName_Profiles

    4. Test the Connection to make sure the configuration is correct

    5. Click Ok to Exit all the dialog boxes.

    6. Restart the Web application by using IISReset. In the <data source> Properties dialog box, on the Partitions tab, select the partition and click Edit

Store Locator has wrong layout

A known issue exists where, following migration, Contemporary Sites require fix to the layout. Perform the following steps:

  1. Open the site with SharePoint Designer

  2. Check-out and edit "Style Library”/defaultSite.css

  3. Add the following code snippet:

Skin_StoreLocator_Tab {
                TEXT-ALIGN: center; BORDER-LEFT: #000000 1px solid; PADDING-BOTTOM: 3px; LINE-HEIGHT: 30px; PADDING-LEFT: 3px; WIDTH: auto; PADDING-RIGHT: 3px; BACKGROUND: #c0c0c0; HEIGHT: 25px; COLOR: #ffffff; VERTICAL-ALIGN: middle; BORDER-TOP: #000000 1px solid; CURSOR: pointer; MARGIN-RIGHT: 2px; BORDER-RIGHT: #000000 1px solid; PADDING-TOP: 3px
}
.Skin_StoreLocator_Tab_Selected {
                TEXT-ALIGN: center; BORDER-LEFT: #000000 1px solid; PADDING-BOTTOM: 3px; LINE-HEIGHT: 30px; PADDING-LEFT: 3px; WIDTH: auto; PADDING-RIGHT: 3px; BACKGROUND: #ffffff; HEIGHT: 25px; COLOR: #000000; VERTICAL-ALIGN: middle; BORDER-TOP: #000000 1px solid; CURSOR: pointer; MARGIN-RIGHT: 2px; BORDER-RIGHT: #000000 1px solid; PADDING-TOP: 3px
}
.Skin_StoreLocator_LeftColumn {
                MARGIN: 0px 15px 15px 0px; WIDTH: 25%; FLOAT: left
}
.Skin_StoreLocator_Map {
                POSITION: relative; MARGIN: 0px 0px 10px 10px; WIDTH: 71%; FLOAT: right; HEIGHT: 350px
}

  1. Check-in the file.

  2. Delete temporary files in your Internet Explorer.

Store Locator Page does not render correctly

A known issue exists where, following migration, the Store Locator Page does not render correctly. This error occurs when you add a new page. The new page must use the site’s master page or defaultSite.css style sheet in order to render correctly. Perform the following steps:

  1. If you want to use the site's master page:

    1. Open the site with SharePoint Designer

    2. Check-out the page and edit the MasterPageFile attribute. Set the attribute to ~sitecollection/_catalogs/MasterPage/CSDefaultSite.master

    3. Check-in the file.

  2. If you want to use the defaultSite.css stylesheet:

    1. Open the site with SharePoint Designer

    2. Check-out the page and add the following inside <asp:Content ContentPlaceHolderId="PlaceHolderAdditionalPageHead" >

      <link href="/Style%20Library/defaultSite.css" rel="stylesheet" type="text/css"/>

    3. Check-in the file.