Skip to content
This repository has been archived by the owner on Dec 16, 2023. It is now read-only.

Not parsing existing fields with qtranslate-x #35

Closed
loganyott opened this issue May 19, 2015 · 1 comment
Closed

Not parsing existing fields with qtranslate-x #35

loganyott opened this issue May 19, 2015 · 1 comment

Comments

@loganyott
Copy link
Contributor

Greetings!

I am using the following:
acf-qtranslate v1.7.9
advanced-custom-fields v 4.4.1
qtranslate-x v3.3

Most fields seem to work fine. My main problem is the wysiwyg field.

If I use the "standard" field translation, the WYSIWYG field is loaded with the content from the current language, but no others. Switching the language works, but all languages are defaulted to whatever the language is when I load the page. Example: If I load the page in English, the english field value is used for all languages. If I load in chinese, chinese field value is used for all languages.

If I don't use the "standard" field translation and add the language tabs, I get all languages displayed in the wysiwyg field. If I add the content and switch the language tab, it transfers the new content correctly. However, existing content for all languages is loaded in every languages box.

Have you seen an issue like this or any ideas on where I should debug first? If it helps, I semi-recently migrated from mqtranslate to qtranslate-x, so these fields are currently stored with <!--:--> tags instead of the new [:].

Thanks!

@Tusko
Copy link
Contributor

Tusko commented Jun 12, 2015

https://goo.gl/yx1Z3r
this works fine

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants