Setting OG and i18n contexts

Out-of-the-box contexts

A major component of localizing content is to be able to set language and other contexts so that your Views, blocks, and other data may be country and language aware.

Out of the box, for a multilingual site you can visit:

/admin/config/regional/language/configure

And for OG you can visit:

/admin/config/group/context (requires OG Context module)

To set the types of context providers you wish to use, along with priorities. IP-detection modules also extend the list of options for multilingual options.

Date Formats and Exposed Filters

Date formatting – the order of day, month, and year – is important to many websites. However, getting date formats working correctly with Views’ exposed filters can take a bit of administrative work.

The following modules should be installed and enabled:

Migrating from static HTMLs with i18n

Some key points in migrating static HTML pages to Drupal 7 with the full i18n (Internationalization) features incorporated are described.
Drupal's i18n feature is powerful and has a great flexibility. However the flip-side of the coin is it is not that easy to understand how it works, partly because it heavily depends on your configuration. Also, it may not match well the suffix-based language negotiation by the Apache server for the static HTML pages, and so the migration of such static HTML sites to Drupal is not quite straightforward.

Import content and its translations from CSV (managing entityreference field)

In this page, we will see how to handle an entityreference field in content type 2 referencing a content of content type 1 without having the id of the target, only its title.

And of course in all the languages we want.

Principle

For the main language import, we will be using an entityfieldquery to get the id of the content of content type 1 in the main language.
For the other languages import, we will use the main language import to be sure of the id of the target.

Pages

Subscribe with RSS Subscribe to RSS - i18n