This thread is resolved. Here is a description of the problem and solution.
Problem: You have multiple MB text fields on your homepage, but some are not visible in the WPML Advanced Translation Editor screen, even though they are set to 'Translate' in WPML > Settings > Custom Fields Translation. Solution: We recommend adding the following line to your functions.php file:
After adding this code, edit the page in the default language, make a minor edit, and then update it. This should allow the missing fields to appear when using the search field in the Advanced Translation Editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
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.
Background of the issue:
I have multiple MB text fields inside my homepage, but for some of them, I don't see them in the Advanced Editor screen. Those fields are set to 'Translate' inside WPML > Settings > Custom Fields Translation.
Symptoms:
Some MB text fields are missing in the WPML Advanced Translation Editor screen.
For example I don't have homepage__pourquoi_bloc_1_chiffre_1, homepage__pourquoi_bloc_1_chiffre_2 and homepage__pourquoi_bloc_2_chiffre but I do have homepage__pourquoi_bloc_3_chiffre
Questions:
Do you know why some MB text fields are not appearing in the Advanced Editor screen?
Is there a way to refresh the screens so WPML fetches all the fields?
Thanks for contacting WPML forums support. I'll be glad to help you today.
Please let me know how these fields are added in the default language.
Also, please try the following steps:
1- Edit the home page in the default language
2- Add "V2" to the page's title and update it
3- Delete the "V2" and update the page
4- Update the translation using the translation editor
1 - Clear Litespeed cache
2 - Go to my homepage in default language (FR) and click edit page in the admin bar
3 - Click on the page title, add "V2" at the end and click the "Update" button
4 - After the page is updated (notification) I remove the "V2" and click "Update" again
5 - After the page is updated I click the "Update French (Canada) Translation" icon within the WPML sidebar
6 - Then inside the Advanced Translation Editor, I still not see my field, just the dynamic tag of Bricks that is used to fetch the value of the metabox field
See screenshots that show that I still cannot see the **field-MB_FIELD_ID**
Thanks for your update. 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 need your permission to deactivate and reactivate the plugins and themes and change site configurations. This is also why 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.
Why is your Advanced Translation Editor in dark mode and does not have the same layout as what I have on my website?
I checked the plugin version, and it is the same.
On my development website, I deactivated every plugin to match what you have on your sandbox, keeping only the Bricks theme activated. However, I still can't see the "17%" when I edit the translation on my homepage (FR-BE).
Please check the development website again and let me know what's going on with my WPML setup.
Thanks for your update. The numbers issue will be fixed in the next version of ATE. Currently, the workaround is to translate this field manually by editing the translated page using WordPress editor.
Also, I'll consult our second-tier support team about this issue to see if there is another workaround.