[Resolved] wpml and toolset template and custom fields

[Author]

Posts

[katjaN]

How can I correctly assign the template and the custom fields created with Toolset with wpml and then translate them?

Do I have to use the string-translation or can I simply duplicate the page as with the other pages and designate it as EN and translate that? his is how I do it with the normal pages.

hidden link
kbh+2024!

Thanks!

[Nigel]

Hi there

I'm not sure I understand exactly what you are asking.

The link you shared is to a standard WordPress page. If you want to translate its contents you should just send the page to translation with WPML like any other page.

Please refer to these documentation pages about translating Toolset with WPML: https://toolset.com/related-lesson/translating-your-site/

Pay attention to this one in particular, for translating templates, Views, Forms, etc.: https://toolset.com/course-lesson/translating-views-content-templates-archives-and-forms/

If you are using the block editor rather than the legacy editor you should not normally need to use String Translation.

[katjaN]

I don't want to translate via a translator or a translation tool, I do it myself.
The page is a search page that I have created using a toolset and which leads to a template. When I want to translate the page, a message appears saying that I can't do it the way I normally do it. See screenshot above.

Thanks for the links, they certainly help, otherwise I'll get back to you. thanks!

[Waqar]

Hi,

Thanks for the update and glad that Nigel's message helped.

Let us know if you have any follow-up questions and for a new question or concern, you're welcome to start a new ticket.

regards,
Waqar

[katjaN]

Unfortunately, I can't get the translations of the toolset view, the toolset templates or the custom fields to work.

I have found some things via the Strings Translation, but somehow there are many fields that are already in English, although I have not translated them. Probably due to duplicating the template, I don't know.

My questions: I just want to translate the one template and the corresponding custom fields so that I have the fields in the English template: what is the smartest way to do this?
And how do I delete the duplicate fields, I don't know where they are?

[Waqar]

Thanks for writing back.

> My questions: I just want to translate the one template and the corresponding custom fields so that I have the fields in the English template: what is the smartest way to do this?

- Think of the translation of custom fields and the template's content, differently.

a). Custom fields:
WPML allows you multiple options for how the translation of custom fields can be handled, depending on the required scenario.

These settings and usage scenarios are explained here:
https://wpml.org/documentation/getting-started-guide/translating-custom-fields/

b). Content templates:
Just as we can manage the translation of the individual pages and posts, we can also manage the translations of the individual templates:
https://toolset.com/course-lesson/translating-views-content-templates-archives-and-forms/

Here is an example. Suppose, you have one page "Page A" that includes the content in the body directly, without any content template. You'll just translate the page, and its content will be translated, as part of the page.

And suppose, you have another page 'Page B', where the content is coming from the assigned content template. In this case, you'll also have to translate the content template, as explained in the documentation link shared above.

> And how do I delete the duplicate fields, I don't know where they are?

- If you're referring to the custom field option entries in the string translation section (shown in your screenshots), you can ignore them. As long as you've chosen the correct option for the custom field translations, these entries shouldn't cause any interference.