![MULTILINGUAL Entities Form...declaration
● As we have define Entity translatable = True,
We also need to define setTranslatable(TRUE)
Over each Field.
● Strings which does not define in core,
we imported all strings in .po files.
● I have also manage the title of forms to define
With t() funtion in Entity form $form['#title'] = t(“strings”);](https://image.slidesharecdn.com/drupal8customizedcheckoutsystem1-170823094650/85/Drupal-8-customized-checkout-system-6-320.jpg)
![Core Possibilities… Code
● From Entity Obj, we can get translations and then we can get translation of
all fields, e.g,
$translation = $ent->getTranslation(‘de’);
$titles[‘de’] = $translation->title;
● How we can get the lanuage code:
● $language =
Drupal::languageManager()->getCurrentLanguage()->getId();
● To get the language name: $language =
Drupal::languageManager()->getCurrentLanguage()->getName();](https://image.slidesharecdn.com/drupal8customizedcheckoutsystem1-170823094650/85/Drupal-8-customized-checkout-system-19-320.jpg)
Drupal 8 customized checkout system
- 1. DRUPAL 8 MULTILINGUAL POSSIBILITIES FOR CUSTOMIZED CHECKOUT SYSTEM Drupal Camp Munich 12/2016 Ahmad Hassan Sr. Drupal Developer
- 2. DRUPAL 8 MULTILINGUAL POSSIBILITIES ● Customized Checkout system ● Translatable Custom Entities ● Multilingual Entity Form ○ Translate Form Authentication ● Twig Translation ● Block and Menu Translation ● Using PO file for additional Translation. ● Core Possibilities.
- 3. DRUPAL 8 MULTILINGUAL POSSIBILITIES Customized Checkout system ● Why it called customized. It has Customized entities, custom blocks, custom cart… almost everything except drupal8 multilingual core support. ● We have designed a Customized Checkout system with custom Content Entity. ● We have used mainly three entities for user interaction to submit their orders. ● Actually for these Entities, we need translation support for atleast five EU languages. ● We need to translate our forms and information about the order. ● This was my first multilingual site but it was easy to manage in drupal 8. ● To achieve all this we need to follow some simple steps…
- 4. Translatable Custom Entities… - After creating new content entity, we need to declare translatable = TRUE in Entity annotation. e,g - Drupal 8 provide Interface to select which fields we need to translate. e,g -
- 5. Translatable Custom Entities… ● Each Field have to define with label/description with t() function.
- 6. MULTILINGUAL Entities Form...declaration ● As we have define Entity translatable = True, We also need to define setTranslatable(TRUE) Over each Field. ● Strings which does not define in core, we imported all strings in .po files. ● I have also manage the title of forms to define With t() funtion in Entity form $form['#title'] = t(“strings”);
- 7. MULTILINGUAL Entities Form… Example
- 8. MULTILINGUAL Entities Form… Country names list ● We have taken list of countries from some services by sending language-id in parameter. ● For example if current language is German, I pass ‘de’ and get country names in German. ● We can get current active language in drupal 8 with language Manager. $language = Drupal::languageManager()->getCurrentLanguage()->getId();
- 9. MULTILINGUAL Entities Form… form validation ● In form validate function, we can override core form validation ● We can simply define string with $this->t() function. ● $form_state->setErrorByName('Field', $this->t("Please Enter your Field"));
- 10. MULTILINGUAL with Twig … .twig ● We can also define labels or description strings in twig file as html. ● And to translate these string we can just use {% trans %} Please review your order details {% endtrans %}: ● And import those strings for other languages with .po files.
- 11. MULTILINGUAL Custom Block and Menu… form validation ● We can define in visibility, on which languages this block should be visible.
- 12. MULTILINGUAL Custom Block and Menu… Blocks ● In drupal 8, we can define a block and than translate them in other language ● We just need to define title and block content separately for each language.
- 13. MULTILINGUAL Custom Block and Menu… Blocks ● We can also publish or unpublish each translation and use as other contents. ● As well as we make these translation outdated to use some other. E.g,
- 14. MULTILINGUAL Custom Block and Menu… Menu ● Similarly we can define a menu and for each menu element can have different settings for each language.
- 15. MULTILINGUAL Custom Block and Menu… Menu ● We can create different link title, description for different languages. ● We can also publish/unpublish or outdate menu element translation as blocks.,
- 16. Import strings Using .po files… Import ● I have just copied core .po file and remove all the string and add all my strings and translated string in it. ● Drupal 8 provides import/export feature to update or get all string by interface. ● So no need to update code for just translation. Just define all with t(), ● Add all strings and translation in .po file and import in related language.
- 17. Core Possibilities… settings ● We can install Drupal 8 in any language instead of doing it on later staging. ● In Drupal 8, we can define how current language would be detect, e.g, by Url, Session, browser, user. Depend upon your settings, Im using Url. ● Custom language settings, where we can see a list of translatable Entities. Any content type, Entity, user, Profile, custom Entity blocks.. ● After Selecting each Entity, we can also select their fields. ● We can also set if these settings should display on view/edit pages.
- 18. Core Possibilities… settings ● We can import and export .po files. I have added my strings with .po files, we can also override in file if already exist. ● The good thing is that once you import all translations you are able to edit any string by interface. ● So instead of just content translation, we have also list of configuration settings. And we can translate configuration.
- 19. Core Possibilities… Code ● From Entity Obj, we can get translations and then we can get translation of all fields, e.g, $translation = $ent->getTranslation(‘de’); $titles[‘de’] = $translation->title; ● How we can get the lanuage code: ● $language = Drupal::languageManager()->getCurrentLanguage()->getId(); ● To get the language name: $language = Drupal::languageManager()->getCurrentLanguage()->getName();
- 20. Languageicon… contrib module ● This was the only contrib module we have used in our site. ● This module provide a list of flags of enable language. ● It also provide us block. We can make visible any region of our site. ● Only one click on language can change your page to another language
- 21. DRUPAL 8 MULTILINGUAL POSSIBILITIES FOR CUSTOMIZED CHECKOUT SYSTEM Thanks Questions