[Resolved] Translated ACF Choices field not showing correctly on frontend
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is using ACF with Bricks Builder and WPML for a custom post type (CPT) like 'Cars' and encountering issues where choice fields such as Select and Checkbox are not displaying correctly in translated versions on the frontend. Solution: We recommend replacing the problematic choice fields with ACF taxonomy custom fields. Create a taxonomy for each field and add the necessary data. After setting up these taxonomies, ensure to translate all of them. This approach has successfully resolved the display issues in other languages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the 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 or visit our support forum at WPML support forum.
0% of people find this useful.
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'm simply using ACF with Bricks Builder and WPML. I have a cars CPT that has fields for car data. Some of the fields are choices fields like Select and Checkbox.
Symptoms:
After translation, all fields are showing correctly in the frontend, but NOT the choices fields.
Questions:
Why are the translated choices fields not showing correctly on the frontend?
Welcome to the WPML support forum. I will do my best to help you to resolve the issue. Sorry for the late response because of the weekend and holidays.
Please visit WPML>>String Translation after a site backup and enable the *Look for strings while pages are rendered* option of *Auto register strings for translation* section(on the bottom of the screen). Then visit the front end pages and check the issue is existing or not.
Thanks for the reply, I recreated the problem with simply using Bricks Builder, ACF and WPML in this site: hidden link
I created a CPT “Cars“ , With 2 Fields (Car Colors: Radio fields), and (Transmission: Select Field), Translated everything correctly but still bricks not showing the correct translation of these choices fields for the other languages.
I have found a work around solution for it, basically what I did is I replaced all these fields with ACF taxonomy custom field ( Which is a choices field ) and made a taxonomy for each field and added its data.
I then translated all these taxonomies and now it is working perfectly.