In a multilingual environment, MMS unifies handling of all translations at once for any block, node, or structural content without using separate containers, and with only the Locale module activated.

Briefly said, it works upon all <input type="text"> and <textarea> elements, giving them the ability to contain their own whole set of translations.

In administration context, each of these areas is replaced by a multilingual widget where the user can instantly look at all translations of the content, and edit them at its option. Another, dedicated widget is also available for areas managed with CKEditor.

The benefits of using this method are mainly:

  • when creating new content or updating an existing one, authors keep a total visibility upon all the translations at the same time
  • a direct consequence is to reduce the risk of omitting to update the translations when an original content has been modified
  • when a content includes a lot of lang-insensitive data (like images, links, or simply verbous HTML with a number of attributes), these parts don't have to be duplicated: only the textual parts must be entered as "multi" and rewritten in the different languages
  • since it emulates the SPIP < multi > syntax, this method is nicely suitable to allow the direct migration of contents from this CMS, without the need of a painful data restructuration
  • moreover, in the latter case, authors can maintain their previous work habits unchanged

MMS is the successor of the previously introduced Multilang module, which has been totally rebuilt with a number of enhancements:

  • fully WYSIWYG: the user now gets rid of the "multi" syntax (though it is still present in the underlying structure, so migrating contents from SPIP remains an easy task)
  • applies to any text content (so only the user interface remains out of its scope), without needing other translation modules for content types, fields, menus, taxonomy, views, and so on
  • comes with a wide set of configuration options to control its behaviour (entry modes, rendering behaviour, highlighting of missing translations, ...)
  • adds some helpfull capabilities, such as undo/redo history local to each entry area or the ability to insert line-breaks even in simple input areas

For more information you may read the basic description and the more detailed full documentation. The latter is also available as inline help when MMS is installed.

Pros and cons

The advantages of using MMS are essentially:

  • it works for any content without needing other dedicated translation modules
  • it offers a unique interface for the user to watch and manage all translations at the same time for each content
  • it uses less database space (less tables, less duplicated content)

At the opposite it implies some limitations:

  • it does not allow to manage separate nodes for different languages
  • currently it reduces the available space for "small" contents (such as titles), because their allowed size is shared by all translations
    NOTE: this limitation will be lifted in a future version


Requires the Locale Drupal core module to be active.

Recommended modules

Best results are achieved when also using the CKEditor module (with Widget plugin): if present and activated, then the integrated MMS plugin for CKEditor is activated too (see this screenshot).


A Drupal 8 version is currently in progress.

In multilinguism domain Drupal 8 brings both more simplicity and wider capabilities than Drupal 7 did.
Especially it needs only a few number of additional modules: so one of the main advantages of MMS (use a single module for all) becomes of little interest.

But beyond that and despite a lot of real good improvements Drupal 8 retains a major feature: to work on translations of a given part of content needs to first go to a dedicated "Translations" tab, then choose a language, and only then view/edit the translation in this language.
It's where MMS keeps its other advantage, which is to offer a direct and unified view/edit interface for all translations on each content part.

In addition MMS also remains interesting for all cases where contents have to be migrated from the SPIP CMS, with its integrated "multi" syntax, without any data restructuration.

So we're working hard to make MMS smoothly collaborate with the best of Drupal 8.
Should be coming soon...


Development of MMS is sponsored by p-interactif.

README.txt3.19 KB
HELP.txt18.64 KB

Project information