Views, Content Templates, WordPress Archives, and forms are basic Toolset elements that you use to build your custom site. They include texts and labels that you need to translate. WPML allows you to translate them just like any other post or a page.
With Toolset, you design your whole site using the WordPress Block Editor. This is why the translation of these Toolset elements is the same as for posts and pages.
Use the following steps to send Content Templates, WordPress Archives and Toolset forms for translation.
- Go to the WPML → Translation Management page.
- Use the search section at the top of the page to find the element you want to translate. If you cannot find a certain Toolset element, try re-saving it first and then search for it again on the Translation Management page.
- Select the element you want to send for translation.
- Select the languages you want to translate the Toolset element into.
- Click to Add selected content to translation basket.
- Finally, click the Translation Basket tab, select the translator you want to use and click to Send all items for translation.
If you want to translate the items yourself, simply go to the WPML → Translations page and click the Take and translate button next to the translation job you want to do.
You are taken to the Translation Editor and all texts from the element you are translating appear for translation.
To send a View for translation, simply send the page where you created the View. Translator that takes the job will have all the View texts available for translation.
Forms are translated just like other Toolset elements, as described above. However, if you install WPML after creating your Toolset forms, you must resave the forms for them to appear on the WPML Translation Management page.
Archives are also translated as described above. When selecting the type of content to search for on the WPML → Translation Management page, you will find them as WordPress Archives Block.
After you translate the WordPress Archive, you will notice that the title of the archive page on the front-end is not fully translated. Here’s an example of how a fully translated archive title looks like.
The first part, “Archives” is a word that is already translated in the WordPress’s own (core) translation files. If it’s not translated by default, go to the WPML → String Translation page and search for it. The one you need to translate is Archives: %s but make sure not to remove or change the %s part. If you cannot find this string, click on the Can’t find the strings you’re looking to translate box. It will expand and allow you to scan the WordPress core for text strings. After this, you will see this text string and it will probably be translated already.
The second part is actually the name of your custom post type. To translate it, go to the WPML → String Translation page and search for the plural name of the post type that this archive is for. It will be under the Types-CPT domain. Then, simply translate it to other languages and your archive’s title should be fully localized.