barjD-2

Problem:
The client was experiencing issues with not all ACF fields appearing in the WPML Translation Editor despite being set up identically. They were unsure how to ensure all fields are included in the translation process and faced difficulties with saving the 'Same fields across languages' setting in WPML.
Solution:
1) Ensure that the 'Same fields across languages' setting is selected for the ACF field groups when using the WPML Translation Editor. This setting should be saved by clicking 'Save Changes' in the ACF UI.
2) Set the ACF Field Groups to 'Not translatable' in WPML > Settings > Post Type Translation to avoid translation issues. If there were previous translations for these field groups, they should be removed.
3) Do not use the same field name more than once within your ACF groups to prevent conflicts.
4) Always use the WPML Translation Editor or the WordPress Editor consistently for translations. Mixing these methods can lead to loss of data.
For detailed guidance on setting up ACF fields for translation with WPML, refer to the documentation here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
The client is trying to translate the 'Roles:' string from the Genesis theme, which is added via the functions.php file. The string is not appearing in WPML's String Translation search even after scanning the theme and child theme.
Solution:
1. Enable the 'Look for strings while pages are rendered' option in WPML >> String Translation page.
2. Visit the page where the string appears on the front end.
3. Return to the WPML >> String Translation page and search for the 'Roles:' string.
4. Translate the string and then disable the auto-registration option.
If this does not resolve the issue, install the String Locator plugin (https://wordpress.org/plugins/string-locator/) and search for the text in theme or theme bundled plugins files. Ensure the 'Roles:' string is wrapped in the gettext function, as detailed in the documentation (https://wpml.org/documentation/support/translating-the-theme-you-created/#wrap-all-texts-in-gettext-calls).
Alternatively, replace the existing code in functions.php with:

/* Add Trustee Roles to Trustee Single pages*/<br />add_filter( 'genesis_post_meta', 'monochrome_display_custom_tax' );<br />function monochrome_display_custom_tax($post_meta) {<br />    $roles_string = __('Roles:', 'themedomain');<br />    $post_meta = '[post_terms taxonomy="trustee_role" before="'.$roles_string.' "]';<br />    return $post_meta;<br />}

Then, scan the theme again and translate the 'Roles:' string via WPML >> String Translation page.

If the solution provided here 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. If needed, please open a new support ticket at WPML support forum for further assistance.