Background of the issue:
I'm trying to make my custom ACF blocks translatable. I have several custom blocks created with Advanced Custom Fields, and I want to be able to translate their content using WPML. I have been referring to the general WPML and ACF documentation and understood from previous support tickets that I needed to set a translation method to make the fields appear.
Symptoms:
When I go to the WPML Translation Editor, the fields from these blocks are not appearing, making it impossible to translate them. The only ACF fields I can see are those associated with posts and custom post types.
Questions:
How can I make my custom ACF blocks appear in the WPML Translation Editor?
Is there a specific setting or method I need to follow to make ACF block fields translatable?
I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)
**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **
I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.
NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.
1. Added a page called WPML Test and added a block /banniere LV
2. Filled out the Title, subtitle and text
3. The fields are not pulled in the ATE editor, but the content is pulled into the secondary language.
I can confirm that the Bannière field group items are indeed set to 'translate'.
Workaround:
Go to pages -> edit the page in the default language
Use the language switcher (exit guttenberg full screen mode) and switch to the translation language.
Manually edit the block content
This will allow you to manually edit the fields.
See example here: hidden link
Regarding the issue of the fields not pulling into the ATE editor, are you possibly using the same field names for another field in another field group that has a different translation setting?
Thank you for your assistance.
However, the proposed workaround is not a viable solution for our needs, as it would be significantly more time-consuming than the expected functionality of translating words directly.
We have numerous pages that require bulk translation, and it's essential that ACF Fields are included in this process. We're looking for a solution that can efficiently handle our large-scale translation requirements while maintaining the integrity of our ACF content.
I understand, were you able to review my question at the end of the last thread?
"Regarding the issue of the fields not pulling into the ATE editor, are you possibly using the same field names for another field in another field group that has a different translation setting?"
There is a chance that you are using the same field names in another field group causing this issue.
I followed your suggestion. First, I deleted every field group except "Bannière". Then, I created a new page, cleared the WPML cache, and filled in the inputs. However, I'm still experiencing the same issue: the fields are not appearing in the translation editor.
Hi !
They are registered using acf-json folder inside the theme.
I also have a problem with links, there is no longer an automatic translation of links to posts that have an english and french version, I don't know if this should be in another ticket.
The topic ‘[Closed] ACF Blocks not appearing in WPML’s Translation Editor’ 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.
