WordPress 3.7 ?

Hi razoredger, it is working now, thank you so much for your help. You saved my day!! ??

Actually, I’m not having any problems after the update to WP3.7.1. I just left the qtranslate editor disabled. The site and the language switch work fine. The only problem is that I have to use the qtranslate’s shortcodes because I can’t use the editor.

That’s definitively the best option for me. I just leave plugin untouched and keep on editing using shortcodes. You can copy & paste them from any page you have already multilingual.

It could be not a solution for customers not used to edit HTML code, but I think it’s best to let the author update the plugin.

Problem fixed
until the new version of

qtranslate_wphacks.php
line 54 :

if($GLOBALS[‘wp_version’] != QT_SUPPORTED_WP_VERSION)

change

if($GLOBALS[‘wp_version’] == QT_SUPPORTED_WP_VERSION)

Glad it did the trick!

Check out mqtranslate plugin to get compatibility with WP 3.7.1. It’s a fork of the other,is totally 3.7.1 ready and picks up all your qtranslate stuff.

@hititdesign
THANKS, this did the job!!

I didn’t try the first solution given in the beginning of this topic,
changing define(‘QT_SUPPORTED_WP_VERSION’, ‘3.6.1’); to 3.7.1.

Are these solutions the same, or one is better than other maybe?!

IMO, switching plugins to mqtranslate is the preferred solution due to the fact that doing so adheres to WordPress website security advisories to implement currently maintained up-to-date plugins within the latest WP version environment.

“Patches” are proposed to qtranslate, are help, much like duct tape fixits, made for the short term.

@rezoredger As soon as the update for 3.7 arrives, I plan to rewrite the code to old settings and update the plugin.

What do you think about this plan? ??
It should work I guess…

@greg007 Sure, if you mean undoing the version number patch on qTranslate before updating it, why not. I’m not sure it would be necessary to do so however since any update overwrites version stuff in the plugin.

Personally, as soon as I switched to the mqtranslate plugin and found it did the job, I deleted qtranslate altogether as it interfered and was not required. No data, style or functionality loss was observed. It just works.
BTW, here’s the link to the alternate plugin: mqTranslate plugin

after updating qtranslate , i still got and error in erro_log

[18-Nov-2013 21:15:39 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at…./public_html/post_car.php:1) in …./public_html/wp-content/plugins/qtranslate/qtranslate_core.php on line 71

@tayssir.ch

The patch does not always work…
Why don’t you try the alternate plugin? It does the same job, is up to date: mqTranslate

@rezoredger

Under support tab, there are few topics with issues on this plugin.
One says that this plugin does not translate widgets (crucial to me),
and the other one says this plugin changes the website appearance.

Did you experience such problems?

I am using several widgets that switch languages between French and English, such as Testimonials, Tag Cloud.

Widgets to be translatable must be localized, if they are, they can be translated and switch the same as did the original plugin in my experience.
If no localization code exists in the plugin template, then no translation will show until that code is added. See plugin localization for that.

In the case of widget titles translation, I have used the title short codes successfully when title translation was not available such as for menus.

UPDATE is here this morning. ??
All is ok now with qtranslate!

OK, now AGAIN qtranslate is not working, I have all pages and posts in one page for all languages.
Is anybody experiencing the same problem with updated qtranslate plugin??!

It was fine after the update, now a few days later I come back to and find a problem… :/

If I am not clear, I do not have a different tab for each language, all is in one page now.