QTranslateX and Visual Composer

Hello, all: I was told that there is a ticket at Visual Composer support to enable compatibility with qTranslate-X, like they previously did with original qTranslate. I decided to drop a note here to encourage you to contact them with this issue. The more people complain, the quicker they will update it. You may also mention to them, that the qTranslate Team is ready to cooperate with them, if they have any questions: https://qtranslatexteam.wordpress.com/contact-us/

I contacted them (WP Bakery) with a new support ticket. The response I received from the VC support dept was: “We had recently added a compatibility fix for qtranslateX which allowed both the plugins to be used simultaneously. Can you please share the login credentials and the login url so we can take a deeper look at it?
It is great that the developer is ready to work with our team and I am sure this will make life much easier for the users who are using both the plugins.”

I have given them the credentials to one of my sites to explore, but if you want to provide more details, let me know and I will update my support ticket.

So this is the latest news from VC. They are convinced it works fine. On the web site I gave them to play with, they were able to add text, modify and update pages without problem. When I then tried, it did not work.

I decided to try another browser (I am using FF 36.0.4/ Win8). I edited a page with Chrome – and guess what? It worked fine! I then tried IE, and it’s a no go. So Chrome seems to be fine, FF and IE do not work.

Can anyone else verify this finding?

@tfagen: could you publish the version number of VC, which is compatible? It would be also nice if you could share it with us: qtranslateteam a t gm ail d c om. We do not need the license key, just the zip file with the code itself.

The VC version 4.4.3 seems to work fine in chrome browser. Also need to enable the legacy switch, “Compatibility Functions”, in qTranslate-X.

We work on a better design of integration interface, which will make it easier for other plugins to integrate.

Can somebody please explain to me what the big deal is? It (4.4.3) works perfectly fine with the last version of mqtranslate. Why isn’t it possible for qTranslate-X to use the solution which mqtranslate has used?

@solojuve1897: mqTranslate has not used any solution, they did not do anything special to make it work, but VC adjusted their plugin to use with mqTranslate. Now they have adjusted it to use with qTranslate-X, which uses a completely different java script. If it was up to us, it would have been done long time ago.

@john Clause: It should be working fine now? It isn’t working for me. I have version 4.4.3 of VC and the latest of qTranslate-X. When trying to update a change made in a page, nothing happens. It just goes back to the configuration before the update. The same procedure works with mqtranslate. Have I missed something?

@solojuve1897 – what browser are you using? Did you try using Chrome? It’s the only one that works for me.

@tfagen Yes, I use only Chrome. Do I need to do something special? I tried activating compatibility functions, but it didn’t help either. I simply can’t get the changes I make to stick with qTranslate-X. If I understood you correctly, you can? It works with mqtranslate though. What version of VC are you using?

I am using 4.4.3 of VC and Version 3.2.9 of qTranslate-X on 2 sites.
I also have Version Version 4.3.5 of VC with Version 3.2.9 of qTranslate-X working fine on another site.

In all cases, they only allow Updates to VC pages when I am using Chrome browser. I am currently using Version 41.0.2272.118 m of Chrome under Win 8.1.

I had an issue with Compatibility functions at one point, but I think it was a caching problem. After you enable it, delete your site cache and browser cache and see if that helps.

@tfagen: I will try your suggestions and report back how it goes. I’m very happy to hear that it in fact should work with certain circumstances.

Actually, VC 4.4.3 does not work for me either on the latest alpha q-X from GitHub. I mean, it does not respond to Language Switching Buttons, but it saves changes ok if I do not switch edit language or use “Single Language Mode” for option “Editor Mode”. It works as expected under version 3.3 without custom integration: https://qtranslatexteam.wordpress.com/2015/03/30/release-notes-3-3/ (this is a draft of release notes).

I also searched their code for any traces of qtranslate-x and came out with nothing. They have separate classes dedicated to qTranslate and to mqTranslate though. So, I am not sure what is going on. I will probably try to make it work with modifications of their code and let them know what changes are required. If somebody can also try to figure it out, I would appreciate a lot sharing of the observations.

Hi All, @solojuve1897, @tfagen, @kerfro, @rreisdasilvagmailcom, @kainer, @johnymas, @silu44, @alexgontcharov, @mix999, @nicolecurioni, @masterbip, @mpbm23, @infprt, @yonahbasic, @xtof_r, @meyerovb:

Could you please try the latest version from GitHub, which you can download with ‘Download ZIP’ button on GitHub page or get a specific pre-relese 3.2.9.8.9 here for the sake of convenience?

It has experimental Visual Composer support. One thing I have just discovered myself, that VC frontend editor uses user front-end language, instead of admin edit language, otherwise it works for me so far. How many of you really use VC Frontend editor? As to me it is a real overkill, people would not bother to use, but I might be mistaking. Please, share with me how you use VC.

I know some designer that uses visual composer but none uses frontend editor. I used it once, no more.

Thanks for the experimental version. I will try to take a look and let you know.