The Admin Language Negotiation module allows non-admin users to have their preferred administration language.
The module enables the Administration pages language settings to anyone
that has the permission Admin language negotiation
and introduces a new Language Negotiation based on this permission.
The Admin User Language module makes sure that any user has a pre-selected administration pages language.
This is useful when you want to give a consistent user experience to your users, in the specific, when you want to force the back end navigation to be always in a specific language (e.g. English).
If your users have any administration privilege in fact, since their registration, they will have the administration pages language set to - no preference - unless manually changed.
Experiment about accessing content in another language using path aliases.
NOTE: it's recommended to apply the patches from the child issues of #2860901: Doubts about Content language negotiation.
Typical setup:
Entity Tools provides syntactic sugar over entities for custom modules and themes (Twig templates in general). It comes with helpers to select, load and display content or configuration entities. The goal is to try to improve the DX by providing an uniform way to work with entities, without using strings parameters so we can safely rely on class constants or methods instead.
Select, load and display helpers are meant to be independent. You can still execute a core EntityQuery that gets you the entity ids and then rely on the load and display helpers.
If you have a site that is multilingual, but only some pages are translated, this module redirects untranslated pages to the source language, to help with search engine optimization.
The purpose of the Partially Multilingual module is to avoid having multiple, unaliased URLs for the same page, which differ only by the language prefix in the URL, if your site has pages that are not translated into all of the enabled site languages.
Yandex translation plugin for Translation Management Tools (TMGMT) project.
Features
Requirements
Update:
Dec 4
Aug 7
July 27
July 25:
Language Popup is provide an additional option in language negotiation features.
This module provides an option to select a language to traverse if there is no language present in URL.
What does this module do?
Features:
Translate all fields in a node and inside paragraphs items (recursive)
Keep the paragraphs structure across the translated versions of a node (the paragraphs field must not be translatable)
Delete the entities translations when delete the paragraphs items
Bugs fixed in the paragrap module:
Display empty fields when edit a node in another language
The entity translations never are deleted after delete a node or paragraphs, only are deleted if remove the translations of a node one by one.
The token modules provides only tokens about the language a node is in.
There are use cases where, for example a field help text, needs to link to another page prefixed by the current interface language code.
This module adds the missing tokens about the interface language:
This module requires the token module.
