I'm using ACF and Advanced translation editor to translate those fields. The normal field groups are translating and showing on frontend and in page editor. But custom field group with Flexible content is not populating. The translations of the Flexible content field group are showing in Advanced Translation editor but not coming up on front end/edit page.
To resolve I've tried updating the original language page by making some minor edits and then updated the translation, but it's still not working for me.
Can you please help me to find a best way to use Advanced Translation Editor with ACF.
Welcome to the WPML support forum. When it comes to ACF fields, setting up translation preferences for each field could be tricky.
1.- For special fields like "Repeater" and "Flexible Content" the translation preferences should be "Copy".
2. Then subfields inside those repeater/flexible content fileds can be set as:
- "Translate" for all the fields you want to translate such as texts, WYSIWYG etc...
- "Copy" if you don't want to translate the field but keep the same value, for example for colors, true/false, images etc...
Also, not directly related to your question, but I've noticed your website has a low PHP memory allocation (40M). The minimum requirement for WPML is 128M but we recommend 256M:
- Access your server via FTP and open wp-config.php (in your WordPress root directory).
- Insert those lines just before /* That's all, stop editing! Happy blogging. */
For the fields, I've set it to the same field across all languages. To change the translation preferences, I can change the same field across all languages to the expert, right? Or I need to do it from settings? Once I change the preference, will it start working?
To sum up:
In "ACF > Field Groups" you can set for each individual group your multilingual option.
You have 3 options:
- Same fields (what most clients will use)
- Different fields (every specific cases or if you want to use the WordPress editor instead of our translation editor)
- Expert (To decide yourself the translation preference for each field)
I would recommend to start by "Same fields" as it will set the correct preferences in most cases. But then if you need to fine tune some preferences, you can switch to the Expert mode and make changes accordingly.
For example, "Same fields" will set all text fields as "Translatable" but maybe you want to "copy" one of those fields to keep the same value. Imagine for example a field with a person's name, the name is the same in al languages. No need to translate here, so you will set it as "Copy" instead of "Translate" in the Expert mode.
Once you're happy with all translation preferences, you can make a small edit in your original page (like adding a space at the end of the title) and resave. It should be enough to trigger the update on the translation. Then enter the translation and re-validate it.
It seems to be working now with Same fields. I've few other questions regarding the translations.
1. Is there any way to change language code from es to es-es? So that hidden link will be hidden link.
2. I've created an image upload field for the menu item. Before sometime, it allows me to upload new image for menu item. But now if I upload the image in menu item, it is not saving it. In the field group I've used the Same fields option.
1. The "language repertory" is based on the language code. Which is the identifier for that language in the database. So you shouldn't change it because you will lose your translation.
What you could do instead is create a new custom language that will use the language code "es-es" and duplicate all your "es" content to "es-es".
Any specific reason you want to change it? I ask because if you want to do this to specify to search engines that it's Spanish from Spain (localization), you can achieve that with the hreflang meta.
- Go to "WPML > Languages > Edit (link)"
- On the next page you will see that you can edit the hreflang column
You would recommend that only if you have several "locale" versions of Spanish: Spain and Mexico for example. Also, I'm not an SEO expert but I think it's recommended to keep a default "es" before adding any localization. So, in my example it would be "es" for Spain and "es-mx" for Mexico. Does that make sense?
2. As for the second issue, I'm not sure to understand. Could you please send me a video or some screenshots for better understanding? I personally use Loom for videos and it's free.
Thank you for explaining the language code. I initially wanted to use it in the URL, but as you recommend using "es," I'll keep it as is.
For the second issue, I've created an image field to add flags to the menu items. However, when I upload an image to that field and save the menu, it doesn't retain the image. It was working fine when I had only one language, English, but when I added other languages, the field stopped functioning. Any ideas on how to resolve this?
Below are a few screenshots for reference:
1. ACF field group page: hidden link
2. Menu page: hidden link
I would like to bring up another issue, and I apologize for the numerous questions. I am currently facing difficulties in translating content, as I have many pages that need to be translated into approximately 15 languages.
I have an image field under the Flexible Content, and I want it to be translatable for other languages. The translation preference is set to "translate," but I am still unable to modify the image. The same issue applies to text fields, as they are all in read-only format.
Please find below screenshots for reference:
1. Edit field group page: hidden link
2. English edit page: hidden link
3. English (Middle East) edit page: hidden link, hidden link
Please note that English is the main language, and all the fields in the English (Middle East) section appear to be greyed out in the WordPress Editor.
Thanks for all the details. At this stage I think it will be more efficient if I could have an admin access – preferably to a test site where the issue has been replicated – so I can further investigate.
I will activate a private field for your next answer where you can provide that information safely (this field is only visible by you and the support team). Don't share your own admin account, create a new one that you will delete when we finish troubleshooting.
IMPORTANT: Before we proceed, please backup your site and database.
---
Having said that let me give you some pointers here.
1. Depending of the way you translate your content, recommended translation preferences are different. You mentioned editing the translation in the WordPress editor. If you translate your content using the WordPress editor then, you need to set most (if not all) your fields as "Copy once" because you're not using WPML here.
As mentioned in my first answer "Different fields", would be the multilingual option when using the WP editor. And if you are in Expert mode, look at the third column (Different fields across languages) in this documentation: Ref: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/
2. Regarding images to be replaced/translated. Here you're uploading a file so the setting should be "Copy once" (see previous point)
Then you should use our add-on Media translation to translate the file by another file.
A. You can download id directly from your WPML account.
- Go to https://wpml.org/account/downloads/
- Click on "Download WPML manually" to see all plugins and download them
- In your WP dashboard, go to "Plugins > Add new" and use the button at the top of your screen to upload the .zip file
B. Then go to "WPML > Media Translation"
C. Locate the image you want to “translate” and click the pencil icon under the language you want to use a different image for.
D. Upload a different image and click on the Save media translation button.
Ref: hidden link
3. Regarding the Menu Options, I have to be honest. It seems to be a new option from ACF and that's one of the reasons why I'd like to get access, to make sure I understand how it works.
Thanks for the access. I will look at the menu options and get back to you in a moment.
In the meantime I can already recommend you the following for your workflow:
1. I would not use the "Duplication" feature, instead you can set the translation preference to "Translatable - use translation if available or fallback to default language" for your post types (posts, pages...).
- Go to "WPML > Settings > Post Types Translation".
Why?
As you can read here: https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/
- Duplication is more for content that you don't want to translate and want to keep always in sync with the original language (for example legal pages).
- Plus, duplication works with the native WordPress editor, while automatic translation works with our Advanced Translation Editor (ATE).
2. We have different revision options for automatic translations:
- Review the translations before publishing (recommended)
- Publish translations and review them later (good for when you’re publishing a lot of content and can’t review in real time)
- Publish translations without reviewing (your translations may have some inaccuracies)
Ref: https://wpml.org/documentation/automatic-translation/how-to-review-automatic-translations-on-your-site/
2. When I go to "ACF > Field Groups > Menu Options" I can see that the translation preference is still "Translate". It should be:
- "Copy" if you want to keep the same image
- "Copy once" if you want to be able to translate it (replace the image) using Media translation.
Last, I noticed that the rules are applied to specific menus, if I add the FR version of your primary menu, I can see the custom field in "Appearance > Menus".
I can change the translation preference to 'Copy,' but will it allow us to save an image for a menu item? I have applied rules for specific menus to show that field on those menu items.
Regarding the recommendation to set the post type as translatable, we don't want users to be redirected to the English page if a particular post is not found. Some pages will be exact translations of the main page, while others will be completely separate from the main language pages.
Have you found out why some fields are in readonly mode even if I have set them to translate?
Unfortunately we don't offer support via phone calls. I would recommend to create a video to explain exactly the issues you're facing. I personally use loom for less than 5 min videos. But you can use any software to create your video. You can even send me a link to a Gdrive/WeTransfer link to a MP4 to download.
I'll reply with a video, that way it will be more like a conversation.
Now regarding the custom fields translation preferences.
I know it can be confusing so let me go step by step:
First the translation method will determine the translation preferences.
1.
- Here from your screenshot it seems that you're translating your content in the WordPress native editor.
- In that case you should use the multilingual mode "Different fields" or if you are in "Expert mode", set all fields to "Copy once". because when using the WP native editor, WPML is deactivated.
2. If you use our Advanced Translation Editor (ATE) to translate your content, then do not enter the WP native editor to make changes. Do all you changes in our editor. Switching editors an cause some issues and you may lose your translations.
I'll wait for the video to fully understand you workflow and what you want to accomplish before sending you clearer information/recommandations on how to proceed.
Apologies for the delay. I've successfully resolved the translation problem I was encountering and can now translate the pages as intended. The only outstanding issue is that the flags are not being saved in the menu item ACF field. Have you had an opportunity to investigate this?
Additionally, could you please provide guidance on how to rectify "This site has moved to a new location" error on the development site? When I select "Yes, move back here," it generates the same error on the live site, and when I select it on the live site, it disrupts the functionality on the development site.
1. hidden link
2. hidden link
Thanks
The topic ‘[Closed] ACF fields are translated in translation editor but not reflecting on front end’ 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.
