Global Blocks and wpml

Hi Cendar,

I haven’t done specific testing myself, but a gentleman named Miroslav from the X users group has, and he confirmed it worked fine. He did mention there was an old way and a new way of translating, and he had to play with those before figuring it out. His final report was that is was a bug in WPML and he was able to solve it, but I didn’t hear back about the specific fix.

If you’re a member of the group, it may be worth pinging him. I’ll do the same and update you as soon as I can.

Cheers

Ok, I can’t find his post on the X user group, but I made some research and I think I understand what he means.

wpml has two “modes” to translate. The default one when we install wpml with x-theme is a mode where you create the page in default language, and when you want to translate to other languages, wpml provide us a UI with all the blocks to translate (but not the global blocks). In this mode, we don’t have the possibility to use cornerstone on other language pages.
—> This is the “new” way of translating, witch is faster than the “old” way, but not letting as many possibilities.

The other mode is to simply copy/paste all pages and to translate in the pages directly with cornerstone. In this mode, we can create several global blocks and choose which block is on which page.
—> This is the “old” way of translating.

So, if we want to use global blocks in multilanguage, I think for now the only way is to use the “old” way of translating.

For info and for anyone who read this, to change the translation mode, you must go to wpml—> translation management —> config of multilingual content tab —> and choose create translations manually instead of use translation editor.

Since you’re the plugin creator, maybe you can see with guys at wpml if they can find a way to “recognize” your global block in the translation editor. I think I saw on some posts on their site about that.

Anyway, thank you for your response and sorry for my bad english, I hope I’m understandable ??

Best regards

Ha! I think I found a workaround to use global blocks in the “new” way of translating!

I don’t know why I didn’t think of it before.

Instead of using the block “global block” in cornerstone, I will use a text block with the shortcodes of global blocks. Global block is not recognised by wpml with the translation editor, but text blocks are.

That way, I can create global blocks for my different languages, and just change the shortcode in the text blocks.

I will test this and update you if it works.

IT WORKS!

Thank you for your time Michael.

Hope this will help other users!

I appreciate the detailed replies! I’ll see what I can do in the future about automating it.