I see the exact same problem. A fix would be great.
@r: what is great about the plugin, if what you describe makes it unusable? 🙂
Thank you though for the supportive words.
There are too many hits on “Visual Composer” in search. Please, give me link the plugin with “Visual Composer”, which you mean.
Aslo, you may try the latest ‘stable’ from git: https://github.com/qTranslate-Team/qtranslate-x/archive/2.9.8.5.zip
Do not take the very latest, 2.9.8.6, it has problems, which are being resolved now.
http://vc.wpbakery.com/
Thanks. I have tested the newest version from Github, but it is not working.
Visual composer is included in a lot of themes and the theme author from the theme I am using currently guarantees it is working with qtranslate and mqtranslate. He said he could not test against all available forks.
It would help if you could give us a copy of this plugin to test: qtranslateteam at gm ail d com.
For now, this goes into “Known Issues”:
If other plugin installs a custom TinyMCE editor on a translatable field served by qTranslate-X, then all kind of problems start to happen. Examples of ‘offending’ plugins are: Fusion Page Builder, Page Builder by SiteOrigin, Rich Text Tags, Visual Composer, WP Editor.
We are looking into possibilities to enable integration with those plugins.
Hi John, I’ve sent you a copy to check out. Would be nice to get it work, else I have to choose another language plugin. People love using things like visual composer. Every client asks for this.
Thank you, @kainer, we will be working on it shortly.
Hi folks,
Just wanted to let you guys know that using the previous version (2.9.8.5) (not x.x.x.6) seems to have sorted out the editor display bug (on default WYSIWIG editor) I was experiencing.
Thanks John !
Version 3.0 in combination with visual composer is still buggy. Things I change are not saved when qtranslate-x is active. Not possible to work with it currently.
Hopefully this is fixed soon as I have to work on my page translation.
@lavenpillay: thank you for encouraging words. I assume it is also ok in the latest release 3.0, is that true?
@kainer: nothing was done yet to fix the issue with Visual Composer. The only workaround now is to deactivate it. Sorry, that is on todo list and will take a bit longer.
I thought I’d weigh in on the Visual Composer issue and qtranslate-x. Firstly, I like the ease of adding a language menu item and the widget works great too. Now if you can fix the Visual Composer issue, I’d even pay for this plugin!
The only way I have found to edit or add new text for other languages is to deactivate qtranslate-x, then activate mqtranslate, do the edit, then deactivate mqtranslate and activate qtranslate-x.
To prevent surfers from seeing this while I’m editing, I put the site into maintenance mode.
still doesn’t work with TinyMCE editor. I switched back to mqtranslate.
qtranslate-x challenge is to work with page builder like visual composer and other plugins
Alex
(@alexgontcharov)
I am using the latest qTranslate-X 3.1
Issues with standard visual editor.
I edit content on both languages and switching between them during editing.
Very often all content just disappear… for both languages.
The only workaround – do not use editor in WordPress.
Edit in external app, then copy paste and quickly save.
Hope this can be fixed soon.
I have the same issue. I installed visual composer like silu44 suggest and problem wasn’t solved. Content disappeares all the time and then you can’t save content at all.
