This thread is resolved. Here is a description of the problem and solution.
Problem:
The client reported that after translating a property into Greek, the content was missing on the Greek page. Additionally, some fields were still untranslatable.
Solution:
We advised the client to ensure that the ACF Field Groups were set to 'Not Translatable' in WPML → Settings → Post Types Translation. Then, in ACF → Field Groups → Property Fields, we recommended using the option to apply all fields across languages. For finer control, we suggested switching to 'EXPERT' mode to access field-level options.
To address the missing content on the Greek page, the following steps were taken:
1. Edited the property in the default language.
2. Switched to Greek using the language switcher.
3. Scrolled to Theme/Page Options and copied the same settings from English to Greek, ensuring the Content Layout → Post Template was set.
4. Set the custom field 'thegem_page_data' to copy.
For the untranslatable fields, we set the specific field 'ammenities' to 'Translate' in ACF Field Groups under 'Expert' mode and updated both the property and its translation.
If this solution does not resolve your issue, or if it seems outdated, 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 problems persist, 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.
This topic is split from https://wpml.org/forums/topic/custom-post-not-showing-in-the-backend-in-the-language-for-translation/
