Problem: You are trying to translate content in ACF repeater fields within a custom block. While the first block translates correctly, in subsequent blocks, only the content fields are visible in the translator, and the title fields are missing. Solution: This issue typically arises when the same field names are used more than once across different blocks. Each field name in your ACF repeater fields should be unique to ensure they all appear in the WPML Translation Editor. We recommend checking and updating your field names to be unique per group. For more details, please refer to our documentation on using the same fields across languages.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, if you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You have an ACF Taxonomy field on a WooCommerce attribute set to Copy, expecting the settings in the original language to automatically apply to the secondary language. However, the fields are editable in the secondary language but are not updating or taking the value of the primary language, leaving all secondary language taxonomy radio lists empty. Solution: We have identified that the taxonomy field requires you to click the update button twice for the changes to reflect correctly in the secondary language. We have documented this issue in our errata. For a temporary workaround, please follow this step: 1. After making changes in the primary language, save and then click the update button again. For more details, refer to our errata here: https://wpml.org/errata/taxonomy-custom-field-metadata-set-to-copy-requires-double-save-for-updates-to-reflect/
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. Additionally, please feel free to open a new support ticket for further assistance at our support forum.
Problem: The client created English content in the theme and translated it into French via String Translations, but the new translations were not appearing on the front end. Solution: 1. Navigate to the
wp-content/languages/wpml/
directory and delete files named "nm_theme_options". 2. Go to WPML > String Translation, find and select the string, and delete it. 3. Access your theme settings while in the English version and re-save your top bar text. 4. Return to WPML > String Translation and re-translate the string.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
