ACF field label translations not applying when page is accessed via direct /he/ URL

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing an issue where ACF field labels such as 'Location' and 'Photographer' display in English instead of Hebrew when accessing a Hebrew post directly via a /he/ URL, despite having translated these labels in WPML String Translation, this might be due to the labels not applying when the language is determined solely from the URL path.
Solution:
We recommend updating your WPML plugins and all related add-ons to the latest version, currently 4.9.5, to ensure you have the latest bug fixes and improvements. You can check for updates in your WordPress dashboard under Plugins → Add New → Commercial, or download them from My Account → Downloads on wpml.org. Before updating, please make sure to back up your database. If updating does not resolve the issue, we may need temporary access to your site to investigate further.

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 problem 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.

Tagged: Compatibility, Exception

This topic contains 5 replies, has 0 voices.

Last updated by Andrey 1 month, 1 week ago.

Assisted by: Andrey.

Author	Posts
June 8, 2026 at 1:53 pm #18087685
marcM-67	I have a Custom Post Type called 'Sunrise Photos' with ACF fields including 'Location' and 'Photographer.' The Elementor loop item template displays these fields with their ACF field labels. In WPML String Translation I have translated both strings correctly: 'Location' to 'מיקום' and 'Photographer' to 'צלם.' These translations are registered under the ACF field group domain. The problem: when a visitor arrives at a Hebrew post directly via a /he/ URL (for example, from a link in an email newsletter), the field labels display in English as 'Location:' and 'Photographer:' rather than in Hebrew. All other content on the page, including the post date, the quote, and the field values, correctly displays in Hebrew. Only the ACF field labels stay in English. What works: when navigating to the same page through the website with the Hebrew language session active, the labels correctly display in Hebrew. What I have confirmed: 1. The WPML String Translation entries for 'Location' and 'Photographer' are correctly entered with Hebrew translations. 2. The Elementor loop item template shows the Hebrew labels correctly in the editor. 3. The /he/ directory is correctly configured in WPML Language URL Format settings. 4. Testing in a fresh browser with no cookies also shows English labels on a direct /he/ URL, so this is not a cookie issue. 5. Browser language redirect is disabled. 6. The issue is specific to the ACF field label strings. Dynamic field values and all other post content switch to Hebrew correctly. This suggests the WPML string translation for ACF field labels is not applying when the language is determined from the URL path alone, and only applies when there is an active browsing session. Please advise on a fix or workaround. Please note that the uploaded visuals are screenshots but include texts with descriptions relevant to this request as well as red rectangles showing the translations that are relevant.
June 9, 2026 at 1:28 pm #18090645
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for contacting WPML support and for providing detailed information about the issue. Could you please try regenerating the translation files and check whether that resolves the problem? Here are the steps: 1. Go to WPML → Support → Troubleshooting. 2. Scroll down and click “Show custom MO Files Pre-generation dialog box”. 3. The page will refresh, and a popup should appear. 4. Click “Generate MO Files” and wait for the process to complete. If the popup does not appear, please go to WPML → Theme and Plugins Localization. The popup should be displayed there, allowing you to generate the MO files. Once the regeneration is complete, please test the issue again and let me know the results.
June 10, 2026 at 8:32 am #18092443
marcM-67	Hi Andrey, I passed your message on to my website tech person who did what you suggested, but it did NOT solve the problem. I hope that you will be able to find the source of this glitch and fix it. I will be at my computer for most of the next 6 hours (with a short break in the middle). I will leave this chat open so as to get whatever messages you may have in realtime. Thank you, Marc Marcus
June 10, 2026 at 7:54 pm #18094623
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for your feedback. We have just released new versions of the WPML plugins. Before I investigate this further, could you please update WPML and all related add-ons to the latest version, 4.9.5, to benefit from the latest bug fixes, compatibility improvements, and performance enhancements? While this update may not necessarily resolve the issue, it is important that we troubleshoot using the most recent codebase available. If you do not see the updates in your WordPress dashboard, please go to: Plugins → Add New → Commercial and click “Check for updates.” You can also download the latest versions from My Account → Downloads on wpml.org. Update instructions can be found here: http://wpml.org/faq/install-wpml/ Before proceeding, please ensure that you create a full backup of your database. Once the update is complete and the issue persists, I need to request temporary access (wp-admin and FTP) to your site—preferably to a test site where the problem has been replicated, if possible—so I can better help. When you log in to leave your next reply, you will find the needed fields below the comment area. The information you will enter is private, meaning only you and I can see and access it. Just in case, please include the steps to replicate the issue.
June 11, 2026 at 9:32 am #18095916
marcM-67	Hi Andrey, After installing the updates it would appear that THE PROBLEM IS SOLVED. If there should be any further problems I will be in touch. THANK YOU VERY MUCH FOR YOUR HELP. Have a good day, Marc Marcus
June 11, 2026 at 9:56 am #18095956
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for your feedback, Marc Marcus. I am glad to hear that the issue is resolved. You are always welcome. Have a nice week.