Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Author Gunu

    (@grafcom)

    @beta2k

    try the latest beta version of qTranslate X

    Download it here

    Do not use install via WordPress admin!
    First unzip the new file.
    Deactivate the existing version of qTranslate in WordPress admin.
    Then with FTP delete all files in the existing qtranslate-x folder and after that copy all new files in it.
    Activate qTranslate-x again via WordPress admin.

    Thread Starter Beta2k

    (@beta2k)

    hm there is no more language switcher button after this update?

    Thread Starter Beta2k

    (@beta2k)

    i get this error when trying to edit a post:
    https://i.imgur.com/z1XAGLl.png

    what is the reason?

    Plugin Author Gunu

    (@grafcom)

    @beta2k

    what plugins and theme you use?

    Thread Starter Beta2k

    (@beta2k)

    WordPress 4.2.2
    Twenty Thirteen Theme
    plugins: https://i.imgur.com/o7hMUT9.png

    Plugin Author Gunu

    (@grafcom)

    Disable qTranslate Slug see if that makes a difference with the latest beta version of qTranslate X

    I Adressed the same issue with version 3.5.5 javascript error here – https://github.com/qTranslate-Team/qtranslate-x/issues/164

    Plugin Author Gunu

    (@grafcom)

    @guntiss @beta2k

    another update in the Beta version Download it here
    see if that makes a difference

    ## Changelog ##
    ### 3.3.5 ###
    * Feature: [Integration Framework](https://qtranslatexteam.wordpress.com/integration/) finalizing JSON file format.
    * Enhancement: function qtranxf_error_log to show crucial error messages as admin notices on all admin pages and to update ‘error_log’ file.

    Thread Starter Beta2k

    (@beta2k)

    still the same error (https://i.imgur.com/z1XAGLl.png) :/

    Hi, some update/news about this issue?
    I downloded QtranslateX 3.3.8.8 and the error still the same.

    Beta2K, Do you solve the problem? How?

    Tks, hugs!

    Thread Starter Beta2k

    (@beta2k)

    nope.
    not solved for me, yet :/

    Plugin Author Gunu

    (@grafcom)

    @guntiss @beta2k

    this has now been resolved with the latest version?

    I have the same Problem like the other guys,

    WordPress 4.3.1
    qTranslate 3.4.4
    ACF qTranslate 1.7.9

    Plugin Author Gunu

    (@grafcom)

    @ppkoch

    did you read this Integration Guide?

    I did read the integration guide guide, not just once.
    But t is really hard form as non-native english speaker to understand.
    what i understood:

    Need to tell qTranslate which fields are for translation and
    on the frontend where to change output if language change.

    Multiple ways designate the fields to be multilingual.
    1.editing the JSON-File in the qTranslate-x Plugin folder.
    –> don’t know what to write in there
    2. don’t understand, setting the class of the backend input fields?
    how can I edit classes from elements in the backend.

    3. Add the class or ID from designated multilanguage input field a
    Language–>Options–>CustomFields.

    4. +5 I don’t understand

    How translate multilingual fields at frontend

    didn’t had to do that with acfqTranslate-x

    To get the change just wrap the field function in __() like that.
    exp. __(the_field(‘customFieldName’)).

    2. + 3. I don’t understand.

    I added the id from the desired field into the custom field id field
    and wrapped at the front end the out in __().
    example id =wp-wysiwyg-acf-field-introtext-55fceae795086-editor-container
    __(the_field( ‘introtext’ ));
    doesn’t make any difference.

    All fields where I added the acfqTranslate fields, worked fine,
    they get the Flags from the different Languages added, and I just add
    the different lang. and I works out on the front and backend.
    Just the WYSIWYG editor works on the front but not on the backend.
    One language always overrides the other entered.

    I am really sorry I really want to learn how to use it, I really like the plugin I allready tryed for shure 3-4 other language plugins, and all hade alot issues.

    thx
    p

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘language switcher not working for WYSIWYG custom field’ is closed to new replies.