Pro 6.8.0. Components still not translatable?

Beta
#1

Hi @charlie, Ii know you said that you are working with WPML on this, but it is unclear if Components are now translatable natively or not?

I did a test and created a translated Component inside /wp-admin/edit.php?post_type=cs_global_block.

That exposed translating the Components page title only, so I did that. With that, I got an option to change the language of the components page and to actually translate the content inside it. So I translated a headline that was exported as a Component.

Now I had that exported component in two languages, but on the front end, the text is not changing. Only the text from the primary language stays.

If components are still not translatable, that’s fine. TWIG function is a solid solution, but I would like to know more clearly what works with the new version today? Or we need to wait?

I had to translate one of the new websites and the project was prolonged for a few weeks due to absolutely horrible WPML issues. That is unsustainable, and I don’t have any safe procedure for the upcoming websites, which all need to be multilingua.

#2

Right now for the WPML translation editor we are working with them to get Layouts working first. I gave them a heads up on what needs to be done months ago, but now that this release is out I’m hoping we can get them to finish their portion. You’ll notice on both layouts and components only the title is translatable.

When we have layouts finished I’ll get them started on components. I know it’ll be slightly different on their end to do that, which is why I started them with layouts. There’s a small thing we’ll update on our end with components related to cache, and we should have translated components after that. At least we have a game plan for this issue now. You can reach out to them about this too.

1 Like