Title: WPML compatibility Last modified: November 22, 2017 --- # WPML compatibility * Resolved [paulovsky](https://wordpress.org/support/users/paulovsky/) * (@paulovsky) * [8 years, 8 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/) * I am using the Divi theme and WPML’s [translation editor](https://wpml.org/documentation/theme-compatibility/divi-builder/) but for some reason, the strings that should show the SEO data on each page are not registering with WPML. Is there something that I am missing? Viewing 6 replies - 1 through 6 (of 6 total) * [Pierre LeBaux](https://wordpress.org/support/users/lebaux/) * (@lebaux) * [8 years, 8 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/#post-9709909) * Hi [@paulovsky](https://wordpress.org/support/users/paulovsky/), hope you are doing well 🙂 since you are using proprietary theme and proprietary plugin, I would humbly recommend reaching out for support in their forums first. I’m not trying to push you away — it is just very hard to deal with problems that are behind paywall. You pay for their proprietary code, so I think it is reasonable to ask them to ensure compatibility. Now [@cybr](https://wordpress.org/support/users/cybr/) is usually more than happy to tweak TSF so it works 100% with both DIVI and WPML, but it is always better if they reach out first, not the other way around, simply because TSF code is openly available. I hope you understand. * That being said, was this problem present in TSF 2.9.4? Or it was introduced with version 3? Are you using the latest versions of both DIVI and WPML with all its plugins? Thanks for clarification! * Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/) * (@cybr) * [8 years, 8 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/#post-9711046) * Hi [@paulovsky](https://wordpress.org/support/users/paulovsky/), * I’m not sure which strings you’re referring to. * If this issue is regarding the home page, then it can be solved within WPML, see: [https://wpml.org/forums/topic/translating-title-with-the-seo-framework-plugin/#post-1397843](https://wpml.org/forums/topic/translating-title-with-the-seo-framework-plugin/#post-1397843) * I’d love to get feedback! Cheers 🙂 * Thread Starter [paulovsky](https://wordpress.org/support/users/paulovsky/) * (@paulovsky) * [8 years, 8 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/#post-9755427) * Hello and thank you for your help! * This might be a bit tricky to explain but I will try my best. * SEO Framework is compatible with WPML, that is certain, but only when it comes to the normal usage of the wordpress editor. However, WPML has a different UI for translations, called the [Translation Editor](https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/). This is useful to avoid having to redesign the page for each language, as it only shows the text strings. * The problem is that the SEO’s custom fields do not register in this interface and it causes a workflow headache. I need to send a separate file with the SEO fields to my translators, they will send it back to me and then I will open and edit each page after it has been translated. * Apparently your plugin has to output the custom fields in a way that WPML can see them, as seen [here](https://wpml.org/documentation/support/language-configuration-files/#custom-fields). * Following WPML’s instructions, please provide a wpml-config.xml that is compatible with their guidelines for the Translation Editor. - This reply was modified 8 years, 8 months ago by [paulovsky](https://wordpress.org/support/users/paulovsky/). - This reply was modified 8 years, 8 months ago by [paulovsky](https://wordpress.org/support/users/paulovsky/). * Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/) * (@cybr) * [8 years, 8 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/#post-9757286) * Hi [@paulovsky](https://wordpress.org/support/users/paulovsky/), * I’ve moved this to GitHub, describing the issue and your plausible solution: [https://github.com/sybrew/the-seo-framework/issues/229](https://github.com/sybrew/the-seo-framework/issues/229) * Feel free to add comments there. I might have left some important (workflow) details out as I don’t use WPML myself. * Cheers! * Thread Starter [paulovsky](https://wordpress.org/support/users/paulovsky/) * (@paulovsky) * [8 years, 8 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/#post-9758347) * Awesome! thank you! * Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/) * (@cybr) * [8 years, 6 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/#post-9927222) * Hi [@paulovsky](https://wordpress.org/support/users/paulovsky/), * Vuk from WPML.org left a comment on how to resolve this through the UI: [https://github.com/sybrew/the-seo-framework/issues/229#issuecomment-362259721](https://github.com/sybrew/the-seo-framework/issues/229#issuecomment-362259721) * I’m looking further into this to see if it’s possible to make this work by default for the v3.1 release. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘WPML compatibility’ is closed to new replies. * ![](https://ps.w.org/autodescription/assets/icon.svg?rev=3000376) * [The SEO Framework – Fast, Automated, Effortless.](https://wordpress.org/plugins/autodescription/) * [Frequently Asked Questions](https://wordpress.org/plugins/autodescription/#faq) * [Support Threads](https://wordpress.org/support/plugin/autodescription/) * [Active Topics](https://wordpress.org/support/plugin/autodescription/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/autodescription/unresolved/) * [Reviews](https://wordpress.org/support/plugin/autodescription/reviews/) ## Tags * [SEO Framework](https://wordpress.org/support/topic-tag/seo-framework/) * 6 replies * 3 participants * Last reply from: [Sybre Waaijer](https://wordpress.org/support/users/cybr/) * Last activity: [8 years, 6 months ago](https://wordpress.org/support/topic/wpml-compatibility-121/#post-9927222) * Status: resolved