Skip Navigation

[Resolved] Translate Toolset button

This thread is resolved. Here is a description of the problem and solution.

Problem:

1) In the content template, setup a view block,

2) In the view block, display a button block

3) Translate the content template with WPML plugins, the button does not display translated text in front-end.

Solution:

It is a known issue, and have been escalated to our developers, I will update here if there is anything news.

Currently, you can setup the view block directly in page content(without content template), then translate the page, it should be able to avoid above issue.

Relevant Documentation:

This support ticket is created 3 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 4 replies, has 2 voices.

Last updated by Puntorosso 3 years, 8 months ago.

Assisted by: Luo Yang.

Author
Posts
#2015513

I was able to translate everything, except a Toolset button, contained on a Content Template.

hidden link

I see that it's correctly translated on the String Translation

hidden link

and on the normal translation page

hidden link

But in front-end it shows only the original language.

Any idea? Thanks

#2015591

Hello,

There do have one issue in this case:
1) In the content template, setup a view block,
2) In the view block, display a button block
3) Translate the content template with WPML plugins, the translated button text does not work in front-end.

Can you confirm if it is the same problem?

If it is not, please provide detail steps to reproduce the same problem, thanks

#2015661

Yes, exactly the same problem.
The only difference, in my case, is that the view block is contained on a page.

#2017913

Thanks for the confirmation, it is a known issue, and have been escalated to our developers, I will update here if there is anything news.

Currently, you can setup the view block directly in page content(without content template), then translate the page, it should be able to avoid above issue.

#2018497

Ok thanks.