This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is unable to translate the Module Link URL of a Divi Blurb using the Advanced Translation Editor (ATE). The issue arises when using Divi's Dynamic URL feature, as the URL does not appear in the ATE. The client has tried adding custom XML configuration for the Divi Blurb shortcode and has made changes to the blurb to trigger WPML's translation detection, but without success.
Solution:
We have identified that dynamic URLs are encrypted and therefore not recognized by ATE as translatable URLs. To work around this issue, the client should use either absolute or relative URLs for the Module Link URL field. Here are the steps to configure the translation:
- For absolute paths, add the
<et_pb_blurb>
shortcode tag with the
link_option_url
attribute AND
link
type.
- For relative paths, add the
<et_pb_blurb>
shortcode tag with the
link_option_url
attribute and WITHOUT the
link
type.
This approach allows the URLs to be recognized and translated within the ATE. If you are experiencing this issue and the solution provided does not seem relevant, please open a new support ticket with us.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
This topic contains 3 replies, has 2 voices.
Last updated by 1 year, 4 months ago.
Assisted by: Osama Mersal.
 |
Tell us what you are trying to do? I am trying to use the ATE to translate the Module Link URL of a Divi Blurb. The Blurb Module Link URL does not appear in the ATE in order to translate. I've added the Divi Blurb shortcode with link url attribute to the custom XML. I've made small changes to the blurb in order to force WPML to notice translation changes, but it still does not show. I've also re-processed the links in WPML and cleared the WPML cache. The only unique thing about my situation is that I'm editing a Global Divi Blurb module instead of a blurb on a page. Is there any documentation that you are following? I followed the following documentation for registering custom XML / Shortcut for the Divi Blurb Module Link URL field. https://wpml.org/forums/topic/translate-divi-text-modules-link-url/ https://wpml.org/forums/topic/divi-blurb-title-link-url-not-translating/ hidden link Is there a similar example that we can see? Screenshots attached. I can set up a test site if needed. What is the link to your site? hidden link    |
 Supporter Languages: English (English ) Arabic (العربية ) Timezone: Africa/Cairo (GMT+02:00) |
|
|
|
Hi Osama, Thanks for the sandbox site. I recreated the scenario on there and was able to figure out the problem – I now have a workaround solution, but will explain my findings/understanding and remaining problem/quesiton. The issue had nothing to do with the Divi "global" module functionality, but actually with how the URL is specified in the Divi Module Link URL field. Attached is an image to explain. The Divi Blurb module has a Module Link URL field. What I found was that depending on how you enter a link/URL into this field, you'll need to configure the "et_pb_blurb" shortcode differently. For example: 1) Divi Dynamic Link – If you use the Divi Dynamic URL feature, I'm unable to have the link show up in the WPML ATE to translate it. Is there a way to translate the link this way with WPML? This is how I currently understand the WPML shortcode configuration and translation to work with the Divi Module Link URL field. Please let me know if this is correct and whether there is also a way to translate this URL when using the Divi Dynamic Link option. For now and going forward, I'll be entering the URLs manually (absolute or relative path). Thanks, Matt  |
|
Supporter Languages: English (English ) Arabic (العربية ) Timezone: Africa/Cairo (GMT+02:00) |
Hi Matt, Thanks for your update. You have found the workaround by using absolute or relative URLs because dynamic URLs are not working correctly with ATE. The dynamic URL is encrypted, so ATE can't see it as a URL. (Kindly check the attached screenshot) Best regards,  |
|
|
