{"id":5664,"date":"2014-06-11T00:00:00","date_gmt":"2014-06-11T00:00:00","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/2014\/06\/11\/deploying-a-multilingual-website-with-episerver-7-5\/"},"modified":"2021-01-27T21:38:03","modified_gmt":"2021-01-27T21:38:03","slug":"deploying-a-multilingual-website-with-episerver-7-5","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2014\/06\/11\/deploying-a-multilingual-website-with-episerver-7-5\/","title":{"rendered":"Deploying a Multilingual Website with Episerver (Optimizely) 7.5"},"content":{"rendered":"

The Episerver (Optimizely) platform’s latest version 7.5 was released in December 2013 and introduced new tools and features to enhance productivity and the content management processes. The new version continues Episerver (Optimizely)’s excellent language support functionality and is able to handle efficiently multilingual content. In this blog I will go through the main steps required to configure the CMS in order to enable it to display and handle content in different languages.<\/p>\n

\"episerver-translation\"<\/p>\n

Local and Shared Blocks<\/strong><\/h5>\n

Episerver (Optimizely) 7 introduces a new way to handle content in addition to the old one (Pages): Local & Shared Blocks<\/strong>. Blocks are simply a reusable component that can hold different formats of content. Local Blocks are limited to the boundary of one page but Shared blocks are saved globally and can be shared between any of the pages in the CMS. So based on this the configuration requirements are now extended to include Blocks and not only pages as was the case in the 6R2 version.<\/p>\n

Enable Globalization<\/strong><\/h6>\n

First Step<\/strong> after installing the CMS is to enable CMS Globalization by logging in as the Admin and from the Config<\/strong> tab select System Settings<\/strong> and check Enable Globalization<\/strong>:<\/p>\n

\"Episerver<\/p>\n

Enable Localization<\/strong><\/h6>\n

Second Step<\/strong> is to review carefully all Pages and Blocks’ properties and make sure that they are unique per language in order to be able to display content in different languages. Otherwise the fields will be disabled for all target languages except the main one. Log in as Admin, select Content Type tab, then go to each item under Page and Blocks Types and check the properties that belong to each item. Make sure that each cell under the Localized<\/strong> header displays the word Yes<\/strong> and is not empty. The properties that don’t deal with content can be skipped.<\/p>\n

\"Episerver<\/p>\n

If you want to enable localization for one of the already existing Properties, click the property name and check the item “Unique Value per Language<\/strong>”<\/p>\n

If you want to add New Localized Property, Click Add Property<\/strong> and then add the necessary details and check the same item as done in Edit<\/strong> mode.<\/p>\n

Enable Languages<\/strong><\/h6>\n

Third Step<\/strong> is to enable the languages that you have decided to use in the CMS. Log in as Admin, select Config<\/strong> Tab, then click Manage Languages<\/strong>:<\/p>\n

\"Episerver<\/p>\n

To enable one of the currently listed languages, Click language name and check Enable<\/strong> field then Save<\/strong>.<\/p>\n

If you didn’t find a language in the list you can add it by clicking Add Language<\/strong> and select it from the list that will appear.<\/p>\n

\"Episerver<\/p>\n

Fallback and Replacement<\/strong><\/h6>\n

Fourth Step:<\/strong> Now you will need to enable CMS Fallback and Replacement in order to instruct Episerver (Optimizely) how to handle cases such as when specific languages are not available for certain pages or blocks.<\/p>\n

Note<\/strong>: As the following steps are the same for both Pages and Shared Blocks the below step-by-step guide will take Pages as example. An important note to mention here is that Local Blocks do not have a stand-a-lone mechanism to set languages because they inherit their settings from the page where they are created.<\/p>\n

After login, select the a node in Pages<\/strong> or the Blocks<\/strong> tree and then click the On-Page Editing<\/strong> icon in the top right corner of the page, click Tools<\/strong> and finally select Language Settings<\/strong>.<\/p>\n

The next screen will enable you to do the following:<\/p>\n

    \n
  • Add other languages to the page<\/li>\n
  • Set the Fallback and Replacement feature based on your business needs<\/li>\n<\/ul>\n

    \"5\"<\/p>\n

    To enable the same settings for a child page select it, go to Language Settings<\/strong> following the above steps, and check Inherit settings from the Parent Page: “Start”<\/strong><\/p>\n

    This Blog showed the main steps needed in order to enable Episerver (Optimizely) 7.5 to handle multilingual websites. My next blog in this series will discuss the Localization (L10n) of Episerver (Optimizely) 7.5.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The Episerver (Optimizely) platform’s latest version 7.5 was released in December 2013 and introduced new tools and features to enhance productivity and the content management processes. The new version continues Episerver (Optimizely)’s excellent language support functionality and is able to handle efficiently multilingual content. In this blog I will go through the main steps required […]<\/p>\n","protected":false},"author":13,"featured_media":5665,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[530,284,64],"_links":{"self":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/5664"}],"collection":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/comments?post=5664"}],"version-history":[{"count":4,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/5664\/revisions"}],"predecessor-version":[{"id":29775,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/5664\/revisions\/29775"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media\/5665"}],"wp:attachment":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media?parent=5664"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/categories?post=5664"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/tags?post=5664"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}