Skip to content Skip to sidebar

Home › Support › English Support › [Waiting for user feedback] Button Links are not pointing to translated page automatically

[Waiting for user feedback] Button Links are not pointing to translated page automatically

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 is split from https://wpml.org/forums/topic/links-to-a-new-post-type-are-not-translated/

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: Asia/Singapore (GMT+08:00)

Tagged: 

This topic contains 15 replies, has 0 voices.

Last updated by Kor 1 day, 22 hours ago.

Assisted by: Kor.

Author Posts
October 21, 2025 at 3:18 pm #17503691

arnoP-3

I manually translated the button link on hidden link, and another is hidden link where the button still links to English on the German translation.
October 22, 2025 at 4:06 pm #17509108

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. I've escalated this to our 2nd Tier Support for further investigation.

October 29, 2025 at 4:38 pm #17530364

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. Could you share FTP access to the dev site? Also, please allow me to create a backup package for escalation.

October 31, 2025 at 8:01 am #17534884

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks, I've forwarded this to our 2nd Tier Support. I will come back to you once I've response.

November 4, 2025 at 3:28 pm #17546505

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your patience. I've corrected the custom XML configuration and it should work correctly now. Could you please retry?

<gutenberg-block type="meta-box/ohcc-block-button" translate="1">
      <key name="data">
        <key name="block_button_text" />
        <key name="block_button_url" type="link" />
      </key>
      <key name="block_button_url" type="link"  />
    </gutenberg-block>

Testing on this hidden link and the links are auto translating as shown in the attached screenshot.

Screenshot_125.png
November 5, 2025 at 9:24 am #17548958

arnoP-3

Thanks Kor. I created a brand new "child post", the ones we're linking to. I translated it too.

Then I added links to that new post in the same places (intro text and button) on this page: hidden link

The translation editor does not translate the URL (see attached). I ignored that and only translated the texts and then saved the translation. The translated page hidden link now contains an English link in the summary. I thought this was solved, but it's failing again. The button link is ok though.

Why is this so difficult? What's different here than all the other translations throughout the site that work fine?

WPML URL not translated.jpg
November 5, 2025 at 1:32 pm #17550468

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. I've tried to test this on a new page but I'm having issues saving it as shown in the attached screenshot.

Could you create a new page and only insert a wp:meta-box/ohcc-block-button pointing to a translated URL? I'd like to isolate the issue and retest this and then, show this to our 2nd Tier Support if the issue persists.

Screenshot_135.png
November 5, 2025 at 2:20 pm #17550688

arnoP-3

Sorry, that error is because the post has a couple of required fields:
1) Content summary - Content long title (any text)
2) Content classification - Content popularity (any number, e.g. 0)
3) Content management - Content last update (any date)

On child posts, it's the same fields, and in addition:
4) Post hierarchy - Parent post

I created this new post: hidden link
November 5, 2025 at 3:04 pm #17550905

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. I've just forwarded this to our 2nd Tier Support for a second look.

November 5, 2025 at 4:02 pm #17551160

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your patience. The link corrects it automatically after the translation is saved. You may check now hidden link

November 6, 2025 at 8:47 am #17552575

arnoP-3

But in my last test, I saved the translation too.

Anyway, I tried again and changed the button link on hidden link to point to hidden link

Then I updated the translation of hidden link. It showed an empty translation for the URL hidden link. I ignored that and saved the translation. Indeed, the button URL is now fine in the frontend.

I can't say I'm very confident it's fully solved. It feels like it works randomly, and the empty link in the translation editor is weird.

But, if you're convinced it is solved, please let me know the final steps.
- I guess I can already update the XML on the live site? Is it only the section you shared on November 4, 2025 at 3:28 pm?
- And then wait for the WPML update that contains the fix?
November 6, 2025 at 9:36 am #17552771

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. Yes, this is solved. Please copy the entire custom XML configuration from the dev site and paste it into your production site. Then, make minor edits to the primary language page so that the Advanced Translation Editor could resync the contents.

November 7, 2025 at 7:35 am #17556126

arnoP-3

Ok, for reference, on the live website, I replaced this:

<gutenberg-block type="meta-box/ohcc-block-button" translate="1">
<key name="data">
<key name="block_button_text" />
</key>
</gutenberg-block>

by this:

<gutenberg-block type="meta-box/ohcc-block-button" translate="1">
<key name="data">
<key name="block_button_text" />
<key name="block_button_url" type="link" />
</key>
<key name="block_button_url" type="link" />
</gutenberg-block>

But, I also have to wait for an official release containing the fix that was made before, right? Only then, the link will be translated in both locations that were problematic in my original request?
November 7, 2025 at 7:55 am #17556145

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. Yes, that code replacement is correct. There won’t be a fix for this since it’s not a workaround. You just need to add the correct custom XML configuration to tell WPML how to translate the links.

After updating the custom XML configuration, make a small edit to the page in the default language and retranslate it. The links should then update correctly.
November 7, 2025 at 8:52 am #17556327

arnoP-3

Sorry, I got confused because the original problem was split into two support tickets:

- What we're discussing here is solved with the adjusted XML.
- The issue here https://wpml.org/forums/topic/links-to-a-new-post-type-are-not-translated/ requires me to update WPML once there is a new release containing the fix.

That's it, right?