[Resolved] Choice of ACF Field not being translated
This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported issues with translating content using Kadence Blocks and themes in conjunction with WPML Solution: 1. We confirmed the potential compatibility conflict between WPML and Kadence products. 2. It is a compatibility issue with Kadence blocks and Query Card.
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 at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I created an ACF field "Language" (Type: Checkbox). The choices are "English", "German", "Italian"... I translated the choices in String Translation. However, everything is still in English in the frontend.
Symptoms:
Translated choices in the ACF field are not displaying in the frontend; they remain in English.
Questions:
What must be done so that I see in German the assigned translation "Englisch", "Deutsch", "Italienisch"?
Welcome to the WPML support forum. I will do my best to help you to resolve the issue.
Please check you have updated the Post translation after completing the translation of ACF Field Labels. Refer to the following documentation for more details.
If you are still facing the problem, please fill the private details fields after a full site backup. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information sharing policies.
Thank you for the details and login information. It looks like there might be a compatibility conflict.
I have a dobut about the Query Card post type. It is not set as translated. So how are you managing it in secondary languages, especially since you are using it to list values here - hidden link
So far a translation for the query Card wasn't necessary. It pulls the translated title correctly. Therefore, I find it strange that the translation of the values gets ignored.
Making the Query Card post type translateable doesn't help. I translated it into German but the outcome is the same.
I also assume that there is some compatibilty issue between WPML and Kadence Query Loops. How do you approach these issues? Is there some technical documentation that describes how to make a query loop and ACF field or any other element within translatable with WPML?
Thank you for the feedback. Please allow me to make a duplicator copy of your site using the Duplicator plugin(https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. So we can troubleshoot the bug without affecting your site.
I have installed the Duplicator packages on our testing servers. But somehow the hidden link page is showing the following fatal errors in the local copies. It also happens when all the WPML plugins are inactive.
Fatal error: Uncaught TypeError: Query_Frontend_Filters::sort_terms_hierarchically(): Argument #1 ($terms) must be of type array, WP_Error given, called in ****\kadence-blocks-pro\includes\query\query-frontend-filters.php on line 537 and defined in ****\kadence-blocks-pro\includes\query\query-frontend-filters.php on line 186
TypeError: Query_Frontend_Filters::sort_terms_hierarchically(): Argument #1 ($terms) must be of type array, WP_Error given, called in ****\kadence-blocks-pro\includes\query\query-frontend-filters.php on line 537 in ****\kadence-blocks-pro\includes\query\query-frontend-filters.php on line 186
Have you ever faced this error? Is it because the license key for the Kadence theme is missing in our local copies?
Hey, brief update. I informed Kadence that we don't need any further assistance. In case any other users experience the same issues with translations, please get in touch with Kadence.
