WordPress.org

Ready to get started?Download WordPress

Forums

qTranslate
[closed] qTranslate and WordPress 3.9. (66 posts)

  1. whaus
    Member
    Posted 5 months ago #

    hi!
    is there someone already using a WP 3.9 beta together with qTranslate? It worked for me with a 3.9 alpha (changing the "supported version" in qtranslate, of course), but now the blog in my testing environment doesn't seem to work anymore since a 3.9 beta installed itself. I get an error like:
    Object of class WP_Post could not be converted to string in .../blog/wp-content/plugins/qtranslate/qtranslate_core.php on lin e485

    Strangely, the line referenced is part of the date/time functions (qtrans_strftime):
    return $before.strftime($format, $date).$after;

    https://wordpress.org/plugins/qtranslate/

  2. whaus
    Member
    Posted 5 months ago #

    well, as some kind of workaround until a new qtranslate version comes out, I helped myself by simply removing the "$before." from the last line quoted above. in my environment, that doesn't seem to have a visible impact on the date display, and with it removed, qtranslate works here with WP 3.9

  3. Tracey
    Member
    Posted 4 months ago #

    Thanks for the heads-up - I've just been having problems with auto-updating from 3.8.1 to 3.8.2 and 3.8.3 - so I've switched off auto-updating of WP until things are more stable!

  4. Rafal Lukawiecki
    Member
    Posted 4 months ago #

    Thanks, I can confirm this fixes the problem for me, too. However, the line number is not 485 but 455 in my case.

  5. cukeving
    Member
    Posted 4 months ago #

    As with the last 3 updates - I just changed the wordpress version number to 3.9 in the main plugin file and all working fine now.

  6. kisss
    Member
    Posted 4 months ago #

    Changing version number to 3.9 in qtranslate.php didn't work for me this time. My website was a complete mess and I had to manually downgrade to 3.8.2.

  7. wpusta
    Member
    Posted 4 months ago #

    Dear whaus, many thanks for your quick solution!

    I appreciate it!

  8. elber73
    Member
    Posted 4 months ago #

    In my case it worked smoothly with 3.8.3 but with 3.9 it did not work. I had to go back to 3.8.3.

  9. lakilevi
    Member
    Posted 4 months ago #

    upgrading to 3.9 made problems in visual editor. They introduced a new html editor instance, so the qtranslate javascript code is not working good any more. I got errors in the CMS.
    Did anyone find a solution for that?

  10. Fabian
    Member
    Posted 4 months ago #

    Remove the "$before." at line 455 works for me. Many thanks whaus.
    I don't see any problem right now... But I am wondering in what this "$before." was useful. Strange.

  11. aks49
    Member
    Posted 4 months ago #

    thanks whaus, it works now !

    My articles and menu didnt work since updated to 3.9 this morning !

    Object of class WP_Post could not be converted to string in .../blog/wp-content/plugins/qtranslate/qtranslate_core.php on line 455

    return $before.strftime($format, $date).$after;

    simply removing the "$before." in qtranslate_core.php file from the last line quoted above and with it removed, qtranslate works here with WP 3.9 !

    Cya

  12. hurior
    Member
    Posted 4 months ago #

    Thank you so much whaus, it works for me, and you save my blog and my woocommerce :D

  13. wp_dev5
    Member
    Posted 4 months ago #

    @Lakilevi I'm having the same problem.
    The visual editor is not working. I get this error:
    TypeError: r is undefined
    in tinymce.min.js (line 8)

  14. charlieyllobre
    Member
    Posted 4 months ago #

    Thank you a lot Whaus. Remove the "$before." at line 455 works for me too. For the visual issues, you only need to change the version number of Qtranslate to 3.9 in qtranslate.php and done! it should works properly and we only have to wait for the next update.

  15. lakilevi
    Member
    Posted 4 months ago #

    unfortunately is not enough to change the version number.
    My visual editor is not loading, it makes a js error.

  16. sgross
    Member
    Posted 4 months ago #

    I have the same problem. I tried to change first the version to 3.9 in qtranslate.php and then it said "fatal error" and nothing worked anymore. I removed the qtranslate plugin via FTP and replaced it with the old version. Then I tried only to remove the "$before." as you all said, and then it says "no data transfered from server". I again only exchanged qtranslate core back to its original state. Now at least the pages look ok again, but none of my posts. I would be so so happy and grateful about an idea, thank you!

  17. Tracey
    Member
    Posted 4 months ago #

    Hi folks,

    for those of you still struggling even after changing the plugin as described above : it might be useful to consider reverting to an older version of WP (3.8.3 worked for me) and switching off auto-updates to the WP core so that you can select to upgrade WP only when you know a proper version of Qtranslate is in place - this is what I had to do on my clients bilingual site.

    Here are the steps I took:

    1. Edited wp-config.php to say do NOT automatically update
    2. restored WP version 3.8.3, keeping the wp-config.php in place from the previous step
    3. told my client that under NO circumstances is she to update WP herself until I give her the go-ahead! :)

    Result = perfect!

    These 2 articles were very useful to me to do steps 1 & 2 :

    Stopping auto update http://make.wordpress.org/core/2013/10/25/the-definitive-guide-to-disabling-auto-updates-in-wordpress-3-7/

    reverting to old version of WordPress [ Please don't use that link, use this one instead with 3.8.3 ] https://codex.wordpress.org/Updating_WordPress#Manual_Update

    hope this helps some of you!!

  18. whaus
    Member
    Posted 4 months ago #

    glad I could help.

    Note: as some mentioned already, the Visual editor will not work. qtranslate will work in the text editor, but as WP 3.9 introduces a new version of the visual editor (as lakilevi noted), this will require more changes in how qTranslate replaces that editor.

    same goes for the next WordPress (4.0): changing the version number in qtranslate will enable it in text editor mode, but will not make the visual editor work.

  19. whaus
    Member
    Posted 4 months ago #

    @sgross: did you use your ftp program to make the changes, or did you use the plugin editor built into WordPress?
    I suggest you use the builtin editor, and you need to apply both changes.

  20. FionaFionaWP
    Member
    Posted 4 months ago #

    Anyone know when the update for qTranslate is ooming .. we're in a mess without it.

  21. sgross
    Member
    Posted 4 months ago #

    @whaus: thank you, I tried both at the same time, it all broke together; 2nd time I only deleted $begin and it broke, too. I used the internal editor. Now someone helps me to figure out how to get back to 3.8.3

  22. sgross
    Member
    Posted 4 months ago #

    What's the difference of using the internal editor and ftp, i thought this both has the same functionality?

  23. Tracey
    Member
    Posted 4 months ago #

    @sgross - I posted details of how to get back to 3.8.3 above - it's important that you disable auto-updates first as otherwise each time you go back to WP 3.8.3 it will quickly update to 3.9 ... good luck!

  24. lakilevi
    Member
    Posted 4 months ago #

    I struggled 4 hours to correct the editor bug. Partially it was working, but the data was not saved in the end. They switched to a new major version of TinyMCE and I had just to give up.
    I rolled back to 3.8.3

  25. Side note:

    as otherwise each time you go back to WP 3.8.3 it will quickly update to 3.9

    I'm sorry but that is 100% not true. Auto-update only does minor version number updates. It will not update from 3.8.3 to 3.9. Never. ;)

    Now someone helps me to figure out how to get back to 3.8.3

    You can install WordPress 3.8.3 directly on top of 3.9. Use the manual update instructions and make sure you have a backup of the way it is now first.

    https://codex.wordpress.org/Updating_WordPress#Manual_Update

    You can get the 3.8.3 files from the release archive page, scroll down to the bottom.

  26. Tracey
    Member
    Posted 4 months ago #

    @Jan Dembowski
    As it happened to me 4 times, I think I can safely say that it happened :) despite what is intended...

  27. sgross
    Member
    Posted 4 months ago #

    Thank you all so much, and also @Jan, thank you!

  28. Sorry and I'm not being obtuse (and only on 1 cup of coffee too ;) ) but the only reason 3.8.3 would update to 3.9 is if that was enabled via a plugin or filter. Honest.

    http://codex.wordpress.org/Configuring_Automatic_Background_Updates

    If your installations did get automatically upgraded then give that link as well as the one you posted a read. Somewhere in your setup something enabled that filter.

  29. FionaFionaWP
    Member
    Posted 4 months ago #

    Maybe if we knew when the update was coming we wouldn't be destroying our websites and spending inordinate amounts of time devising temporary fixes that are clearly not working effectively for us all. Anyone know when this is? Are we talking days, months years?

  30. zioproto
    Member
    Posted 4 months ago #

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic