Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi john,

    I have tested to change editor raw mode save and change it back then save again 3 or 4 time but i couldnt get the langage switcher back on top of the form. I also tried to desactivate all other plugin i had on the website but that didnt work either.

    I’ll upload a test version during the weekend to give you tha access so you can check yourself if you see something wrong.

    I have also tested the plugin on a fresh install and it seems to be working great. If it is not a conflict with my plugin maybe i’ll look in the theme to unplug some js component i added but they usually dont interfer with backoffice as long as they are only loaded on the front from function.php.

    Thank you for your time.

    Bruno

    I have used qtranslate for many years on a lot of website, and followed clothely your project since you forked it to have an updated bug free version.
    The step :
    I have just updated qtranslate-x v 2.9.6 with the package from github so 2.9.7.4 if i understand correctly extension.
    Then i went to pages admin and edited one page.
    What i have with the 2.9.6 version Edit page
    And what i have with the 2.9.7.4 Edit page

    The theme used is twenty twelve but it was working well before this update as you can see on the 2 images.

    You are welcome, thanks for all the hard work.

    Bruno

    Hi John,

    I have just tested the latest version from github.
    The page admin doesnt show the language selector anymore, so the title and the content are not splited. I thought it was because i also use qtranslate-slug so i desactivated it but it doesnt pull back the selector on top of the form.
    I dont see any JS error in the console, neither as php error with all debug option activated.

    Bruno

    Hi Pedro,

    @bteboul, did you find any error in includes/class-qtranslate-slug-widget.php line 49?

    Yes i did find that the value is related to a form checkbox that is not set if not checked so it warn us about the undefined value, the isset test allow us to get rid of this warning without side effect.

    I did find a bug in the taxonomy backoffice, wp-admin/edit-tags.php?taxonomy=category that seems to break the taxonomy form.
    Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'qtranxf
    I’ll try to have a look asap and hold you inform.

    Thanks again

    Hi, thank you both for your work on qtranslate-x and slug.
    I had 2 changes to make in the code of slug contrib from github :
    File includes/class-qtranslate-slug.php line 739 in order to remove an unidefined value
    if ($GLOBALS['q_config']['url_mode'] == 2) {
    file includes/class-qtranslate-slug-widget.php line 49
    $short_text = (isset($instance['short_text'])) ? $instance['short_text'] : '';

Viewing 5 replies - 1 through 5 (of 5 total)