Open beta2k opened 4 years ago
Use q-translate-xt rather then this old plugin.
The new version of this plugin q-translate-xt includes this plugin "acf-qtranslate".
thanks, just read about qTranslate-XT. I will use it asap. The thing is, that my website is productive already and it is for an event that is starting in one month. I think migrating to the new plugin right now, might not be the best idea, or what do you think? is it possible to migrate and what adaptions would I have to make to the custom field WYSIWG editor?
I have been testing this solution for some time and have also implemented it on production versions of websites. Everything works great.
In my opinion, there is no point in waiting. Q-translate-X has not been updated for over 2 years.
In addition, a big update XT version 3.6.3 came out yesterday which solves a multitude of problems.
Good luck :)
Custom fields WYSWIG works like a charm on my sites.
on your sites with XT you mean?
If I migrate, do I need to change anything with the WYSWIG fields? I now have a custom post type with a custom field that uses the WYSIWG (qtranslate) editor. Do I need to change something there?
Yes, XT.
I didn't have to change anything in the ACF fields. Everything worked fine.
but i have to disable the qtranslate-x and acf: qtranslate plugins right?
Yes, you need only "q-translate-xt".
Turn off "q-translate-x" and "acf-qtranslate" plugins.
turned out it is/was an issue with TinyMCE: https://support.advancedcustomfields.com/forums/topic/5-8-strips-paragraph-tags-from-wysiwyg-field/
I use:
When I use the visual editor of the WYSIWG (qtranslate) field, the paragraphs get removed. When I edit directly via HTML (text mode) the paragraphs are not removed. Please help how this can be fixed.