The solution you provided is not feasible because we have a huge data with thousands of pages. We request you to setup a call to understand the other way.
The field groups are created from the day one setting up the WPML Automatic Translation method and those field groups are set to translatable. This issue had occurred since December 2023. We have also noticed that "ACF-ML" feature has been added after updating the plugin.
We never had such issue earlier. We have the similar structure of separate custom fields for each languages on staging. Here we used same method for translating the data as live. We want it like earlier.
Hello There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Please be informed that providing support via calls falls outside our support capabilities. Our assistance is exclusively available through our online support platform. We appreciate your understanding on this matter.
I can understand your concern and agree that changing the field group translation preference will require lots of work. Given that you have already translated a substantial number of pages/posts with the field group set to "Translatable," it may be best to maintain this setting. If you switch the preference to "Translatable - Only show translated items," the field group will then be displayed exclusively in the respective languages.
Please feel free to let me know if you need any further clarification or assistance in this matter. I will be happy to help.
We have set the field group to "Translatable - Only show translated items" but still it is not working. We are not able to update or add content. The fields are not fetching updated content. I would request you to recheck the backend and let us know the solution. We already shared you the backend access details.
I tried to log in to your site using the credentials you've shared before but unfortunately, the login access is no longer working. Could you please check and share the credentials again?
I have enabled the private fields for you so that you can securely share the access information.
I hope this message finds you well. Thank you for sharing the access information, which has allowed for a thorough review of your current content translation setup.
In one of my responses(#15342128), I highlighted a crucial aspect concerning the translation preferences for the ACF Field Group post type. If the translation preference for the ACF Field Group post type is set to "Translatable", then you will need to manually(Using WordPress Editor) translate the page. If you try to add/update the Translation using WPML Translation Editor, the translated contents will not appear there as expected. For a comprehensive understanding of the manual translation process, please refer to the following guide: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/.
Upon further investigation, I noticed that the translation methodology for your pages varies; some have been translated manually, while others have used the WPML Translation Editor. An exemplar case is your Homepage, which was initially crafted in French and subsequently translated into English manually. After that, the default site language was changed to English.
Now, if you prefer to use the WPML Translation Editor for future translations, it is advisable to adjust the translation preference for the Field Group Post Type to "Not Translatable." This adjustment will allow you to translate content using WPML Translation Editor. It is also important to note that upon setting the ACF Field Group post type to "Not Translatable," and translating a page using the WPML Translation editor, all translated content is added within the main field group, not in the translated one. You can check the "WPML Test" page, where both main and translated field groups are visible, yet the translated content appears only within the main group.
Based on these findings, I recommend the following strategies:
1. For "Not Translatable" Preference:
- Both default and translated field groups will appear on all pages, enabling the use of the WPML Translation Editor for content translation. It is important to note that content translated via the WPML Editor will be added only to the default field group. You can remove the translated field group that doesn't have any content. For the contents that have been added manually in the Translated field group, please don't delete the Field group as you will lose the contents that you have added manually.
2. For "Translatable" Preference:
- Only the translated field group will be visible, but, you can only translate contents manually. If you use the WPML Translation Editor under this setting, the translated field group will not capture the translations, as field groups are treated as separate entities upon translation.
It is essential to weigh these options carefully and choose the one that best aligns with your workflow and content management practices. if you have any questions or require further assistance, please do not hesitate to reach out.
Best regards,
Prosenjit
The topic ‘[Closed] Content missing from backend fields’ is closed to new replies.
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.
