Before starting to translate your site, there are some initial steps that you need to take care of first.

Installing the necessary plugins

To translate sites built with Toolset, you need the Multilingual CMS version of the WPML plugin. It includes the main plugin and two additional ones that you need: WPML Translation Management and WPML String Translation. You can download all these plugins from your WPML Account’s download page.

After installing WPML, you will have to go through a short and simple set up process, which includes options for selecting the languages you need, the placement of the language switcher, and others. To learn more about this process, please visit the WPML language setup guide.

Setting up Translation Management

After configuring WPML, go to the WPML -> Translation Management page and follow the short wizard. The wizard helps you set up the translation workflow you prefer to use on the site. You can choose to translate yourself, send content to be translated by your local translators or have a translation service do the translation.

Finally, go to the WPML -> Settings page and in the How to translate posts and pages section find the New content subsection. There, select if you want to use the Advanced or Classic Translation Editor.

We suggest using the Advanced Translation Editor because of its advanced features and interface. It provides you with visual translation without editing HTML, automatic translation, glossary, spell checker, and more.

Making your custom types translatable

To be able to translate your Toolset site, you need to make all the relevant custom types translatable. This includes:

  • Custom post types
  • Custom fields
  • Custom taxonomies

Making custom post types translatable

Go to the WPML -> Settings page and scroll to the Post Types Translation section. You must make the following post types translatable:

  • Content Templates (view-template)
  • WordPress Archives Blocks (wpa-helper)
  • All the custom post types you created and you want to translate

Setting the custom post types to be translatable
Setting the custom post types to be translatable

Making custom fields translatable

On the WPML -> Settings page scroll to the Custom Fields Translation section. There, select the translation options you want to use for your custom fields. Custom fields you created with Toolset have the wpcf- prefix. For example, if you had a custom Image field called “Trainer Photo”, it would be listed here as “wpcf-trainer-photo”.

You can make your custom fields translatable or select their values to be copied over to translations.

Setting the custom fields to be translatable
Setting the custom fields to be translatable

Translating custom fields with static options

There are four types of custom fields that feature static options:

  • Checkbox
  • Checkboxes
  • Select
  • Radio fields

For example, a typical Radio field has at least two options users can select. You set the values (texts) of these options when setting up the Radio field.

To translate the options for these field types, go to the WPML -> String Translation page. Use the filter at the top of the page to find the texts. They will appear under the “plugin Types” domain.

Translating field options manually


Click the translation link for the string you want to edit. Translate the string, select that the translation is complete and save.

Sending field options for translation to other translators


Select the strings you want to send for translation. Below the list, select the languages you want to translate the texts into and click to add them to the translation basket. Go to the Translation Basket and send the strings for translation.

Making taxonomies translatable

On the WPML -> Settings page scroll to the Taxonomies Translation section. There, select the translation options you want to use for your custom taxonomies.

Setting the taxonomies to be translatable
Setting the taxonomies to be translatable

Translating slugs of custom post types

WPML allows you to translate the whole URL structure, including the slugs of your custom post types.

For example, a real estate site features a custom post type called “Houses”. The slug of a post type is its singular name or “house” in our example. This means that the URL structure for this post type will be the following:

  • www.example.com/house/

In the Spanish version of our site, we can translate this so that the URL structure for this post type viewed in Spanish will be:

  • www.example.com/es/casa/

After making your custom post type translatable (see previous section), you can translate its slug. To do this, follow the instructions provided on the WPML page about translating page slugs.

Translating custom post type slugs with WPML
Translating custom post type slugs with WPML

Need help?

Ask us about how to prepare your site to run multilingual and we’ll do our best to help.

For more elaborate questions, please use our Toolset Professional Support forum.