WPML does not let me translate the strings i passed to component properties. Therefore, i always see the original language throughout the site.
Yes, you’re right, I can also confirm that components are not working with WPML. I have added this to our internal development log.
1 Like
@charaf is this solved with the release of 1.12 ?
Edit: Nope it is not fixed 
components still in experimental stage not released yet so its fine. lets wait.
Correct we haven’t tackled this yet. We’d like to get more feedback before committing to working on WPML compatibility for components since it requires a bit of effort and if there are breaking changes we’d have to do it all over again and it could break existing translations.
@charaf will this be tackled with 2.0? I found nothing in the changelog, but the components seem to leave the experimental phase.
2 Likes
@charaf any updates on making components translatable? Making everything in the CMS translatable is crucial as most of my clients nowadays need multilingual websites.
Hi @JUVO_Justin & @lbch,
Unfortunately, components integration with WPML hasn’t been tackled for 2.0. This should be next in line now that components are leaving the experimental stage.
2 Likes
I was not aware that components can’t be translated even with WPML strings. This is huge for us as well. 2 days before go live I guess the other languages will be seeing some English content then.
Any workarounds? I guess we can duplicate them, translate them and then change the French page with the corresponding component but that would break with each update of the original language page I am guessing.
@telmosilva, I replaced all components with regular elements and will not use components for future projects until multilingual support has been tackled. I think this is the best way, even for single-language websites: just in case you might need to make a website multilingual in the future.