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.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
wow, thanks for the great videos! I could easily follow the steps.
By the way it wasn't necessary to change the concert-id in the shortcode (e.g. 922 in your example)
It was enough to just change the shortcode to "Home-Single-Concert-EN" - the translation magically worked then.
A hopefull last question: How can i translate the view at the bottom of the homepage? There is a "WEITERLESEN"-Button again.
I already translated the view's template, but it did not work. What do i have to do, to make it work?
Let me consult our second tier team again about this. I tried to fix it myself, and as far as I can see, the Views also need to be manually translated. But I'll need to confirm it with them first.
I did this to the last View added in the homepage here: hidden link. This View is also coming from a content template I have created, which was also manually translated: hidden link
In this case, if we use manual translation for both the content template having the View and the View itself, then the button is correctly translated in the English version (we had to select the new copied View, which is carrying the English info).
Please stay tuned, and when I receive an update from our second tier/dev teams, I'll bring it to you.
Today we have released a bunch of Toolset updates, which includes a fix for better translations of Content Templates, Views, and WordPress Archives when using WPML. So, may I kindly ask you to try to update your Toolset plugins (WPML as well, since we also released new versions for it), and try again to do your Content Templates and Views translations?
After this, you can translate them as you were doing before this issue.
Please just make sure to have a complete backup before updating the components.
Looking forward to your reply and confirmation. Thank you.
That is right, now you should be able to translate as you were doing before, and therefore the Views can be translated inside the post/content they are inserted, and not manually.
I have made some tests, please check it: hidden link.
- First, I updated WPML to the latest versions
- Then, I made a minor edit in the original language of the problematic content templates, and updated the translations
- The same needs to be done in the homepage and every other post using the templates
After these actions the buttons were correctly translated.
Please give it a try in the original website and let us know how it goes. Thank you.
