Here is some context information. We are using the Flexible Content field in combination with all different kind of field such as repeaters, groups, etc. With this setup we created a very basic ‘Page Builder’.
Making this setup multilingual is giving us many problems and we are curious what your experience is with this. I don’t think we are the first doing this, I guess there is a solution.
As you know, fields need to be set to copy/copy once/do noting/translateble.
This needs to be set on a field by field basis. To streamline this process we can set up fields in the wpml-config.xml with these settings predefined. This also has to be on a field-by-field basis but at least you have to do it only once. Repeater/flex fields on the other hand can’t be set this way and every new instance of a flex/repeater field has to be toggled to be translateble as well.
Hi There, not really. ACF Custom fields are really a mess with WPML in my opinion. But recently we switched over to native gutenburg blocks and WPML and Gutenburg blocks work way better than our old setup….
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
ACF PRO’s Flexible Content field allows you to create smaller pieces of UI and compose them into whole flexible patterns. In our latest article, we show how to use it to create swappable site sections and integrate it all in a theme.https://t.co/ZRocH8oJSp