Navigation überspringen

Dieses Thema ist gelöst. Hier finden Sie eine Beschreibung des Problems und der Lösung.

Problem:
You are trying to translate ACF blocks with textarea fields named 'text' that are set to 'translate'. However, when you send a page with these blocks to the Advanced Translation Editor (ATE), the fields named 'text' do not appear for translation.
Solution:
This behavior is expected and works similarly to how internal links are handled. You can still locate these entries using the search function in the Advanced Translation Editor and translate them from there. For more details, please refer to this guide: https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/

If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.

Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.

Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.

Schlagwörter: 

Dieses Thema enthält 3 Antworten, hat 1 Stimme.

Zuletzt aktualisiert von Marcel Vor 3 Wochen, 5 Tage.

Assistiert von: Marcel.

Autor Beiträge
Mai 21, 2025 um 6:35 am #17055198

montagmorgens

Hintergrund des Themas:
I am trying to translate ACF blocks with textarea fields named 'text' that are set to 'translate'. When I send a page with these blocks to the Advanced Translation Editor (ATE), I expect all fields set to 'translate' to appear for translation.

Die Symptome:
Fields named 'text' do not show up in the ATE, even though they are set to 'translate'.

Fragen:
Why do ACF fields named 'text' not appear in the ATE for translation?
How can I ensure all fields set to 'translate' show up in the ATE?

Mai 21, 2025 um 7:31 am #17055353

Bruno Kos
WPML-Unterstützer seit 12/2018

Sprachen: Englisch (English ) Deutsch (Deutsch ) Französisch (Français )

Zeitzone: Europe/Zagreb (GMT+02:00)

Could you please upload soe of these ACF field groups to the sandbox below?

versteckter Link
(ACF is already installed)

Specifically:

- One field group where a title field (Field Name: title) works as expected in the ATE
- One with a text field where it does not show in ATE

This will help us reproduce the issue.

Mai 21, 2025 um 8:23 am #17055715

montagmorgens

Hi Bruno, I uploaded one field group where the title works for us but the text field not.

Btw – in our test install, I changed all "text" field names to "text_content", now everythign works as expected.

But I found another issue while testing: When I just enter a single digit (e.g. 1) in a text field, it will not show up in the ATE, either.

Mai 22, 2025 um 3:38 pm #17062825

Marcel
Unterstützer

Sprachen: Englisch (English ) Spanisch (Español ) Deutsch (Deutsch )

Zeitzone: Europe/Madrid (GMT+02:00)

Hi,

thanks for the info.

But I found another issue while testing: When I just enter a single digit (e.g. 1) in a text field, it will not show up in the ATE, either.

This behavior is expected and works the same way as with internal links. You can still locate these entries using the search function in the Advanced Translation Editor and translate them from there. For more details, please refer to this guide: https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/

Best Regards,
Marcel