UPDATE:
You know what, don’t even bother with qTranslate anymore.  If you currently have qTranslate and you’re fed the hell up with it breaking constantly do yourself a favour – install a new plugin called mqTranslate and simply reconfigure the language settings, blow away qTranslate and live happily ever after. True story.


If you run a bilingual website on WordPress you likely had a plugin conflict as a result of last week’s WordPress update.

What the hell happened?
First, WordPress issued an automatic update to patch holes that were vulnerable to the Heartbleed Bug.  What’s the heartbleed bug? Well, essentially it’s a bug in the opensource ssl programming that most websites are built on, and it can can make your site vulnerable to hackers who can then access private information.  So far, it looks like nobody discovered/took advantage of this vulnerability,  but in any event, WordPress patched the hole (so to speak).

Back to qTranslate.
If you run a bilingual website, you have no doubt heard of qTranslate. It’s an utterly frustrating plugin that allows you to create versions of your site in multiple languages.  I call it frustrating because support for the plugin is virtually non-existent, workarounds are scattered throughout the Interwebs, and it was written with such clunky code that it essentially breaks every time there is a WordPress update.

Why does it break? Basically, it has the compatible WordPress version at the date of the latest plugin update hard buy cymbalta online cheap coded into the programming.  So, to fix the bug you need to go in to the plugin code and change the WordPress version number. That’s it.

Huh?

OK, follow me here…

You go into your WordPress dashboard and click on plugins.  You will see a list of all the plugins you have installed. You see qTranalsate there? OK, click on Edit.  You will open the default page, qTranslate.php. Now, look for the line that says “QT_SUPPORTED_WP_VERSION', '3.8.1“. Change that one at the end to 2 or 3, depending on the update version you are running. Then hit save.

Bam. Fixed.

I wouldn’t normally post something like this because I generally tell clients not to mess with the code, but it’s the kind of bug that will keep popping up if/when WordPress is updated, so it’s worth knowing.  If you don’t feel comfortable doing this yourself, that’s fine.  Your developer can do it for you in seconds.

A wee note of caurion, though: Some folks are reverting back to the previous WordPress release instead of just updating the plugin, which essentially leaves you open to the Heartbleed bug.  Bad idea.

In the meantime, let’s hope the qTranslate developers write a better plugin update soon.

For more information on the Heartbleed bug visit heartbleed.com. It’s a site that was created to explain the bug/vulnerability to the public.

Also, before you do ANYTHING to your code, make sure to backup your site. Just in case.

 

Comments

Pin It on Pinterest