Problem: You are working on a site and want to exclude certain paragraphs or headings on specific pages from automatic translation using WPML. You have encountered issues where you cannot clear a translation field and save it empty in the ATE, and editing through the WP editor causes the translation to disappear. Solution: Excluding specific paragraphs or headings from automatic translation within the same page using WPML's automatic translation system is not directly possible. To achieve different content on specific translated pages, you can switch from using ATE to the WP editor for those specific pages. This allows you to fully customize the translated versions, including removing content altogether. For detailed steps on how to switch editors and customize translations, please visit Using Different Translation Editors for Different Pages.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You have set up a development copy of your live site and want to ensure that the Advanced Custom Fields (ACF) translation settings configured on the dev site can be exported and then imported into the live site without having to redo the settings. You are concerned whether the import will update the existing ACF fields on the live site or create new ones. Solution: We have tested and confirmed that exporting ACF field translation settings from a development site and importing them into a live site works effectively. The import process updates existing ACF groups and fields, provided they share the same names and other identifiers. However, we recommend that you double-check and confirm the settings after completing the import to ensure everything is configured correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
Problem: The client was experiencing an issue where all images disappeared from translations after setting up WPML Media Translation. Solution: This problem was linked to the incorrect setting of a Flexible Content Field in ACF, which was set to "Translate" instead of "Copy once", leading to corrupted data on translated Custom Post Types (CPTs). We recommended setting the ACF Field Groups used on CPTs to "Different fields across languages". This setting is advised when translating with the WordPress Editor as it avoids the need to configure each field individually. If the issue persists, the client should delete the translated CPTs and translate them again. Alternatively, investigating the
1
wp_posts
and
1
wp_postmeta
database tables to identify the problematic translations could help. Additionally, ensuring that fields are set to "copy" or "copy once" based on the translation editor used (WPML Translation Editor or WordPress Editor) is crucial.
If this solution does not resolve the issue or 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.
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.
