Open adamlindqvist opened 9 years ago
I am currently working on WordPress 4.3 + qTranslate-X + ACF + ACF-qTranslate and they seem to work for some extent. Currently my only concern is that it does not seem to support translation on Image field. By the way, could there be some plugin conflict in your case?
I havent tried the Image Field so far, so the only one I've been experiencing issues with is the WYSIWYG field.
I doubt there is a plugin conflict for me since apart from qTranslate-x, ACF and ACF-qTranslate I'm only using a twitter feed plugin and custom post type UI.
In my tests everything works fine with WP 4.3, qtranslate-x 3.4.3 and acf pro 5.3.0
However, after updating wp 4.3, acf-qtranslate throw a notice (saving field work anyway):
wp_richedit_pre is deprecated since version 4.3! Use format_for_editor () instead.
in fact there was some problem, try this fix: https://github.com/funkjedi/acf-qtranslate/pull/50 (I could not try ACF4 only PRO version)
Also tested with ACF4: https://github.com/fburatti/acf-qtranslate/commit/2e4a9e6dc97894cefae26019067ccbce9d35344a You must use the acf-qtranslate WYSYWYG field and disable the "translation for Standard Field Types" option.
WordPress 4.3.1 qTranslate-X Version 3.4.4 Advanced Custom Fields 4.4.3 Advanced Custom Fields: qTranslate 1.7.9
still have issues with qTranslate wysywyg fields
@Liscus you tried this? https://github.com/fburatti/acf-qtranslate
@fburatti thank you! the #50 worked for me. I had the problem that formatting in the WYSIWYG fields would not save, and changes in the content would be applied to all languages. this fix fixed both issues. I think the WYSIWYG should probably go out since qtranslate x already takes care of that, no?
At last!!! Thank you! This solution helped to me (;
Using https://github.com/fburatti/acf-qtranslate try to disable and enable qtranslate-x. Then go to settings -> languages -> integration and click save changes. Go to settings -> acf qtranslate and make sure none of the options is selected. In ACF filed-groups make sure to use the ACF qtranslate wysiwyg field instead of ACF standard field. Please try again!
fburatti, thanx, this work
@fburatti: thanks for your patch, it works. The only annoying thing is that this comes up as version 1.7.8 (that's the version number in the code, although the readme says it's 1.7.9) and the most recent version of the plugin on wordpress.org has the version number 1.7.9. For this reason, my wordpress keeps notifying me that the plugin should be updated. Any chance you can get the plugin author to include your changes and generate a new version?
@fburatti: Any idea why my wordpres 4.3. 1 with ACF 4.4.5 and ACF qtranslate 1.7.9 and qTranslate-X 3.4.6.4 is not working with the ACF WYSIWYG-Editor or the ACF qtranslate WYSIWYG-Editor. Thanks
WYSIWYG is not translating for:
WP v4.5.4 ACF:qtranslatex v1.7.9 ACF v4.4.7 qTranslateX v3.4.6.8
Any idea how to fix it?
I have a big problem fields duplicate content in both languages, ...any hint?
I have the same problem, the text is duplicated in editor. Help to correct the problem.
hello guys finally i found the solution 1-in advanced custom field you want to change field to this look in picture and you will know every things
Just add this in your theme functions.php file
function override_mce_options($initArray){ $initArray["selector"] = "#content, textarea[id*=wysiwyg-acf]"; return $initArray; } add_filter('tiny_mce_before_init', 'override_mce_options');
I've tested a few of the ACF fields and the WYSIWYG is not possible to translate!