Multisite and Mulitlingual

 Multilingual

Step 1 : To get started, we first need to install the required language. Log into Sitecore and go to the control panel. Under Localization, click Add a new language.




Step 2 : From the dropdown, choose the language you want to add. Notice there are multiple options for Spanish. You can create content based on the language and the region.


Step 3 : The dialog is populated with the language and the region code. These codes will be used by Sitecore when creating links to other language versions of content (ie. /es-ES/about). We do not want the region code, so clear out that box. When Sitecore creates links to our Spanish content, the links will only have the language (ie. /es/about).


Step 4 : In the content editor you will notice that the UI is updated to allow creation and publication of content in Spanish. By default all content authors can create and publish in all installed languages.


You can view you site’s content in Spanish by adding /es/ between the domain name and the page path (ie domain.com/es/about-us) or by adding ?sc_lang=es at the end of the page path (ie domain.com/about-us?sc_lang=es).  Once Sitecore sees either of these language identifiers, it stores the language in a cookie.  If no language identifier is found in the url, it will use the value in the cookie.  The user will browse the site in the last identified language until another language identifier is specified.

Step 5 : This first time you publish content in Spanish and view the page, you will likely get the yellow error screen. Sitecore attempts to get the Spanish version for every content item on the page (header, nav items, subnavs, content, footer, footer links, etc). If there is no Spanish version of a given piece of content, it returns a null object to the view causing this error.


Step 6 : To correct this error we must enable language fall back. This feature was fully introduced in Sitecore 8.1. It allows you to set a default language for your site as well as a fallback language for any installed languages. If there is no version for the requested language, Sitecore will look for the version in the fallback language. 



Step 7 : Next, we need to patch our site configuration to allow language fallback.  Add this patch to a file that will load late in the process according to the naming conventions and structure of the configs for your site.  Note there are two types of fallback, item level and field level.  I found it easier to fall back at the item level because a version of the item either exists or does not exist in the chosen language.  Remember to recycle the app pool after patching the configuration.

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
<sitecore>
<sites>
<site name="website">
<patch:attribute name="enableItemLanguageFallback">true</patch:attribute>
</site>
</sites>
</sitecore>
</configuration>


Multisite

Consider a new site whose name will be 'local.sitecore92.com'. Configuring this site to Sitecore requires the following steps:

  • Step1: Select an existing item in the content tree (or create one from scratch).
  • Step2: Add your site name to Sitecore Instance and it can be done in the following two ways:

Add the <site> element under the <sites> section of the sitecore.config file.
Or
Add the <site> element under the <sites> section of the SiteDefintion.config file.


Adding a new site to the config file is only the first step. To access the newly added site, there are two other steps that need to be completed outside of Sitecore.

  • Step3: Add the site name to the IIS binding.


  • Step4: Add the site name to the host's file of your server.


You can now access your newly added Sitecore website after completing these three steps.












Comments

Post a Comment

Popular posts from this blog

Federated Experience Manager (FXM)

Image
The Federated Experience Manager (FXM) is an application that allows you to track visitor interactions and generate analytics information on external, non-Sitecore websites with Sitecore. You can use FXM to implement personalization rules, create goals and events, and implement content profiling on an external website. To enable FXM functionality, a JavaScript tag is added to the external websites. It allows the FXM application to connect the external site's components to the Sitecore Experience Platform. FXM has a dedicated Experience Editor that allows you to assign marketing attributes, implement personalization rules. You can access the FXM through the Marketing Control Panel or through the FXM application on the Sitecore Launchpad. When you have applied the FXM JavaScript tag to an external website, you can assign FXM functionality in one of the following ways: Capture Click Action Add Placeholder Add Page Filter Assign Marketing Attributes For reference :  https://vinayakchau...
Read more

Email Experience Manager (EXM)

Image
Email Experience Manager (EXM) To engage with customers in the website, we can deliver the relevant email messages to the customers at the right time. The Email Experience Manager (EXM) helps you create and deliver bulk email campaigns quickly and easily. The email campaign builder has four tabs each of which represents a step in the process. General On the General tab, you specify the campaign name and description along with the sender's details. Recipients On the Recipients tab, you add lists or segmented lists that you have created in the List Manager. You can also add a list of recipients that have been saved to a file. Message On the Message tab, you define the elements of the email message and this tab contains some important controls. Delivery On the Delivery tab, you have the choice to select the message variant and specify options and schedule.
Read more

Sitecore Products

Sitecore XP: Sitecore® Experience Platform™ is the digital experience platform providing personalization, machine learning, and marketing automation. Sitecore XM: Sitecore Experience Manager™ is the content management system (CMS) providing multilingual, multicultural, multichannel, and multisite content management. Sitecore xDB: Sitecore® Experience Database™ is the database that connects to Sitecore XM providing data interchange, encryption, and real-time insights. Sitecore xConnect: xConnect is the service layer that sits in between the xDB Collection database and xDB index, and any trusted client or device that wants to read, write, or search contact and interaction data. No other system has direct access to the xDB Collection database or the xDB index. Sitecore EXM: Sitecore Experience Email Manager is a channel of delivery within the Sitecore platform. Sitecore FXM: Sitecore Federated Experience Manager is the channel that allows you to connect your non-Sitecore hosted websites t...
Read more