Problem: The client is trying to make Search & Filter Pro work with a second language on their website. The filters should capture values from an ACF field, which are translated using WPML String Translation. However, the filters do not recognize the translated values.
Solution: We have investigated the issue and our 2nd Tier Support has provided feedback. The problem arises because while labels can be translated using ACFML filters when calling ACF functions on the front end, the translated values, which are part of post meta, cannot be translated on the front end. Manually adding translated values in the code of the Search and Filter Pro plugin is not recommended, as these values may change upon post translation, leading to mismatches.
We recommend keeping the values common across all languages and translating only the labels. You can set up your ACF fields with a value:label pair and then translate the labels, keeping the values the same. For example:
all : 전체<br />domestic : 국내<br />intl : 국외
This approach ensures that the values remain consistent while the labels are displayed in the correct language to the user.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking the related 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.
Problem: The client is having an issue related to ACF where he uses ACF Shortcodes to display ACF Fields in Elementor and the fields were not translated.
As the shortcodes also included raw text this raw text was showing on the translated content.
Solution:
We were not able to identify an issue on this ticket, apart from expected behavior, as the affected ACF Fields and their shortcodes were not yet translated.
If you're experiencing similar issues with Dynamic Visibility and ACF Fields not behaving as expected in translated content, here are the steps you can take: - Ensure that ACF Fields are filled out, as empty fields can cause visibility issues. - If changes do not reflect immediately, allow some time as it might take a while for the system to update. - Check the page URL settings and ensure they are set to 'copy from the primary language' if issues persist.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
