Provide tools for translation and display of text in multiple languages and support for regionalization/localization for dates, numbers, currency, measurement, or other local contexts.

Reuse Cached 404s

Drupal has a 404 caching problem.

Drupal's page cache is a fantastic and simple way to improve performance in production. If an anonymous user goes to http://yoursite.com/somepage twice, the second page load is a lot faster because Drupal doesn't spend time re-rendering it; it simply serves it from the cache.

But the problem is that pages are cached by their path. That means that the server has to do all the work to render the 404 page each time a new path is not found. This can be particularly noticeable if your 404 page is a node, view, or other rendered page.

This module takes over the caching process when a page is not found and makes it a little smarter. It's been tested with nodes, but it should work with any 404 page that is served through the menu system. It is compatible with multilingual sites. It caches the 404 once per language.

If you are already using Fast 404 (or Drupal 7's built-in version), you don't really need this module, and compatibility with those configurations hasn't been tested. It's a good alternative though when you need 404 pages with some dynamic content from your site and don't want to have to update HTML files when your site structure changes.

Installation

Pathauto i18n

🇺🇦

This module is maintained by Ukrainian developers.

Field type language

Defines a Drupal field type that allows to store and select one of the active languages.

Extended Translation

This is an experimental Drupal 8 module.

Implementation of D7-like node translation model for Drupal 8. Generalize to any type of entity.

Search API Entity Translation Solr search



An extension module to 2.x version of Search API Entity Translation module.

Changes the way in which Solr Search module stores the multilingual content, making it use solr dynamic fields for translatable entity fields.

For example, when indexing "body:value" field, solr would normally store its value in tm_body:value property. With this hook (assuming that body field is translatable and comes from translatable entity, and that currently being processed content language is fr) it will be stored in tm_fr_body:value instead, with nothing saved to default tm_body:value property.

This allows to use different datatypes for different language-based solr fields, thus allowing to configure different tokenizers/stemmers/spell checkers/stop words/protected words/etc for each language separately.

Obviously it also works when retrieving data from solr, looking for language-based dynamic fields, and, if they exist - assigning their values back to relevant Search API properties (not language-based anymore).

Lingotek App

This is a lightweight wrapper that appifies the Lingotek Translation module.

Pages

Subscribe with RSS Subscribe to RSS - Multilingual