Home›Support›English Support›[Escalated to Compatibility team] ACFML label translation incompatible ACF Local JSON feature
[Escalated to Compatibility team] ACFML label translation incompatible ACF Local JSON feature
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.
Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.
I use the Local JSON feature of ACF described here hidden link. However, when I try to translate the labels of custom fields using WPML String Translation, they are not displayed. Removing the acf-json directory from my theme allows them to work as expected. It seems like the Local JSON feature is not compatible with the new method of translating custom field labels.
Hello There,
Thanks for contacting WPML Support. I will try my best to assist you in this matter.
Kindly note that WPML seamlessly integrates with ACF Local JSON. After saving and synchronizing the JSON file (as described in hidden link), and ensuring that field translations are correctly added, the content will be displayed correctly in all languages.
As you've mentioned that the translated label is not appearing properly, are you trying to output the Field label somehow? I also would like to inform you that when you try to translate the page or post that contains the ACF field, those fields, including the Label will appear in the Translation editor, Would you please try to translate the Field label from there and check if you're getting the expected result?
Hi and thanks. Here is a link to a video of my attempt to translate fields. The frontend form is being displayed using the acf_form() function. hidden link
I hope you're doing fine and am sorry for the delay in getting back to you.
I appreciate your effort in making the video and sharing that with us. I can see that the translation for the label is applied correctly but that translation will only work in the Backend. Since you're retrieving the labels in the Frontend, you need to register the labels for Translation and then you'll be able to display the Translated labels on the Frontend.
Without the presence of the acf-json folder the strings are correctly translated. When I add the acf-json folder to the Twenty Twenty One the translations stop working.
Thanks for testing further and sharing the updates. As the solution didn't work, a closer inspection will require to understand the root cause. I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue.
It would be better to have a testing site where the issue is replicated.
You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please make a backup of site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Looking forward to your response and thanks for your patience and kind cooperation.
Thanks for sharing the credentials. I have checked and successfully been able to reproduce the in my development environment.
The issue is already been forwarded to the 2nd tier team for further investigation. When I have more updated on this issue, I will surely let you know.
Thanks for your kind cooperation and patience in this matter. Feel free to let me know if you have anything else to share regarding the issue.
Hi There,
I hope you're doing well and sorry for the delay in getting back to you.
I can understand the importance of resolving this matter but, at the moment, I don't have any specific suggestions to offer. However, please be assured that our second-tier team is actively working on identifying the root cause of the issue. Once our team has made progress in identifying the root cause, we will update you with further information and any recommended actions. I appreciate your patience and understanding in this matter.
Our 2nd-tier team has thoroughly investigated the issue and has successfully been able to trace the root cause and also a workaround for the issue. The problem was mainly caused due to the absence of the ID for the fields group and fields in the exported JSON file.
In order to solve the issue, insert the ID of the field group and fields in the exported ACF JSON file. The fields will start to appear translated right after that. You can locate the ID of the field group and the fields easily from the String Translation section.
Please check this video to understand the overall process: hidden link
The issue will be resolved once the adjustments are implemented properly. However, please don't hesitate to reach out if you require any clarification or further assistance with the procedure. I am here to help and will be glad to assist you.
Thanks for this. Your solution works, however, it is not sustainable to modify the acf-json files manually. Are you in contact with the ACF developers and can communicate this incompatibility to them, or is that something that I will need to do to have the problem resolved?
I would like to inform you that the issue is already been escalated to the relevant team. They are actively investigating the matter and working towards finding an optimal solution. If required, they will reach out to the ACF authority to address the issue effectively. I hope you can understand.
Please continue using the current workaround for now. Rest assured, you will be notified as soon as we have more information for you regarding this matter.
Hi There,
Thank you for bringing that to my attention.
It seems that the status was changed, which is why it wasn't appearing in your list of open tickets. I have now updated the status, and it will remain open accordingly.
Has this issue been resolved? It no longer appears in my "open tickets" list.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
