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.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | - | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 |
- | - | - | - | - | - | - |
Supporter timezone: America/Lima (GMT-05:00)
Tagged: Documentation request
This topic contains 14 replies, has 0 voices.
Last updated by vitaliiO 1 hour, 5 minutes ago.
Assisted by: Andreas W..
Author | Posts |
---|---|
February 6, 2025 at 3:38 pm #16676286 | |
vitaliiO |
Background of the issue: Symptoms: For example, in the content, there is a link to the page "hidden link", and we have a French version of this page: "hidden link". However, the translation in the advanced editor kept the original version ("hidden link") instead of changing the link to "hidden link". You can see it on screenshot. Questions: |
February 6, 2025 at 4:12 pm #16676446 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Hello, WPML can handle internal links for default WordPress content and some default WordPress Blocks or some widgets of popular page builders. Such internal links will usually not appear on the translation editor but we are currently having known issues with translating internal links inside buttons, calls to actions, and other similar blocks. Our developers are working on a solution for these issues. The Color Box Link, seems to be a custom Block or Page Builder Widget. May I ask which plugin is responsible for this element? For now: If a link is not being handled as an internal link which is why it is appearing on the WPML Translation Editor. You will for now need to adjust this link manually. Guide: Best regards |
February 6, 2025 at 6:54 pm #16676912 | |
vitaliiO |
The Color Box Link is created using Advanced Custom Fields (ACF). |
February 6, 2025 at 7:09 pm #16676955 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
The Flexible Content field should be set to "Copy". Is this the case? |
February 6, 2025 at 8:03 pm #16677054 | |
vitaliiO |
Let's try creating a "copy": 1. In the ACF settings, I set the **link** field to "copy." |
February 6, 2025 at 8:23 pm #16677213 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
The Flexible Content field needs to be set to "Copy". Can you please confirm? For the link to show up inside the translation editor, you need to set the link field to "Translate". All other fields should follow this guide, buy using the suggested field settings for the column "Same fields across languages": |
February 6, 2025 at 8:32 pm #16677257 | |
vitaliiO |
yes, flexible content field is copy |
February 6, 2025 at 8:44 pm #16677286 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
After making changes to the field settings you need to make a minor edit to the original page/post's link field and save the page/post again to generate a new translation job. If you still do not see the link on the Advanced Translation Editor, please try using the search field on top and type "http". If this does not work out, please let me know. |
February 6, 2025 at 8:51 pm #16677290 | |
vitaliiO |
Now i see link in translation advanced editor. |
February 6, 2025 at 8:57 pm #16677315 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
You need to translate the link yourself in this case. The automatic translation can not create such translations. |
February 6, 2025 at 9:00 pm #16677316 | |
vitaliiO |
Did I understand correctly that automatic translation cannot translate links to pages/posts, even if they have the corresponding language version? |
February 6, 2025 at 9:38 pm #16677411 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Correct, the translation engine (Google, Microsoft, Deep L) does not know anything about your website and will not know how to handle the URL. This is why this field by default is set to "Copy", and will not appear on the WPML Translation Editor. In this case, it should automatically use the translated URL if you are handling an internal link and the page that you are linking to is translated and published. |
February 6, 2025 at 9:50 pm #16677419 | |
vitaliiO |
I don’t quite understand. You said, **"it should automatically use the translated URL if you are handling an internal link and the page that you are linking to is translated and published."** However, in my case, it does not automatically use the translated URL. Even if I set the link field to **"Copy"**, it still points to the main language instead of the translated version. Even though the link points to an internal page that is translated and published, link still points to the main language. Why does this happen? |
February 6, 2025 at 10:05 pm #16677430 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
We do have a known issue in regards to ACF Blocks with Links but there should not be an issue with normal link fields. This might be because the link was already translated and a translation is saved in the translation memory of the translation editor. Could you please give this a test on a new page or post using a link that has not been translated earlier? 1) Set the link field to "Copy". 2) Create a post and translate it. 3) Create a second post, add a link to the first post, and translate the post. Does the issue persist? |
February 6, 2025 at 10:17 pm #16677437 | |
vitaliiO |
I've created 2 new pages: test-page-1 and test-page-2. Did all the steps and the link still points to main language. |