Problem: The client needed to know how to use a single ACF text field in multiple languages on a WordPress site without having to translate the ACF label. Solution: We advised the client that when they create a field in ACF, it is available across all languages and can be accessed from each language within the specified post type. It is important to ensure that the translation settings for the field group containing the field are correctly configured. We recommended using the "ACF Multilingual" plugin and adjusting the translation settings for the field groups and fields within it. We provided a guide for detailed instructions:
We also noted that according to the WPML Debug Information, the plugin was not active on the client's site. We advised the client to install and activate the "ACF Multilingual" plugin and set up the translation mode for the field group.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, 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 with us for further assistance.
Problem: The client needed to obtain WPML settings for custom fields using the ACF API but was unsure of the approach since no examples were provided. Solution: We recommended using the
get_field_object()
function to retrieve an array and then access the WPML settings with
$field['wpml_cf_preferences']
, which returns values 0, 1, 2, or 3, indicating the translation preference for the custom field. Specifically, a return value of "2" means that the custom field is set to translate. Additionally, we provided links to documentation for hooks that can be used to obtain WPML settings:
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at our support forum.
Problem: The client needs to use a specific language translation code such as "es-419" for translations, but is unsure if the default locale field is the correct place to define this code, especially since there is an issue with using a dash "-" in the language default locale. Solution: We explained that the XLIFF uses the hreflang to pull the source language for the target-language attribute. However, we currently do not have a feature that allows for the overwriting of this attribute specifically for XLIFF while keeping it unchanged for the site. If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
Problem: The client is trying to retrieve all posts for a single language code using WP_Query and WPML filters, specifically for the default language code 'en'. The provided code with the
and the custom function did not work, as it still retrieved posts in all languages.
Solution: We recommend using
'suppress_filters' => false
in the WP_Query arguments. This will ensure that the query retrieves posts in the current language when on the English version of the website. For further optimization, the client can specify the fields they want to retrieve, such as 'ID', 'post_title', and 'post_content'. For more information on debugging theme compatibility with WPML, please visit: Debugging theme compatibility with WPML. Additionally, for WPML hooks reference, check out: WPML hooks reference. For WordPress reference on get_posts, please see: WordPress get_posts function.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
