Polylang + Deepl => translation of acf fields
-
Hello everyone,
I recently discovered that Polylang had a deepl integration option that allows for automatic translation of pages and posts.
I tested this option and got great results for blog posts with a lot of content but unfortunately i discovered that the acf blocks content wasn’t translated, maybe i’m in the wrong there but I thought those blocks were going to be translated as well. I’m not talking about the fields label but the value contained inside those fields.
For example a text field called “title” with the value “A single post” will remain unchanged upon translation, where i expected the result to be a field called “title” with “Un article unique” for a french translation of this post.
Could someone confirm that those ACF fields won’t be translated ? If not i’d love to find a procedure that would allow that if it exists, i already followed those steps https://polylang.pro/doc/working-with-acf-pro/ to try and translate the whole page.
Thank you for your time and i hope you have a fantastic day.
WP version : 6.6.1
Polylang version : 3.6.3
ACF Pro : 6.3.6
Deepl integration : free version (plenty of free characters remaining)
-
Had the same problem. You need to edit the acf field group while polylang is active and you will see a translation setting in each of your fields. you need to set any desired field to “translate” or “sync” in order to make them available for machine translation.
It’s not documented by polylang in regards of deepl but here is described what I mentioned above (headline 3.1) https://polylang.pro/doc/working-with-acf-pro/#customize-acf-fields
edit: I’m using classic editor, not the block editor. The document (from 2020) says “It does not work yet for options pages and ACF blocks (this is planned for a future version).” So maybe it just doesn’t work for your use case, but I can’t confirm or deny that
- The topic ‘Polylang + Deepl => translation of acf fields’ is closed to new replies.
