This thread is resolved. Here is a description of the problem and solution.
Problem: The client has completed translations for their homepage in Dutch, French, and German, but when viewing the homepage in any language other than English, no content appears, despite the translation edit screens showing 100% completion.
Solution: We checked the homepage and found that the fields were not copied or translated to the second language. We edited the "Components" field group and set the fields to be copied, which resulted in some content appearing on the Dutch homepage. We recommend the client to: 1. Edit fields that use Expert Mode and ensure the correct translation preference is set. 2. Update the default language page and its translations after changing the translation preferences.
We also provided guides to assist with this process:
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, please open a new support ticket here.
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.
Thanks for contacting WPML forums support. I'll be glad to help you today.
I would need to look closely at your site, so I would need to request temporary access (WP-Admin and FTP) Preferably to a test site where the problem has been replicated.
Your answer will be private, meaning only you and I can access it.
❌ Please backup your database and website ❌
✙ I would need your permission to de-activate and re-activate the Plugins and the Theme and change configurations on the site. This is also a reason the backup is critical.
✙ I also need your permission to take a local copy of your site to debug the issue without affecting your live site.
Thanks for the access details. I checked the home page and found that the fields are not copied/translated to the second language, so I edited the "Components" field group and set the fields to be copied. (Kindly check the attached screenshot)
After that, some content appeared on the Dutch home page. Please edit your fields that use Expert Mode and make sure that you use the correct translation preference.
Hey, yep I have seen that update, thank you. Still a few other components not showing but I should think I'll be able to resolve those myself.
The only other few things are, I have a Theme Settings option page setup—which constructs a header and footer—I have set these to "same across languages", which I thought would fall back to the default language, but it isn't—and as you probably saw, the other languages don't show a header or footer, what am I doing wrong here?
Ahh that's a shame that it won't fallback to the default language, but okay. Thank you.
I'm still having issues making the "Links" and "Collection" component appear on the screen... could you have a look for me?
Also on the Home page, I am seeing this notice: "You need to translate this post manually because the field groups attached to it use different translation options.".
The "Links" field group was set to the Expert mode, and all the fields were set to "Not Translatable", so I set the translation mode to "Same Fields Accros Languages". (hidden link)
Please check if the Links group fields work correctly.
1. In Theme Settings > Header, there's a "logo" field. On English and French, this is set, but when I view the page, only the English (default) version is showing the logo.
2. When I go to edit About Us—it seems to have lost the ability to use the Advanced Editor, I seem to be taken to the default editing screen...
Sure, you can leave it open and let me know if you need further help regarding the homepage issue.
If you have another issue, may I kindly ask you to open a new ticket for your additional question?
We try to keep one issue per ticket in our forum. Continuing with one ticket per issue helps supporters focus on one issue at once and enables other users to find solutions to their questions faster.