WordPress.org

Forums

mqTranslate
Problem using mqTranslate, WP 3.9 and Advanced Custom Fields (19 posts)

  1. Bjoernobaert
    Member
    Posted 1 year ago #

    Hi!

    I've got some problems using this plugin together with ACF. It worked on older WordPress versions with qtranslate, then I updated to WP 3.9 and switched to mqtranslate, and now the WYSIWYG Editor is not working properly anymore. It doesn't show the Quicktag Bar and I can't switch between the different languages.

    Does anyone else have this problem? Can this be fixed?

    https://wordpress.org/plugins/mqtranslate/

  2. chsxf
    Member
    Plugin Author

    Posted 1 year ago #

    mqTranslate has not been tested with ACF.
    It is the second report we receive that there is some issues with it. We will try to find a solution as soon as possible.

  3. Bjoernobaert
    Member
    Posted 1 year ago #

    Thanks!

  4. wannfors
    Member
    Posted 1 year ago #

    ACF is the no.1 plugin I use in all sites I produce, so support for it would be great!

  5. hovandoholidays
    Member
    Posted 1 year ago #

    hi, i have just migrated to mqtranslate from qtranslate after upgraded my wp to 3.9. now i have encountered a problem on my custom menu languague bar which also the primary menu. the language icons used to work well with qtranslate but now it can't work with mqtranslate. mqtranslate works well with the widget at the footer area but not the custom menu at primary menu.
    my domain is http://www.hovandoholidays.com. please help. thanks a lots!

  6. chsxf
    Member
    Plugin Author

    Posted 1 year ago #

    @hovandoholidays:
    How did you set up the custom menu language?

  7. hovandoholidays
    Member
    Posted 1 year ago #

    hi, i'm using the "Links" under WordPress at "Apearance - Menu - Links: URL: http://www.hovandoholidays.com/?lang=zh

  8. Dani-Girl
    Member
    Posted 1 year ago #

    Hi just to add to this,

    the Advanced Custom Fields Plugin - Field type of Wysiwyg Editor overrides the content in the main wordpress editor when used with mqTranslate (this also existed as a problem with qTranslate).

    Here is the Main word press editor with ACF Wysiwyg Editor below: different content in each field, before update:

    http://i.imgur.com/HzKvyCh.png

    After update - both fields contain the same content:

    http://i.imgur.com/yXRspul.png

    If i turn off mqTranslate, then ACF and the WordPress Editor works correctly.

  9. toimisto
    Member
    Posted 1 year ago #

    There was a hack for this in qtranslate:

    Replacing
    qtrans_save(switchEditors.pre_wpautop(o.content));

    with

    if (ed.editorId.match(/^qtrans_/)) {
    qtrans_save(switchEditors.pre_wpautop(o.content));
    }

    in qtranslate_javascript.php

    Could something similar exist for mqtranslate?

  10. ShawnRisk
    Member
    Posted 1 year ago #

    I have been using mqtranslate and advanced custom fields for the past month and not getting anywhere. The only option that I have been given is create custom fields for each language, and then somehow make these fields work with that language chosen. I think this is really annoying as this might be too many fields for people to do each time they create a new post.

    Updates on this would be amazing.

  11. agenceHYBRID
    Member
    Posted 1 year ago #

    Hello,

    I came up with the same WYSIWYG issue (as Dani-Girl) after migrating from qtranslate to mqtranslate (up to date plugin compare to qtranslate).
    It worked well on WP 3.8.3 with Qtranslate + ACF qtranslate, but can't anymore save on WP 3.9.1 with mqtranslate + ACF qtranslate...

    any solution for making it working ?

    Do i have to downgrade my WP version ?

    cheers

  12. esmi
    Forum Moderator
    Posted 1 year ago #

    @agenceHYBRID: If you require assistance then, as per the Forum Welcome, please post your own topic instead of tagging onto someone else's topic.

  13. ashkas
    Member
    Posted 10 months ago #

    @chsxf Is there any ETA on when mqTranslate will be updated to address this bug?

  14. ashkas
    Member
    Posted 10 months ago #

    @chsxf we're seeing a problem with mqTranslate and ACF, where attempting to save ACF fields on a user profile does not work, after clicking on a language tab.

    It results in no action.

  15. herrstrietzel
    Member
    Posted 9 months ago #

    ... tinymce and qtranslate ... the never ending story ...

    as I switched to WordPress 4.0 and mqtranslate Version: 2.7.1.1
    and I got it fixed by replacing
    (about line 305):

    if ( ed.getParam( 'wpautop', true ) )
    e.content = switchEditors.pre_wpautop(e.content);
    qtrans_save(e.content);

    with

    if (ed.id.match(/^qtrans_/)) {
    qtrans_save(switchEditors.pre_wpautop(e.content));
    }

    This Hack worked for me without using "ACF qTranslate"(intended to translate advanced custom fields) and both with tiny mce advanced and wp-edit (the successor of "ultimate tiny mce").

    If you are new to qtranslate/mqtranslate, my advice is to check the "achilles heel" of qtranslate:
    It has always been the conjunction of qtranslate tabs with additional wysiwyg instances (in fact tinymce instances) such as custom fields.

    So if you encounter any problems the most likely place to search for is the "m/qtranslate_javascrip.php" in your plugin directory.

  16. mrbicho
    Member
    Posted 7 months ago #

    Thanks @herrstrietzel

    This worked for me. I have added a Pull Request in github:

    https://github.com/xhaleera/mqtranslate/pull/14

    I hope it is included in future releases of the plugin.

    Cheers!

  17. sebastianpierre
    Member
    Posted 7 months ago #

    Does this work with ACF and mqTranslate alone, or do I need tinyMCE?

  18. herrstrietzel
    Member
    Posted 7 months ago #

    Hi sebastianpierre,

    it's not a question of whether you need tinymce as it is the default wysiwyg/rich-text editor.

    So the conflict described above usually occurs when your wordpress posts use custom fields with wysiwyg/rich-text editor in conjunction with mqtranslate.

    That's mainly because both tinymce and mqtranslate heavily manipulate the wordpress content textarea by javascript and can interfere with each other.

  19. sannadrea
    Member
    Posted 6 months ago #

    Hi not a code hack but i resolved this by adding two identical custom fields with the only difference of name ending -en and -it
    wp_cs_field_en and wp_cs_field_it

    in code I add the qtrans_getLanguage() to the fixed part of the name of the fields.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • mqTranslate
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic