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 2 replies, has 1 voice.
Last updated by Andreas W. 3 days, 13 hours ago.
Author | Posts |
---|---|
February 12, 2025 at 2:02 pm #16697086 | |
leonv-20 |
Background of the issue: I only want to add two links in the global footer because I added two pages. I did it on the EN global footer, because this is the site's default language. Now I need to translate the WHOLE footer to NL because I cannot use the Divi builder on the NL footer template. WPML translates ALL links wrong. It puts the EN urls in the translation. Now I need to update all links of the footer. All links are double, because I have seperated sections for the mobile and desktop design. This takes me so long and it is very unnecessary to do it like this. I only want to edit the two anchor text, it should be like that. There is also a problem with a new URL which I cannot save in the translations and it jumps all the time back to that translation. It takes so much time every time I want to add a link to the footer, this is non sense. Symptoms: Questions: |
February 12, 2025 at 2:39 pm #16697266 | |
leonv-20 |
I edit the translations manually and saved it to the glossery for future translations. Hope this works. Furthermore, the Body template of hidden link is not copied to hidden link and hidden link is not copied to hidden link I translated both pages. Why I don't see the right templates? They are also not in the NL Divi Theme Builder. The names of the Body templates are also weird. I copied the Indonesia pages to make the new ones for Bucket list and Maldives, they are names now as Indonesia while I updated the names in the Divi Builder. |
February 15, 2025 at 4:55 pm #16709405 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Hello, This behavior is expected if you use a text content module. If you would use a module that offers dynamic links you could avoid this issue. See: Source: Best regards |