Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client wants WPML to automatically scan internal links from default/custom Gutenberg blocks and ACF Link fields to ensure that users are directed to the correct language version of a page. They encountered issues where changes on the source page were not applied to the translated page.
Solution:
For ACF Link fields, the translation preference should be set to 'Translate' to allow for automatic scanning of links. For custom Gutenberg blocks, if they are rendered via React using a JSON data prop, the internal links might not automatically update to point to translated pages. In such cases, disabling WPML Translation for the specific page and translating it manually with the default WordPress editor is recommended as a workaround. More details can be found here: Using different translation editors for different pages.
Additionally, a separate ticket was created to address the issue of changes not being applied to the translated page, which can be followed here: WPML support forum topic.

If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.

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.

Tagged: 

This topic contains 3 replies, has 0 voices.

Last updated by Noman 2 months ago.

Assisted by: Noman.

Author Posts
September 24, 2025 at 7:35 am #17427608

hounOC

Background of the issue:
I want WPML to automatically scan internal links from default/custom Gutenberg blocks and ACF Link fields, instead of manually 'translate' the links in ATE. This is to ensure that users from one language version page, when clicking on a button with an internal link, are directed to the correct language page. I am working on the site hidden link.

Symptoms:
No specific issue or error message mentioned.

Questions:
In ACF Link field, which translation preferences should I choose to achieve this auto scanning: Copy, Copy Once, or Translate?
For custom Gutenberg blocks, what coding or syntax allows WPML to auto scan the internal links?

September 24, 2025 at 10:57 am #17428755
hounOC

Hi, I created this custom block myself.

New threads created by Noman and linked to this one are listed below:

https://wpml.org/forums/topic/please-wait-applying-translation-but-changes-not-applied/

September 24, 2025 at 5:26 pm #17429974

Noman
WPML Supporter since 06/2016

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

I followed these steps while checking the issue:

1. Tried using the XML method to reflect the translation on the frontend, but the issue persists.

2. Ran troubleshooting options from WPML >> Support to sync ATE.

3. Checked the ATE error log and found errors. After enabling error reporting, multiple warnings/errors were coming from your theme.

Since this issue is with a custom-built Gutenberg block, it may fall under custom programming, where we provide only limited support. As a workaround, you could disable WPML Translation for the specific page where the block is used and translate it manually with the default WordPress editor. More details here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/

If you’d like, I can create a fresh WordPress site for testing. I’ll share the access with you, and I’ll need you to reproduce the issue there by creating the same custom block. This will help us debug the problem in a clean environment without theme or plugin conflicts.

Thank you for your cooperation

September 30, 2025 at 5:55 pm #17446112

Noman
WPML Supporter since 06/2016

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

For the changes on the source page never applied to the translated page problem, it’s a different issue and will be handled separately as per our support policy. I've created a new private ticket for this at: https://wpml.org/forums/topic/please-wait-applying-translation-but-changes-not-applied/

If the custom block translation issue is solved, please mark this ticket as resolved and we will continue working on the above ticket.

Thank you for your cooperation