Source evidence

Can’t translate custom fields

ACF qTranslate · support · 2017-06-06T09:38:00+00:00

ACF qTranslate plugin evidence original source source API

complaintsentiment

mediumseverity

0.86relevance

5replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 31 rows with source links

16.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

MagineM unresolved

Hi, I’ve got this plugin installed and the only thing I seem to be able to translate is the field group title. I can’t translate any of the individual custom field titles or select fields etc. The text/test area fields I can translate when editing my post. UPDATE – ADDITIONAL ISSUE: It seems that my normal text fields etc. also only translate once. If I edit my post and update a second time, all the the custom translated fields default back to my main language. Hi, You have to go to settings -> ACF qTranslate and check the boxes and save. For me it worked, I hope you too. Hi, Those boxes are checked UPDATE: So the text fields etc. translate, but after saving, the field content defaults to the primary language content. The translated content will show on the site when viewing but the minute that post is saved again it overwrites all the translated content with the original. UPDATE: The issue above appears to be an issue when using the WYSIWYG field. When using the textarea etc. the translation sticks and doesn’t get overwritten. I assume this is some tinyMCE issue… I am using TinyMCE Advanced, but even when deactivating the plugin it doesn’t seem to make a difference. I’ve also managed to translate the titles through the templates using the esc_html_e syntax.

Commercial Context

Opportunity

agency visual QA and update safety

ACF visual QA and update safety for preventing client-site regressions before updates or edits go live

Buyer: site builders and agencies

Wedge: detect ACF layout regressions, widget breakage, and client-visible update issues

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Can’t translate custom fields: users show bugs, missing feature, setup pain that may indicate a product gap.

Evidence quote: Can’t translate custom fields Hi, I’ve got this plugin installed and the only thing I seem to be able to translate is the field group title.

Affected feature: translation

bugs missing feature setup value

Plugin

API

ACF qTranslate

8.0K active installs · 184.0K downloads · rating 90.0

acf add on admin advanced custom fields qtranslate

Comments

5 shown

MagineM 2017-06-06T09:48:00+00:00

UPDATE – ADDITIONAL ISSUE: It seems that my normal text fields etc. also only translate once. If I edit my post and update a second time, all the the custom translated fields default back to my main language.

tamarazambrana 2017-06-06T10:00:00+00:00

Hi, You have to go to settings -> ACF qTranslate and check the boxes and save. For me it worked, I hope you too.

MagineM 2017-06-06T10:58:00+00:00

Hi, Those boxes are checked

MagineM 2017-06-06T14:01:00+00:00

UPDATE: So the text fields etc. translate, but after saving, the field content defaults to the primary language content. The translated content will show on the site when viewing but the minute that post is saved again it overwrites all the translated content with the original.

MagineM 2017-06-07T08:01:00+00:00

UPDATE: The issue above appears to be an issue when using the WYSIWYG field. When using the textarea etc. the translation sticks and doesn’t get overwritten. I assume this is some tinyMCE issue… I am using TinyMCE Advanced, but even when deactivating the plugin it doesn’t seem to make a difference. I’ve also managed to translate the titles through the templates using the esc_html_e syntax.