Problem: The client has a number of ACF fields, including a repeater field with an image subfield and a text subfield. The issue arises when trying to handle translations for these fields in a duplicated page. Solution: If you're experiencing this issue, we recommend setting the repeater field to 'COPY' if you want the changes in the default language to be copied or synced to the second language. This setting is necessary when the page is duplicated and you wish to add translations independently. For more detailed guidance on setting up your ACF fields with WPML, please visit our documentation on Recommended Custom Fields Translation Preferences for ACF and WPML.
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: The client is experiencing issues with fields being greyed out in the WordPress Editor and content being erased in the Advanced Translation Editor (ATE) when making changes to translations of custom fields in a Custom Post Type (CPT). These fields are part of ACF groups that are disabled and used as clone fields in another ACF group. Solution: 1. To address the issue of content being erased in the ATE, we recommend disabling the "I prefer bigger segments" feature in the ATE. This allows breaking down each sentence from a paragraph into smaller segments, helping to avoid retranslating the entire paragraph. Resave your primary language page after making this change. 2. For the greyed-out fields in the WordPress Editor, set the clone fields to 'translate' instead of 'copy'. This change will make the text/textarea fields within the clones manually translatable through the WordPress Editor.
If this solution does not resolve your issue, or if it seems 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is working on a site using WPML with ACF fields and experiencing issues where ACF fields (text, wysiwyg, link) are not showing up in the Advanced Translation Editor (ATE) unless searched for, and ACF field labels are appearing in the ATE despite being set to not translatable. Solution: We found that the fields were set to 'Copy Once' instead of 'Translate', which is why the content was not added to the translation editor. We recommend changing the translation preferences from 'Copy Once' to 'Translate' for the fields you want to appear in the ATE. This setting adjustment should allow the fields to display correctly in the ATE. For detailed guidance on setting translation preferences for ACF fields in WPML, please check the following documentation: Recommended Custom Fields Translation Preferences for ACF and WPML.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needs to change the language of over 400 posts that were incorrectly duplicated and translated within the same language instead of being assigned to their respective German and Spanish versions.
Solution: We recommend the following steps: 1. Make a database backup. 2. Export the posts to CSV files for each language using WP All Export and WPML documentation. 3. Delete all the posts from all languages and remove them from the trash. 4. Import them again, ensuring to select the proper language during the import process as outlined in the WPML All Import documentation.
If this solution does not seem relevant to your situation, please open a new support ticket in the WPML support forum.
