qTranslate and WordPress 3.9.

  • 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://www.ads-software.com/plugins/qtranslate/

Viewing 15 replies - 46 through 60 (of 65 total)

  • erm… disabled it anyway. i had some problems in the post dashboard: quick edit was not available anymore. After disabling qtranslate slug, it’s back…
    Another 3 years of these problems and you guys will ask me for help ??
    gr
    v

    It’s somehow peculiar seeing people pushing qtranslate’s author into delivering overnight updates, when nobody cares sending him a dollar in his whole lifetime, for the effort spent developing such hugely popular plug in.

    I am sure that if anyone sent just 1 dollar to the author, he’d have 1.652M dollars in his pockets and would certainly have a lot of time to dedicate into delivering quicker.

    I respect his work and I thank him to distribute it freely. His plugin is the best I found in his domain, and I tell everyone I know who have a wordpress to use it.
    Sorry if i have been rude.
    I was a bit stressed by the situation.

    Alternative plugin mqTranslate, 100% workinq with WP 3.9

    My editor is back!

    Hi, I still have a long way to learn code, in fact all the way… I’m good at following the instructions that you guys post here. I could have never put up my site together without the forums here. But this time nothing helped until I sent this page to a friend who knows code.
    He tells me that he followed Whaus link: https://gist.github.com/warenhaus/10990386/revisions

    He also said that it’s possible to download the files and substitute them, but there is one with the wrong name
    qtranslage_wphacks.php
    should be
    qtranslate_wphacks.php

    So look out for that.

    You can download the fixed files here:
    https://www.mediafire.com/download/c1zjhy1tcmezn8e/qtranslate_fix.zip

    I hope everyone gets their editor back!

    –

    Thread Starter whaus

    (@whaus)

    @contramare: oops, sorry. thank you for putting up the files in a zip. you can also download or copy&paste them from here (that’s the view without all the changes highlighted):
    https://gist.github.com/warenhaus/10990386

    @contramare, thank you so much.. your files fixed the problem!.

    THANK YOU SO MUCH whaus

    I have no idea what all this coding means but it worked for me!!! I almost died from a heart attack as I didnt do any backup OF COURSE…

    @contramare & @whaus: THANK YOU SO MUCH!

    Maybe its time to change to mqTranslate…

    Thank you very much to all. I have use the zip with the code from @contramare and for now on I’m going to keep the mqtranslate as a life saver in case nothing works ??

    @whaus & @akirk : I merged your patches in a github repository. Feel free to contribute!

    The patched plugin can be downloaded here: https://github.com/nsorosac/qtranslate/archive/2.5.39.zip

    Simply replace your plugin with this one (or only the PHP files if you want because they are the only files that were modified).

    @leslierad:

    Under mqtranslate Settings:
    Open: Advanced Settings
    Find: Settings Migration
    Select: Import settings from qTranslate

    Easy transition to mqtranslate. Visual editor is back. I only had to reinstall the language chooser widget, as this had it’s name changed and hence had disappeared after switching to mqtranslate. Thanks @arctablet for pointing me to mqtranslate.

    More users should convert over to mqtranslate as the author is making regular updates and getting more and more plugins supported, unless the githubs follow all mqtranslate’s regular updates, they may be left behind, not only that but there may be security implications by not being in the WP repo – not that there is anything currently wrong but there is a greater chance.

    The more users the better the support and development will hopefully become with more user input, fixes and suggestions.

    It just seems that qtranslate is a bit dead for now.

    I agree with leslierad but there are more concequences: I f.ex. use other plugins that check qtranslate (qtranslate slug, qtranslate support for woocommerce,…) and just switching to mqtranslate is not an option as these plugins have to be modified manually as well.
    aaah, always something to think about ??

    Agreed Vasch, all I mean is the sooner more people change over, the sooner resolutions can be made and shared etc. making it better for everyone.

    It does seem like the mqtranslate author is working on support for Qtranslate slug, table press and woo comm

    I know I just converted a massive site with many dependencies on qtranslate but now its done I feel better for it.

    If people share their changes, knowledge and a bit of time helping others the transition will go smoother.

    BTW here is a fuller how to convert from qtranslate to mqtranslate walk through for those wanting to try it out.

    Anyway just my 2 cents worth.

Viewing 15 replies - 46 through 60 (of 65 total)
  • The topic ‘qTranslate and WordPress 3.9.’ is closed to new replies.

Tags