Skip Navigation

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

Problem:
If you're experiencing issues with page content not translating correctly using WPML, and you find that only the English content appears in the body despite other elements like titles and ACF fields translating as expected, the issue might be due to the pages being created or converted with Classic Editor without the correct structure.

Solution:
We recommend converting your Classic Editor content to Block Editor to resolve structural issues. Here are the steps to follow:
1. Edit the page in the default language.
2. Click anywhere in the page content (except the top heading).
3. Click "Convert to blocks" to convert old/classic editor content to proper blocks.
4. Save the page.
5. Repeat these steps for all affected pages.
6. Navigate to WPML -> Translation Management.
7. Select these pages and send them for automatic translation.
Wait for the translations to complete.

Additionally, if you're dealing with slug translations, consider checking the guide at Translating Page and Post URL Slugs.

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend 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. If the issue persists, please open a new support ticket.

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 0 reply, has 0 voices.

Last updated by Waqas Bin Hasan 4 months, 3 weeks ago.

Assisted by: Waqas Bin Hasan.

Author Posts
January 17, 2025 at 9:26 am

gavinW-3

Background of the issue:
I am trying to translate the page content using WPML. All other parts of the page, such as the title, ACF fields, and SEO, are getting translated correctly. The issue is specific to pages and not posts. It used to work fine, but I noticed the issue yesterday. I have tried rerunning translations, but it did not work. The issue can be seen on this page: hidden link.

Symptoms:
The page content is not getting translated into Arabic. Instead, I see English content in the body.

Questions:
Why is the page content not getting translated while other parts are?
Why does this issue occur only for pages and not posts?
What steps can I take to resolve this translation issue?

January 17, 2025 at 10:18 am
January 17, 2025 at 10:19 am #16605281

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

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

Hi,

Reference to our recent chat, looks like you got disconnected while I waited for a long time and finally moved to this ticket.

I want to confirm that if it is OK to deactivate the plugins in the site? I need to deactivate except WPML to investigate the issue.

I can see that translations are present and content was translated correctly but somehow not rendering correctly on frontend.

Please let me know.

Thanks.

January 17, 2025 at 12:51 pm #16606174

gavinW-3

Yeah its okay to deactivate them

January 17, 2025 at 2:22 pm #16606558

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

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

Thank you for the updates. I'll continue further with the investigation and 'll update you accordingly.

P.S.: I'll be off for the weekend and 'll be able to attend on Monday.

January 20, 2025 at 4:55 am #16611644

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

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

Thank you for your patience and cooperation. I've resumed working on it and found that with even only WPML the issue is still there.

I'm digging further and 'll get back to you as soon as I find a solution.

January 20, 2025 at 6:00 am #16611710

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

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

Thank you for your patience and cooperation. I was able to find and fix the problem, for example, hidden link.

Looks like the existing pages were created (or converted) somehow which used Classic Editor and didn't have correct structure. This caused following problems:

- Content isn't shown as translated on frontend.
- New changes in default language (within these classic editor contents) aren't updating in the translation editor.
--- So the translations on the frontend are simply showing the default language content.

I tested by creating a new test page (hidden link) where I used Classic Editor block and this worked just fine (hidden link). So the existing pages, using the same Classic Editor blocks have either incomplete or corrupted page structure.

To fix this, I edited hidden link in default language and converted the classic editor to blocks, saved the page and updated Arabic translation manually in Advanced Translation Editor (ATE). Several new content appeared in the editor which needed translation. I used Google Translate to translate that content manually and completed the translation to 100%. While previously translated content was already available in the ATE due to Translation Memory.

And Arabic translation of the said page, hidden link, now working as expected. All you need is to simply send this page again for translation (for rest of the languages) and all translations of this page should work as expected on the frontend.

To fix for all other pages or posts having this issue, please follow these steps:

- Edit the page in default language.
- Click anywhere in the page content (except top heading).
- Click "Convert to blocks" to convert old/classic editor content to proper blocks and fix all the structural issues (see attached).
- Save the page.
- Repeat these steps for all pages.
- Go to WPML -> Translation Management.
- Select these pages.
- Send for automatic translation and wait for translations to complete.

A few points to consider:
- Since these pages have already been translated, sending again 'll not cost additional credits (due to Translation Memory as mentioned above).
- Additional credits may be charged, only if, there were new content added in these pages, which may not be appearing properly previously. But I believe either there 'll no additional charge or a minimal for the new content (as detected by the ATE).

P.S.: I have switched to "Translate What You Choose" mode in WPML -> Settings -> Translation Mode, to stop auto-translate and haven't consumed any credits (did my translation tests manually). Remember to switch to "Translate Everything Automatically" mode accordingly.

Screenshot 2025-01-20 104205.jpg
January 21, 2025 at 11:56 pm #16620799

gavinW-3

Thank you very much, that seems to work now

But one new issue is the translated content for the `What is the UK ETA? An Overview
What is the UK ETA? An Overview` page. The translated posts have the number 2 in their slug like this: "uk-eta-overview-2"
How can this be resolved? It should be just uk-eta-overview just as the English post is

January 22, 2025 at 5:50 am #16621075

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

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

Thank you for confirming and glad the issue is resolved.

For the slugs, I'll recommend checking this guide https://wpml.org/documentation/getting-started-guide/translating-page-slugs/#translate-page-and-post-url-slugs. However, generally you can control slug translation in WPML as following:

- Go to WPML → Settings. Scroll to Translated documents options.
- Under Page URL, choose the desired option.
- Click Save.

So this option is regarded for any new content you translate.

For the existing pages, you can simply try the following:

- Edit the translation.
- In ATE (Advanced Translation Editor), look or search for the slug.
- Correct as needed.
- Complete the translation.
- If that doesn't work, then open the content for editing in original language.
- Switch to the other language from top admin bar.
- Click "Edit anyways" if asked.
- From the sidebar, look for the page slug or URL, click it to edit.
- Change and save as needed.

If you need more help on this, I recommend opening a separate ticket/chat because as per forum policy we can only handle one issue per ticket/chat. So you can get more to the point help, without mixing up several issues in one long ticket.