Skip Navigation

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 6 replies, has 1 voice.

Last updated by kevinB-5 1 week, 6 days ago.

Assisted by: Itamar.

Author Posts
May 23, 2025 at 1:16 pm #17066492

kevinB-5

Background of the issue:
I am trying to translate some ACF fields on my WordPress site using WPML. I expect to see an icon on the left and contact info on the right in the footer section, similar to the original language version: hidden link. I copied the exact value of the field to the translation.

Symptoms:
Instead of nicely translated values, I got a strange output on the translated page: hidden link.

Questions:
Why am I getting a strange output instead of the expected translation?
How can I ensure the ACF fields are translated correctly using WPML?

May 23, 2025 at 1:17 pm #17066494

kevinB-5

It is strange, because we use the same block in a page. And when we translate that, it works perfectly.

I used ACFML to tell WPML how to use the custom fields.

Maybe it is a conflict with 'clone' fields?

May 23, 2025 at 1:18 pm #17066495

kevinB-5

Dutch page: hidden link
German page: hidden link

Here it looks perfect.

Produkte-–-Luvego-05-23-2025_03_18_PM.png
May 23, 2025 at 1:41 pm #17066638

kevinB-5

Here are examples of what I should see, and what I'm seeing.

I'm going to remove the URL and the location for now on the translation, so that it looks nice. But ideally I would like to have them visible in the correct way.

Vacuümzakken-–-Luvego-05-23-2025_01_34_PM.png
Vakuumbeutel-–-Luvego-05-23-2025_01_34_PM.png
May 26, 2025 at 1:53 pm #17073647

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I don't see this problem on your site when I check now hidden link. It looks alright. Please see the attached screenshot. Have you managed to fix it already?

If not, please update our plugins to their latest versions and check if the problem persists. We have just released WPML 4.7.5.

Otherwise, please share access to your site and explain to me which field group is in charge of each field.

If you need further help with this, please share the access details to your site with me. I'm enabling a private message for the following reply.

Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/
**IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--

Regards,
Itamar.

2025-05-26_16-48-56.jpg
May 27, 2025 at 7:08 am #17075905

kevinB-5

I fixed it another way. Not via the term translation editor.

That would be preferable by the way, because now I have to manually translate all the texts. That wouldn't be the case with the translation editor.

So the issue is resolved for now, but I would like a solution so that the term translation editor is usable. Certainly when my cliënt will also translate stuff in the future..

May 27, 2025 at 7:35 am #17076079

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

Sure, we'll do our best to help with this issue, and if it is in our hands, we will fix it.

I'm still unsure about the problem. To better understand, I must check things on your site. Please give me access to your site and explain how to replicate the issue. Which ACF fields and which group are in charge of this, and is there any other information to help me see the problem? Please describe the steps I must take to see this issue. It would be best if you gave me access to a staging site, not your live site.

If you need further help with this, please share the access details to your site with me. I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/
**IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--

Regards,
Itamar.

June 3, 2025 at 9:44 am #17101351

kevinB-5

The problem isn't actively visible right now. I'll check back in when it does!