• Resolved uptoeleven

    (@uptoelevengmailcom)


    The problem I am having is with the Types plugin’s WYSIWYG custom fields, but it would be with any plugin that generates WYSIWYG textareas – they will break with qtranslate.

    Qtranslate’s php code is pretty dilligent about only modifying the textarea that contains the content, in the qtranslate_wphacks.php file. However if you have plugins that generate additional WYSIWYG fields, if they aren’t qtranslatified (adding the extra language tabs) then there is a problem. Qtranslate modifies TinyMCE so that it saves the content when you click between language tabs (as it must) – but if your TinyMCE box doesn’t have language tabs (because it’s not Qtranslatified) then the HTML/Visual tabs break.

    The plugin dies, client-side, on the code generated by qtranslate_javascript.php lines 349 – 373
    $q_config[‘js’][‘qtrans_switch’] = “
    switchEditors.go = function(id, lang) {
    // the code where qtranslate is over-riding TinyMCE
    // update merged content
    if(inst && ! inst.isHidden()) {
    tinyMCE.triggerSave();
    } else {
    qtrans_save(vta.value);
    }

    vta is null because the TinyMCE code hasn’t been qtranslatified because it is generated, dynamically, after the page has rendered.

    Any idea how we can maintain the TinyMCE code for those blocks that don’t get modified by qtranslate?

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Same problem here ??

    Current set-up:

    WP 3.4.1
    qTranslate 2.5.31
    ACF 3.3.9
    WP e-Commerce 3.8.8.5

    Thread Starter uptoeleven

    (@uptoelevengmailcom)

    OK – really this is a problem for qtranslate, I was given a solution by the Types people which involves modifying qtranslate… but really qtranslate need to get their act together and incorporate the solution into their own code. It is really irresponsible to write a plugin which renders WordPress unusable, and this is precisely what qtranslate’s hijack does.

    And the workaround is easy.

    https://www.qianqin.de/qtranslate/forum/viewtopic.php?f=3&t=3497

    10 second hotfix – not a fix just ignores the problem…

    In the qtranslate_wphacks.php change this

    if(inst && ! inst.isHidden()) {
    				tinyMCE.triggerSave();
    			} else {
    				qtrans_save(vta.value);
    			}

    to this

    if(inst && ! inst.isHidden()) {
    				tinyMCE.triggerSave();
    			} else if(vta){
    				qtrans_save(vta.value);
    			} else {
     				return;
    			}

    Sorry guys!!! Ignore my last post!!! I posted on an outdated page and had not seen the solution posted by uptoeleven…

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘qtranslate with other plugins that generate TinyMCE blocks’ is closed to new replies.