QTranslateX and Visual Composer

  • Resolved R

    (@rreisdasilvagmailcom)


    9 years, 10 months ago

    Hi guys,

    First of all great plugin!

    I have a problem however. The plugin is having problems with Visual Composer. Once I add content to any page in another language and update the page the content resets to the initial language.

    I can’t also modify anything else on any page or modify any content when QTranslate X is active. No change is saved.

    Is there anything you can tell me to help me solve this?

    Regards,
    Ricardo

    https://www.ads-software.com/plugins/qtranslate-x/

Viewing 15 replies - 46 through 60 (of 69 total)

  • @john Clause

    I don’t care about VC Frontend editor.

    For me this works absolutely great. Will this be the new qtranslate-x version?

    Plugin Author John Clause

    (@johnclause)

    Will this be the new qtranslate-x version

    That is the plan – will go to release 3.3. If VC finishes its own internal integration, there is an option “3rd-party plugins” under section “Custom Integration”, where one can turn off this partial built-in VC integration in order not to interfere with the proper full-featured VC integration.

    We also work on a general simplified way to integrate the 3rd-party plugins. Hopefully, it will be finalized in 3.4. Any suggestion on design of 3rd-party integration are welcome. The best way to submit your thoughts is GitHub.

    I tried it with my site and, unfortunately, I am still experiencing issues:

    When I use language tags in the the “Editor Raw Mode” the translation works well at first. When I then try to edit the translation and open a text block in VC the language tag disappear from the editable text although they are still visible in the non-editable field that displays the content.

    Let me know if this is clear – otherwise I will send you some screenshots.

    Cheers!

    Plugin Author John Clause

    (@johnclause)

    @kerfro: wow, raw mode with VC – that is an usual combination, I would think. This then has nothing to do with the integration done so far, which is not applicable to raw mode.

    It looks like VC specifically removes [:xx] tags. I am not sure why they would do so. Will research more. If anyone finds something out, please do not forget to share.

    ??
    This way I don’t have to think about applying changes to language versions. Otherwise changes in pic etc. don’t automatically show in all language versions.

    Agreed, raw mode is my preferred method. Luckily divi composer doesn’t have any problems with it

    Hey, I really appreciate the effort that the you are making to solve this issue. I have tested latest versions but they aren′t working:( I think that raw mode is useless for basic admin users (maybe clients), they don′t even know what a shortcode is. I will keep track of this thread to know what is going on. Thanks for everything

    Plugin Author John Clause

    (@johnclause)

    @meyerovb: what is divi composer? Could you give a link?

    @bensita: “they aren′t working” – what exactly not working? Could you describe the steps to reproduce what you observe as not working?

    Divi is elegent themes flagship theme with built in visual composer. They also have a stand alone composer plugin

    @john Clause

    I have encountered a bug. Try modifying a Grid Element (with the purpose of for example having different button titles according to the selected language) while having several languages and qTranslate-X activated. The end result, on the front, is very strange. In my example:

    I have a bi-lingual page with the Post Grid element added to the page. I have chosen “Basic grid: Default” as Grid element template, but have modified it so that the Button title is different according to the language. The result is a mess.

    Plugin Author John Clause

    (@johnclause)

    Hi All, we decided to create a separate plugin “WPBakery Visual Composer & qTranslate-X” instead of having an option under q-X, which does not really belong there. This will eventually become another example of integrating plugin for everybody to follow.

    Could you please try it with the latest alpha pre-release https://github.com/qTranslate-Team/qtranslate-x/archive/3.2.9.9.4.zip?

    @kerfro: raw editor mode now works for me too, does it work for you?

    Front-end also worked for me in my simple testing.

    @bensita: I still do not know what you meant. Are you talking about “WPBakery Visual Composer” or maybe some other Visual Composer?

    Hi everybody.

    I don’t know what is new in this new plugin but it works for me like a charm.

    Sadly not working with plugin “Page Builder by SiteOrigin”

    Hi John,

    also works in this constellation:
    – qtranslate 3.2.9.9.4
    – Advanced Custom Fields 4.4.1
    – WPBakery Visual Composer & qTranslate-X

    My problem was I could not save the content in my custom field (advanced custom field).
    I’d recommend to publish the alpha soon as it offers some nice features.

    thanks!

    Hi John,

    Seems to work well in raw mode. Thanks!

    Only caviat: When scrolling in my second language some of the text disappears – https://gyazo.com/8481c55ffa3aafa708223c49d4d7a622

    It doesn’t do that in English – I have no knowledge of programming so I am clueless as to why this is happening. It is not a major issue though.

    Cheers, Kerstin

Viewing 15 replies - 46 through 60 (of 69 total)
  • The topic ‘QTranslateX and Visual Composer’ is closed to new replies.