meyerovb
Forum Replies Created
-
Forum: Plugins
In reply to: [qTranslate X] QTranslateX and Visual ComposerDivi is elegent themes flagship theme with built in visual composer. They also have a stand alone composer plugin
Forum: Plugins
In reply to: [qTranslate X] QTranslateX and Visual ComposerAgreed, raw mode is my preferred method. Luckily divi composer doesn’t have any problems with it
Forum: Plugins
In reply to: [W3 Total Cache] Add defer to footer scriptsNevermind, google page speed doesn’t seem to care
Forum: Themes and Templates
In reply to: Move all footer scripts to headerForum: Plugins
In reply to: [qTranslate X] QTranslateX and Visual ComposerPlease reference this ticket: https://ww.wp.xz.cn/support/topic/option-to-keep-plugin-enabled-but-disable-editor-language-switching
Enabling raw mode and using short codes ([:en]abc[:fr]xyz[:]) will allow you to use visual composer, as well as to only need to maintain a single version of each page.
Props, divi page builder now works, you should modify the note about custom tinymce on https://qtranslatexteam.wordpress.com/known-issues/, you can add this workaround, and also add elegentthemes page builder and the divi theme to the list that break if you don’t use the workaround. Honestly, my opinion is this should be the default mode 🙂
Forum: Plugins
In reply to: q translate x – problems switching and editing the multilingual TextsHere’s a workaround: whenever you need to modify anything in page builder disable the plugin, in the pagebuilder text area use the shortcodes ( [:en]abc[:fr]xyz[:] ), then save the pagebuilder and re-enable the plugin. With the plugin enabled u can’t even save page builder properly, but if u disable it while you edit your data and then re-enable it, it will (annoyingly) work.