[Resolved] qTranslate importer missing language

Home Support English Support [Resolved] qTranslate importer missing language

This topic contains 6 replies, has 2 voices, and was last updated by  Jokke 1 year, 10 months ago.

Author Posts
Author Posts
October 5, 2012 at 10:31 am #78454

Jokke

I've had question earlier on the topic of qTranslate importer missing a language in import process. The original question is at http://wpml.org/forums/topic/qtranslate-importer-misses-one-language/ and that was never resolved. I got customer contact me again wishing to be able to purchase and start using WPML but this is still a roadblock issue, any chance to find out why the problem is happening? I just retried the import process with the latest WP 3.4.2 and qTranslate importer 0.2.3

Cheers,
jokke

October 5, 2012 at 2:11 pm #78518

Anonymous

Dear Joke,
is this still the same database as mentioned here
http://wpml.org/forums/topic/qtranslate-importer-misses-one-language/ ?

October 5, 2012 at 5:56 pm #78591

Jokke

Yes, I tried the import today with the same db dump as in the original post.

Cheers,
Jokke

October 11, 2012 at 1:12 pm #79298

Anonymous

My Manager is going to help with this as it was problematic from the beginning.

October 18, 2012 at 12:02 pm #80516

Anonymous

I don't know how we all missed this but the language code qtranslate is using for swidish is wrong. the correct one is sv and wpml is not finding this!
Let me create a query that may help you with changing this in all your posts

October 18, 2012 at 1:14 pm #80542

Anonymous

I finally got the problem line!!

wp-content\plugins\qtranslate-to-wpml-export\plugin.php
line 449

please change this function

function _lang_map($code){
switch($code){
case 'zh': $code = 'zh-hans'; break;
case 'pt': $code = 'pt-pt'; break;
}

to this:

function _lang_map($code){
switch($code){
case 'zh': $code = 'zh-hans'; break;
case 'pt': $code = 'pt-pt'; break;
case 'se': $code = 'sv'; break;
}

November 2, 2012 at 8:30 am #82844

Jokke

Thank you for your assistance got it working now.

You must be logged in to reply to this topic.