Skip Navigation

Along with WPML, we also maintain several related projects, which allow other kinds of sites to run multilingual.

Migrate from Polylang to WPML »

The “Migrate Polylang to WPML” plugin makes it easy to move sites form Polylang plugin to WPML. It migrates the language information for posts, pages, custom post types and taxonomies.

Continue reading

Toolset »

toolset-logo

Toolset is a set of plugins for web developers who are not PHP coders but aim at developing more demanding WordPress projects.

Using Toolset you add custom post types and fields to your site and build everything around these:

  • post relationships
  • custom templates and lists of content
  • custom archives
  • front-end forms
  • searches

…and much more.

Continue reading

MailChimp for WordPress Multilingual »

MailChimp is a popular online service that allows you to distribute automated email campaigns. The integration between MailChimp for WordPress plugin and WPML allows you to translate sign-up forms and related messages.

Continue reading

Translate Sites Built with Advanced Custom Fields (ACF) »

This tutorial explains how to translate sites that are built with the Advanced Custom Fields (ACF) plugin and WPML.

On This Page

Getting Started

Start by installing and activating the following plugins:

If you’re new to WPML, check out our Getting Started Guide. It quickly walks you through different translation options you can use.

Making the ACF Fields Translatable

WPML’s Translate Everything feature can translate all of your site’s content instantly, including values stored in your ACF fields. The only thing you need to do is set the correct translation option for your ACF fields.

Setting the Translation Preferences for ACF Fields

Go to the WPML → Settings page and scroll to the Custom Fields Translation section. Select the translation options for your ACF fields.

Setting the translation options for ACF fields from the WPML Settings page

You can also select the fields translation options when editing your custom fields settings in ACF.

Setting the translation options for an ACF field when editing it

Setting the Translation Preferences for Repeater and Flexible Content Fields

Setting your translation preferences for Repeater and Flexible Content fields is similar to setting the translation preference for other ACF fields. In the example below, we cover the steps for setting the translation preference for Repeater fields which is exactly the same for setting the translation preference for Flexible Content fields.

These field types are only available with the Pro version of Advanced Custom Fields.

  1. We recommend setting the translation preference to Copy once for the main Repeater field, or the main Flexible Content field.
Setting the translation preference to Copy once

By setting the main Repeater field to Copy once, you can have a different number of Repeater fields for different languages. Edit the translated version of the post or page to have any number of Repeater fields you want.

You can also disable the synchronization of the Repeater field across languages. This means you can manually set the order of the fields for each language. To do this, uncheck the Sync repeater sub-fields positions in post translations box that appears under the Repeater field in the post or page.

If you set the translation preference of the main Repeater field or Flexible Content field to Don’t Translate, Copy, or Translate, you will see a yellow bulb tooltip icon. By hovering over the tooltip icon, you will see a message that recommends setting the Repeater field or Flexible Content field to Copy once, in case you encounter any issues with translating subfields.

Tooltip recommending to set the translation preference to “Copy”
  1. You can choose any translation preference for subfields. If you set translation preference for subfield, each subfield you create on post edit screen will have this translation preference applied.
Setting the translation preference of the main Repeater field is applied to all subfields

WPML automatically sets ACF system fields to Copy which guarantees to display the secondary language repeater field values on the front-end.

Setting the system field to “Copy”

Translating ACF Fields

Now that we have set the translation preferences for our custom fields, it is time to translate the custom field values (texts). In the example below, we have set the field group Location Rule to Post type is equal to Post. If you set the location rule to show the fields in a specific custom post type such as properties, books, recipes, you will be able to translate the custom fields in a similar fashion.

  1. Create a post in the default language and add values to the custom fields.
  2. Publish the post.
Creating a new post and adding values to the custom fields that you created
  1. In the Language section, click the plus icon. You will be taken to the Advanced Translation Editor page. The post content along with the values of the custom field that are set to Translate are available for translation.
Clicking the plus icon to start translating the post
  1. Click the Translate automatically button to add the machine translations. Review the translations and make sure they’re accurate.
  2. Click Complete to publish the translations.
Translating the content automatically

To learn how to send the content to be translated by others, visit our page about translating your WordPress site.

For the choice fields such as the Select and Radio Button fields, please note that if you navigate to the secondary language editing page you will see the choices untranslated showing the default language texts although you have translated them. This is not a bug and it doesn’t affect the functionality as the translated texts are stored correctly in the database. Accordingly, the correct values will be displayed on the front-end.

Translating Options Page Custom Fields

The ACF Options Pages provide a set of functions to add extra admin pages to edit ACF fields. Check out ACF’s documentation on creating Options Pages.

To create an Options Page custom field group and translate its fields, follow the steps below:

  1. Create a custom field group for the desired Options Page.
Creating the Options Page custom field group
  1. Set the custom field(s) translation preference to Translate. Also, set the location to match the Options Page. Once done, Publish the field group.
Setting the custom fields translation preference
  1. Navigate to the Options Page and add a value to the default language custom field then click the Update button.
Add a value to the custom field
Adding a value to the custom field
  1. Use the admin bar language switcher to choose the language you want to translate your field text into.
Use the language switcher to choose the language
Use the language switcher to choose the language
  1. Fill in the translated text then click the Update button.
Add the translated text and update the page
Adding the translated text and updating the page

Translating ACF Blocks

The ACF block content can be translated as any other default WordPress Gutenberg block. For more information on how to create and use ACF Blocks, check out this post.

In our example, we have created a simple Testimonial block with ACF. Let’s see how to set the block’s ACF field translation preference and translate the block’s content using WPML’s Translation Editor.

  1. Create the block field group by navigating to Custom Fields → Add New.
  2. Fill in the field group name and add the custom fields.
  3. When creating the custom fields, make sure that you set the appropriate Translation preferences.
  4. In the Location box, set the field group to show when the Block is equal to Testimonial. Once done, don’t forget to Publish.
Creating the block’s custom field group
  1. Let’s insert the ACF block that we created into a post. Navigate to Posts Add New and fill in the post title. Click the plus icon in the content editor and choose the Testimonial block.
Creating a new post and inserting the Testimonial block
  1. Fill in the block content and Publish the post.
Filling in the Block’s content
  1. In the Language box, click the plus icon corresponding to the language you want to translate your post into. You will be taken to the WPML Translation Editor. There, fill in the translated content and publish the translation.
Starting the post translation

This is how the translated page that includes the Testimonial block looks on the front-end:

Translated block on the front-end

Translating ACF User Interface

Besides being able to translate the values of ACF fields that are shown on the front-end, WPML allows you to also translate the ACF user interface. This means that when translators are translating posts and pages that feature ACF fields, the labels and options for those fields will appear in that specific language. This can help to make the translator’s work easier and more convenient.

If you only need to translate field values and display them on the front-end, you don’t need to perform the following steps. You should only need to translate Field Groups in certain cases. For example, if on the front-end, you want to display different field labels for different languages.

Setting Field Groups as translatable may result in some unexpected issues if you have a fairly complex site.

Translating Field Groups

To translate the Field Group, follow the steps below:

  1. Set the Field Groups (acf-field-group) post type to be translatable by navigating to WPML → Settings and scroll to the Post Types Translation section.
Setting the Field Groups (acf-field-group) post type to be translatable
  1. To translate the Field Group, navigate to Custom Fields → Field Groups and click on the Edit link of the field group you want to translate.
Editing the page of the field group
  1. In the Language meta-box, make sure that the Use WPML’s Translation Editor option is turned off. Then, select the Duplicate checkbox for the different languages you want to translate your field group into and click the Duplicate button.
Duplicating the field group
  1. Click on the pencil icon to edit the text in the fields for different languages.
Editing the field group translation
  1. Now, you can edit the text in this group, for the other language(s). To keep your field groups consistent for all the languages of the site, you should only edit the label and descriptions of the fields and not add new fields or change their Field Name values. If you do make any changes like this to the fields, you should do so for all your site’s languages. Once you complete adding the translated texts to the field group, click the Update button to save the changes.
Translating the custom field texts
  1. If you navigate to the secondary language post editing page you will see the field labels translated.
Translated field labels

Translating Other Parts of the Interface

So far, we’ve covered translating the field groups and fields. Like any other WordPress plugin, ACF has its own user interface which includes text. To have a fully localized WordPress admin, you can also translate the ACF’s interface.

Also like many other WordPress plugins, ACF comes with its own translations. Before you translate ACF’s interface, check with the author to see if the translation in your language is already available.

To translate ACF’s interface, follow the steps below:

  1. Go to the WPML → Theme and plugins localization page.
  2. Under the Strings in the plugins section, you will see a list of plugins installed on your website. Select the Advanced Custom Fields plugin and click the Scan the selected plugins for strings button. WPML will scan ACF’s code and locate all translatable strings.
Scanning the ACF plugin for translatable strings
  1. After the scan is complete, navigate to WPML → String Translation page and choose the “acf” text domain from the “Select strings within domain:” drop-down menu then click the Search button. This loads all the ACF strings that are available for translation.
  2. To translate a string, click on the translations link, add your translated content, tick the Translation is complete check-box, then Save.
Translating ACF strings
  1. When you are done, the ACF’s user interface will appear fully localized.
Localized version of the ACF interface

How to Handle Images and Other Post Object Fields

If you constructed a Field Group with a field pointing to an existing post or custom post type (including images and other kinds of attachments), make sure that the post or post attachments are translated before you start adding them to the ACF field group.

For example, let’s assume you have added a Gallery field to the field group. You are going to add some photos to this gallery under your post.

Before translating your post along with its gallery field, make sure every image in the gallery is translated. Even though you want to have the same images in the translated post, you should go to the WPML → Media page and make sure that all the images included in the gallery are translated.

Making sure that the images included in the gallery are translated

Without translating post objects such as images, posts and other kinds of post types, you will experience some minor problems, though your site will be working. Translated posts will be associated with objects in the original language, which is allowed. On the front-end, posts will display correct relations, however, on the post edit screen, you will see these fields as empty.

Frequently Asked Questions

  • Untranslated post object and page link fields do not show on the backend of the duplicated post despite the fact that the post is associated with the correct value for the post object and page link custom fields in the database.
    Please note that this is not a bug and it does not affect the functionality. Read more about this scenario on our dedicated FAQ page.
  • Is it possible to hide ACFML field annotations?
    Yes. To each translated field, ACFML adds information about the value in the original language. If you want to remove that information you can add the following line to your site’s wp-config.php file:
define( 'ACFML_HIDE_FIELD_ANNOTATIONS', true );

This feature is supported in ACFML since the 1.1 version.

Known Issues

WPML works fine with this plugin, but sometimes there could be minor issues we're working on. This is expected as both plugins provide frequent updates.

Current issues:

Getting Help

If you need help using WPML with Advanced Custom Fields, please head over to our technical forum.

Creating Multilingual Forms Using Ninja Forms and WPML »

Ninja Forms is an intuitive drag-and-drop form builder for WordPress. Learn how to use WPML to create multilingual forms using Ninja Forms.

Form in the default language

Translated form

On This Page

Getting Started

Start by installing and activating the following:

If you’re new to WPML, check out our Getting Started Guide. It quickly walks you through all the translation options you can use.

One of these options is Translate Everything – the quickest way to translate and the easiest way to keep your content up to date. This feature automatically translates pages, posts, custom post types, custom fields, taxonomies, WooCommerce products, and more as you add and edit content.

Using Translate Everything with Ninja Forms will speed up the workflow of translating your forms.

Creating and Translating Your Forms

These are the main steps to follow for translating your forms:

  1. Create the form in the default language.
  2. Translate the form.
  3. Insert a Ninja Forms block into a post, page, or widget and select the form you want to use from the dropdown.
  4. Translate the post, page, or widget that holds the form.

Creating the Default Language Form

To create the default language form, go to Ninja FormsAdd New. In this example, we will use the “Contact Us” form template. Of course, you can use a blank template and build your form from scratch.

Creating the default language form

Translating the Form

To translate your form go to the WPMLTranslation Management page and follow these steps:

  1. In the Select items for translation section, select Ninja Forms from the Element type drop-down menu then click the Filter button.
  2. Use the checkboxes to select the forms that you want to translate.
  3. In the Select translation options section, choose the Translate option corresponding to the language(s) you want to translate your forms into.
  4. Click the Translate selected content button. If you’re not the only translator in the site, this button is called Add selected content to translation basket. In this case, after clicking it, go to the Translation Basket tab, select the translator and send the basket for translation.
Sending the form for translation
  1. Now, go to WPML → Translations and click the Translate button for the job related to your Ninja form. If you’re not the only translator in the site, this button is called Take and translate.
Starting the Ninja form translation

You’re taken to the Advanced Translation Editor where you can translate your form. You can use the built-in automatic translation for quick and easy translation.

For the time being, you can’t set your secondary language forms to have a different date format for the date field nor a different currency.

Inserting the Form Into the Content

After creating and translating your form it is time to add it to a page, post, or widget. In our example, we created a new page in English and used the Ninja Forms block to add our form.

Inserting your form to the default language page

Translating Content With Embedded Forms

Finally, translate the page, post, or widget that includes your form. You can do this by clicking the plus icon corresponding to the language you want to translate your page into in the Language box.

Translating the page that holds the form

Updating Form Translations

If you change the form in the default language you need to update its translations as well.

To update the translation of a form, follow these steps:

  1. Navigate to WPML → Translations.
  2. Translation status shows that the form translation needs updating. Click the Edit button in the form’s row.
Updating the translation for the Ninja form that was changed in the default language

Known Issues

WPML works fine with this plugin, but sometimes there could be minor issues we're working on. This is expected as both plugins provide frequent updates.

Current issues:

Getting Help From Our Support

We have supporters in our forum who are ready six days a week to help you. They are trained in how to use WPML with Ninja Forms.

If you are setting up the site and WPML yourself, please use our Technical support forum.

How to Use bbPress on Multilingual Sites with WPML »

bbPress is a WordPress plugin that turns your site into a forum-driven system. With WPML, you can make your forum system multilingual.

You probably already know at least one multilingual bbPress forum system – the WPML support forum. Our sites run WPML and bbPress together to allow our clients to search for answers and seek support in their native language.

WPML’s multilingual support forum is built using bbPress
WPML’s multilingual support forum is built using bbPress

In the following document, we’ll walk through how to create a multilingual WordPress forum system using bbPress just like ours.

What you need

  • The bbPress plugin (version 2.5.12 or above)
  • Multilingual CMS version of WPML. Install the WPML core plugin plus String Translation, Translation Management, and Media translation add-ons.

Essential resources

  • WPML’s Getting Started Guide helps you in setting up WPML in a few minutes. You will want to refer later to some of its subtopics, such as String Translation. We recommend that you keep this guide open while following this tutorial.
  • The bbPress documentation will provide you with all the information you need to create and manage your forum.

WPML translation tools

WPML offers two translation editors you can use for translating your site’s content:

Besides translating your site content yourself, you can also:

Content

There are two scenarios when you are creating a multilingual forum system:

  1. One forum per language – This is the most likely scenario.  We will have one independent forum for each language, which means we translate only the forums post types. This is how we run WPML support forums.
  2. Translating everything – In some cases, and usually if you are using bbPress not for its strictly original purpose, you might want to translate everything (forums, topics, replies).

One forum per language

In this case, we just need to have one support forum in each language, independent from one another. In other words, we don’t want to translate all the contents of the forums to the different languages.

In the following example, I have set my site’s default language as English and the secondary languages as German, French, and Polish. Let me show you step-by-step how this is done:

Set Up

  1. Go to WPMLSettings page. Scroll down to the Post Type Translations section, and set the Forums custom post type to one of the Translatable options. Click Save.
Marking the Forums custom post type as Translatable
Marking the Forums custom post type as Translatable
  1. Add a New Forum in your default language and Publish it.
Creating a new forum in English, our default language
Creating a new forum in English, our default language
  1. To translate the forum yourself, click the plus icon in the Languages meta box.
Click the plus icon to translate the forum text yourself
Click the plus icon to translate the forum text yourself

This opens the Advanced Translation Editor where you can add your translations.

Translating the forum text in the Advanced Translation Editor
Translating the forum text in the Advanced Translation Editor
  1. To send your forum to be translated by a local translator, professional translation service, or translate multiple forums in bulk, start by going to WPMLTranslation Management. Select Forum from the dropdown menu, and add your selected forums to the Translation Basket.
Adding forums to the Translation Basket to be translated by professional translation services, local translators, or translate in bulk
Adding forums to the Translation Basket to be translated by professional translation services, local translators, or translate in bulk

You can see all of the different forums in each language by clicking on the Forums menu link, then selecting All languages.

Viewing all forums after translation
Viewing all forums after translation

Adding the correct forum to the WordPress navigation

Next, we’ll walk through adding your forums to the WordPress navigation menu, and how to have each forum appear in the right language.

  1. Go to Appearance Menus.
  2. Click on Screen Options in the upper right corner to show the WordPress screen options settings.
  3. Mark Forums in the Boxes row.
Adding Forums to the screen options
Adding Forums to the screen options
  1. Add the default language forum to the menu and click Save Menu.
Adding the forum to the menu
Adding the forum to the menu
  1. Click the Synchronize menus between languages link. WPML shows you which items will be added or updated in your secondary language menus. Click Sync and Apply Changes to update them.
Adding the translated forums to your secondary language menus
Adding the translated forums to your secondary language menus

Translating bbPress texts (strings)

bbPress comes with its own translations, included in the bbPress MO file. This means that after you have followed the above steps you already have most of the default bbPress strings translated to your site’s secondary languages, as you can see below:

Translations from bbPress’s included MO file
Translations from bbPress’s included MO file

If you would like to change any of the string text, you will need to update the translations by following these steps:

  1. Go to WPMLTheme and Plugins localization. Select bbPress from the Strings in the plugins section, and click the Scan the selected plugins for strings button. WPML will scan all the translated strings that come with bbPress.
Scanning bbPress for strings
Scanning bbPress for strings
  1. Go to WPMLString Translation.
  2. Paste the string you’d like to translate in the search field and click Search.
  3. Add your translated text, mark the Translation is complete option and click Save.
Updating the translation of a string
Updating the translation of a string

You can see the translated strings on the site’s front-end.

Viewing the updated string
Viewing the updated string

When people enter one of your support forums it can be very helpful to show them a list of all the forums available in the other languages–we do that in our forums.

To achieve that you will need to add a small piece of code to your theme’s functions.php file, using the bbPress API library. The action we are using is bbp_template_before_single_forum. You can see an example of how to use it here.

Then, we inject the WPML language selector action called wpml_add_language_selector.

Below you can see the complete snippet:

Finally, you can customize how the language selector looks by going to WPML Languages and adjusting the settings in the Custom Language Switchers section.

Customizing the language switcher settings
Customizing the language switcher settings

Translating everything

Although this isn’t the most common scenario, some clients have asked us if it’s possible to translate everything coming from bbPress (topics and replies included). So we wrote a small bridge plugin that you can get from our github repository.

After installing and activating the plugin, set the Forums, Topics, and Replies custom post types to Translatable. You can do this by navigating to WPMLSettings. Scroll down to the Post Types Translation section and select one of the translatable options.

Setting the bbPress custom post types as translatable
Setting the bbPress custom post types as translatable

Once these post types are translatable, you can translate them the same way as explained with the Forum post type earlier in this article.
As always, if you have any issues or questions, head to our support forum and let us help you resolve them.

Known Issues

There are no known compatibility issues between this plugin and WPML.

Creating Multilingual Forms Using WPForms and WPML »

WPForms is a plugin for adding contact forms to your WordPress site. In this guide, you can learn how to make your WPForms multilingual using WPML.

Form in the default language

Form translated to secondary language

On This Page

Getting Started

Start by installing and activating the following plugins:

If you’re new to WPML, check out our Getting Started Guide. It quickly walks you through different translation options you can use.

Translating Your Forms

To translate your form, follow these steps:

  1. Go to the WPMLTranslation Management page.
  2. In the Select items for translation section, select WPForms from the first drop-down menu and then click the Filter button.
  3. Select the form that you want to translate.
  4. In the Select translation options section, choose the Translate option corresponding to the language(s) you want to translate your forms into.
  5. Click the Translate selected content button. If you’re not the only translator in the site, this button is called Add selected content to translation basket. In this case, after clicking it, go to the Translation Basket tab, select the translator, and send the basket for translation.
Selecting the content for translation

Now, go to WPMLTranslations and click the Translate button for the job related to your form.

Starting the translation of a form

You’re taken to the Advanced Translation Editor where you can translate your form. You can use the built-in automatic translation for quick and easy translation.

Translating a form using WPML’s Advanced Translation Editor

That’s it, your form is now translated and you can use it in posts and pages.

If the form ever changes in the default language, use these same steps to update its translations.

Translating Other Form Texts

We translated the main form texts but there are some that might not be translated. This includes sub-label texts like “First” and “Last” ones for the name field.

As above, if you have Translate Everything turned on, these texts will already be translated.

If you’re not using Translate Everything, follow these steps:

  1. Navigate to WPMLString Translation and search for the sub-label text that you want to translate.
  2. Click on the plus symbol in the row you want to translate and add your translation.
Translating sub-label texts from the String Translation screen

Using Translated Forms In Pages

After creating and translating your form you can insert it into any page using the WPForms block. Then, simply make sure to translate that page as well.

As users visit the page in the secondary language, WPML will automatically display the form in the correct language.

Known Issues

WPML works fine with this plugin, but sometimes there could be minor issues we're working on. This is expected as both plugins provide frequent updates.

Current issues:

Getting Help From Our Support

We have supporters in our forum who are ready six days a week to help you. They are trained in how to use WPML with WPForms.

If you are setting up the site and WPML yourself, please use our Technical support forum.

WooCommerce Multilingual - Multilingual WooCommerce Sites Made Easy »

WooCommerce Multilingual makes it easy to run multilingual e-commerce sites with WooCommerce and WPML. The plugin streamlines the translation process, so that you only need to translate the texts. Translations for products, categories and variations are created automatically for you.

Continue reading

Gravity Forms Multilingual »

WPML lets you translate the texts that appear in your Gravity Forms to other languages on your site. Once translated, the form displays in the correct language on the front-end automatically.

Form in the default language

Form translated to secondary language

On This Page

Getting Started

Start by installing and activating the following plugins:

If you’re new to WPML, check out our Getting Started Guide. It quickly walks you through different translation options you can use.

Before translating your forms, make sure that the No-Conflict Mode setting is turned off on the Forms Settings page. When this option is enabled you cannot translate the form using the language switcher in the top admin bar.

Turning off Gravity Forms “No Conflict Mode”

Translating Gravity Forms

Edit the form you want to translate and hover over the language switcher. Here, you can specify which language the form should be in, and you can send the form for translation into another language.

Sending the form for translation from the language switcher


Clicking Send to translation opens Translation Management and filters the available content to show only Gravity Forms.

You can also access this list by going to WPMLTranslation Management and selecting Gravity Form from the dropdown menu.

Viewing the filtered list of Gravity Forms on the Translation Dashboard

To send the form for translation:

  1. Select the form that you want to translate.
  2. Choose the Translation options corresponding to the languages you want to translate your form into.
  3. Click Translate selected content. If you’re not the only translator in the site, this button is called Add selected content to translation basket. In this case, after clicking it, go to the Translation Basket tab, select the translator and send the basket for translation.
Sending the form for translation

Now, go to WPMLTranslations and click the Translate button for the job related to your form.

Starting the translation of a form

You’re taken to the Advanced Translation Editor where you can translate your form. You can use the built-in automatic translation for quick and easy translation.

Translating a Gravity form using WPML’s Advanced Translation Editor

That’s it, your form is now translated and you can use it in posts and pages.

Using Translated Forms In Pages

Once the form is translated all you need to do is insert it into any page using the Gravity Forms block.

Then, simply make sure to translate that page as well.

As users visit the page in the secondary language, WPML will automatically display the form in the correct language.

Updating Form Translations

If you update the default language form by adding, deleting, or updating any of the content, you will need to update the translated versions.

Certain types of fields in Gravity Forms include multiple choices that users select, like Drop Downs and Radio Buttons. Changing the position of options in multiple-choice fields that have already been translated may result in those fields losing their translations. In this case, you need to translate these fields again.

Amending a Gravity Form that will need a translation update

To update the translation of a form or translate new content that you added to the form, follow these steps:

  1. Navigate to WPMLTranslations.
  2. The spinning arrows icon indicates that the translation needs to be updated. Click on the Edit button to update the translation.
Updating a form’s translation
  1. In the Advanced Translation Editor, translate the new field(s), and click Complete to update the translation.
Translating the new field content

Content Submitted into Translated Forms

Please note that the Gravity Forms plugin does not detect a language of contents submitted in a form. When you submit content into a translated form, that content will still be created in the default language.

You can use Gravity Forms hooks and filters to write your own application logic and set the language of the submitted content after Gravity Forms creates it.

Deleting Form Translations

To delete a form’s translations, go to WPMLPackages and choose Gravity Forms from the dropdown menu. Select and delete the package that matches the name of the relevant form.

Deleting form translations


If you want to translate the form again later and don’t see it in WPMLTranslation Management, simply re-save the form.

Known Issues

There are no known compatibility issues between this plugin and WPML.

Getting Help

In case you need help translating your site built using Gravity Forms and WPML, visit WPML’s support forum.

BuddyPress Multilingual »

BuddyPress allows you to turn your WordPress website into a social network. WPML and its BuddyPress Multilingual add-on allow BuddyPress sites to run multilingual.

The main feature of this plugin is to allow you and, very importantly, the visitors of your BuddyPress site to have a consistent language experience. The plugin makes all pages display in the required language.

BuddyPress Multilingual Home Spanish
An example of a BuddyPress Multilingual homepage in Spanish

On This Page

Getting Started

Start by installing and activating the following plugins:

Note: for BuddyPress Multilingual to work, make sure to turn The Different languages in directories option found in the Language URL Format section of the WPML Languages page.

If you’re new to WPML, check out our Getting Started Guide. It quickly walks you through different translation options you can use.

Translating BuddyPress Pages

When you install and activate BuddyPress you’ll have a set of pages created automatically. You can easily translate these pages with WPML. You can let WPML translate pages automatically, send them to be translated by others, or do the translation yourself.

BuddyPress Pages Translated
A backend list of translated default BuddyPress pages

Translating Other BuddyPress Texts

Like many other plugins and themes some texts, or strings as we call them, are not part of Pages, Posts, or Taxonomy. All the strings coming from the BuddyPress plugin can be translated using WPML String Translation.

After installing and activating BuddyPress, go to the WPML → Theme and Plugins Localization page and click to scan your theme for strings. Then, in the plugins section, select BuddyPress and click to scan selected plugins for strings.

Now, you can go to WPML → String Translation and find, translate and save the desired strings. If you are new to using the WPML String Translation module please follow our String Translation tutorial.

BuddyPress Strings Translated
An example of translated BuddyPress Strings

Translating Profile Fields

BuddyPress allows you to add profile fields to your social network members. Using WPML, you can translate these fields.

After creating the fields in your default language, click the Register fields button in the notice that appears on the Profile Fields page.

Registering fields for translation

Now, go to the WPML → String Translation page, look for those field names and values and translate them.

Here’s an example of a profile field when translating it on the String Translation page.

An example of a profile field on the String Translation page

Known Issues

There are no known compatibility issues between this plugin and WPML.

Getting Support

In case you need help translating your site built using BuddyPress and WPML, visit WPML’s support forum.

Import Multilingual Websites Using WP All Import and WPML »