Last updated May 20, 2013. Created by sajitha on November 11, 2007.
Edited by LeeHunter, frederickjh, jvns, sylvain_a. Log in to edit this page.

When the Content Translation module is enabled you can translate site content into different languages. Working with the Locale module (which manages the enabled languages and provides translation for the site interface), the Content Translation module is key to creating and maintaining translated site content.

Configure content translation

  1. Navigate to the Permissions page (Administration > User permissions in Drupal 6, or Administration > People > Permissions in Drupal 7) and assign the “translate content” permission to the appropriate user roles.
  2. Navigate to the Languages page (Administration > Settings > Language in Drupal 6, or Administration > Configuration > Regional and language > Languages in Drupal 7) and add and enable desired languages.

Enable translation support for a content type

  1. Navigate to the Content types administration page (Administration > Content > Types in Drupal 6, or Administration > Structure > Content types in Drupal 7).
  2. Select a content type you want translated, and select "edit", then "Workflow settings" for Drupal 6 or "Publishing options" for Drupal 7.
  3. At the "Multilingual support" section, select "Enabled, with translation".
  4. Be sure to save each content type after enabling multilingual support.

Looking for support? Visit the forums, or join #drupal-support in IRC.


Please make sure that all languages have their path prefix set-up (Home › Administer › Site configuration › Languages > Edit > Path Prefix). This will prevent you from getting ugly "Page not found" error messages for translated pages that are accessed using path aliases.

Thanks for the tip!

Dear friend, I pray that you may enjoy good health and that all may go well with you, even as your soul is getting along well (3 John 1:2)

This guide states "this (“Translation” ) tab allows translations to be added or edited using a specialized editing form that also displays the content being translated."

However in my case from the translation tab you create a new node with a different node ID and may have different settings (taxonomy, publishing options etc may be different from the original). There is no "specialized edit form".

Am I missing something? Or this part of the guide does not apply to drupal 6.x?

If I want to translate a "story" node, then when I click on "translate" tab, and enter the translation and save it, now I have TWO stories showing up on my frontpage because both these are different nodes.

Do I have to remember to manually turn off "promoted to front page" each time I'm translating content?




If translation tab is not appearing when you the node, the problem is with settings. You have to enable this setting for each content type.
Go to content management > content types and then edit the content type for which you want the tab. Then in the "workflow settings" under "Multilingual support" check "Enabled, with translation" option and then check.


Thanks Shinh, you saved me from self hair removal.
Still, i got an issue about the theme used while translating, when i click the tab, it switches to my frontend theme (also my default),
which is quite annoying...

Any suggestion?

I did not set the admin theme for editing content
and had to style the forms correctly in my frontend theme.


Pro designer and *freestyle* coder since '99. Newb to Drupal, looks awesome, no regrets to forget: dusty company CMSs, Spip, Joomla*, WordPress, Typolight. (* especially this one!)

I have "Enabled, with translation" checked under Workflow Settings > Multilingual for the selected Content Type. I view a page of that content type and still do not see the Translate tab. ...any other ideas? Additionally, I am using the default Garland theme.

I had this same problem just now. The issue was that my original node was set to "language neutral". You need to set it to a specific language before the translate tab will appear.

How can I translate the menu.?
this module only translate the content but it will be good if it can translate the menu too
example "About us" in english, then when you click for french it should show "A propos "
maybe it's me that doesn 't know how to do it :)

For Primary links, Create the links for both languages and within that menu item, select the language for what you want it to display.


Primary Links >
- Home
- Company
- Services
- Casa
- Servicios
- Compañía

...English version will display for English, Spanish for Spanish.

Dear Dale,

this is excatly what I was looking for, too, but I just can't find the way to
"within that menu item, select the language for what you want it to display."

I have Drupal 6, and got everything else done fine, so could this be about site themes (a different theme for admin and another for users)?
Or am I missing something about editing a menu item, because at the Edit menu item form (admin/build/menu/item/itemnumber/edit) I have only fields for Path, Menu link title and Description, boxes for Enabled and Expanded, and dropdown lists for Parent item and Weight.

Kindly, help me, please.


Drupal 6.22
MySQL database 5.0.77
PHP 5.2.8
server Microsoft-IIS/7.0

This needed the "internationalization" module installed.
Now I have the primary links displayed as I wanted to.


Drupal 6.22
MySQL database 5.0.77
PHP 5.2.8
server Microsoft-IIS/7.0

I was trying to use just locale and content translation and was scratching my head how to do this without having redundant menu items in different languages.


Hi I was wondering if there is a way to translate "User Accounts" to "Cuentas de usuario" (spanish)

for example if you go to

you will see:

Usser Acount

Create a new account | Log in | Request new password

Where can I translate that part of the code? I just dont know where this is coming from??

If someone knows the answer please help.

You can translate every label in admin/build/translate .

Just search the string in admin/build/translate/search or do a bulk translation with import/export.

If you ever want to change any of the built-in words/sentences in Drupal default, for ex - the description of the node types in add/node/page, then you will have to use the 'translation interface'.

If you have a lot of words that need changing (it will actually show you how much percentage of the site is translated to your language), then I'd suggest exporting the .po file, filling it in with the proper translation and then importing it back and voila, you have your multi-lingual site.


I have just struggled through how to do multiple languages for menu translations and it cost me quite a bit of time to figure out.

I have put a blog entry at to explain how I got it to work in case it helps anyone else.

For some reason after translating a piece of content the association with the original page is gone. Any ideas? Here's an example:

... that you're actually creating a revision of the page?

I haven't worked with revisions so I'm not totally sure, but try to uncheck the revision box and see if it works.


Hello there!

All translations I have done so far, are working fine. This really is a great feature in Drupal, I can have a real multilingual site, with fairly little effort.

Translating the Menus and "normal" Block works like clock-work, too, after I read the instructions to create an own menu / block for each language, and then separate them with "Show only on listed pages" setting, using path prefix.

The problem is only with content types that require the setting Identification => Make a listing page for this content type, in order to work the way I want them to.
For this content type, (at the admin/content/node-type/) I have selected:
Workflow settings => Multilingual support: Enabled, with translation, and
Multilanguage options => Normal - All enabled languages will be allowed

Translating the content itself works fine, of course, but the listing page gets a new list item of every translated page of that type.
I want to separate the different languages to two different listings pages, one language per list.

I think there must be a way to fix this, but just can't seem to see how. Please, help!

Kindest regards,

Drupal 6.22
MySQL database 5.0.77
PHP 5.2.8
server Microsoft-IIS/7.0

I think that I have followed all the advice above, but end up with the same articles appearing in both English and French Sites, i.e. the English article and the translated French one. Any ideas where I have gone wrong?

A supplementary question is on Menu translation. I have installed Openpublish and the primary menus partially change when the language is changed. A number of terms however remain in English. I have used menu translate and added the translations into the fr.po files. Again what I am doing wrong?

All help gratefully received to avoid damaging myself on these brick walls


When all else fails read the manual

I think that I have followed all the advice above, but end up with the same articles appearing in both English and French Sites, i.e. the English article and the translated French one. Any ideas where I have gone wrong?

Thats by design. See my issue:

I have found out that it is possible to resolve the problem. After reading the comments on I realised that some other control not associated with language setting should solve the problem, if it was solvable. The only one that I could think of was Views.

The solution is
Add an extra filter to Views for the content type.
The filter is node translated: equal to one of current language and no language.

Et voila tout est en ordre!

I hope that some one else will benefit from the pain that I have endured.

Unfortunately the menu translation problem is still unsolved


When all else fails read the manual

Your tip works great for the frontpage, Riverrat! Merci

Just double checking but when you goto admin/build/translate does it show your language (fr) as having 100% translation? If not, that may be the problem. You can easily change Drupal's built-in strings from there.


Did you manage to find a solution for the translation of the primary menu? Searching but facing the same brick walls here.

Hello Riverrat,

Working with Openpublish I have found it very difficult to build a topics OP menu in 2 languages. Even if I set the translation of a menu item it keeps displaying in the other language menu. I was wondering how you fixed this Riverrat?

Thank you

So far, so good - I've got it working in principle with a site running English as "first language" and German second, using the "de" path prefix. The problem I'm running into now is that the prefix is also automagically added to image references, leading to the images not being found.

E.g. if I have an image in the English page living at /sites/default/files/images/image.jpg and have a German translation of the page referencing the same image, it's not found because the generated path for it is /de/sites/default/images/image.jpg. I have tried working around that by creating a de directory and linking to ../sites from within it, or by creating a symbolic link "de" in the drupal directory, but both approaches created other problems. And it shouldn't be that way in the first place. What am I missing?

I got really annoyed by the content translation links at the end of nodes that have translations. I totally favor the 'language switch links' block and the possibilities it offers my site visitors.

My solution was to implement template_preprocess_node() in my template.php and then simply added


...and your template.php code?

You saved me!!!

Hello, by this I am able to translate nodes in any language but the problem I am facing is if I am displaying a node at my homepage ,it does not translate body of node because it creates a new node for each translation and hence it is not giving me uniform solution.It only changes language at that particular node only.Kindly help me to get out of this.


Astha Chauhan
(Drupal Developer)
RhaaSoft Technologies Pvt. Ltd.

I am facing a problem that my content not translated while all site translated in defined language.

varun pandit