Viewing 15 replies - 1 through 15 (of 38 total)
  • I could migrate without a problem with 3.1.
    https://www.weigertimages.com

    I just wrote a post & a plugin adressing this issue, in some cases this is proven to help:

    https://kuchenundkakao.wordpress.com/2015/03/03/problems-migrating-from-mqtranslate-with-qtranslate-slug-to-qtranslate-x/

    Great, thank you! But why I don’t have any error when switching languages?

    weigertj

    (@weigertj)

    Hi kuchenundkakao,

    Actually I understand your point as after migrating I had the same problem with the language selector. Your fix works, I have just tried it.
    However, I found a different, simpler solution. I use qTranslate Language Chooser instead of Language Selector and language switching is just fine without your fix.

    My custom CSS looks like this:

    .qtranxs-lang-menu li {
    display:inline-block;
    margin:5px 3px 0px 3px;
    }
    
    #language-box .qtranxs_language_chooser {
    	margin-bottom: 0;
    	margin-top: 4px;
    	overflow: hidden;
    	position: relative;
    	z-index: 100;
    }
    #language-box .qtranxs_language_chooser a {
    	padding:4px;
    }
    #language-box .qtranxs_language_chooser li {
    		float:left;
    }
    
    #header-toolbox {
    	position:relative;
    	z-index:100;
    }
    
    #mainmenu {
    margin-top:0px;
    }
    
    ul {
    margin-bottom:10px;
    }
    HU ist Sebastian

    (@kuchenundkakao)

    After the Update to 3.2.9, the fix breaks the site. Thanks a lot, John ??

    I just updated my post fixing the migration helper. See here:

    https://kuchenundkakao.wordpress.com/2015/03/03/problems-migrating-from-mqtranslate-with-qtranslate-slug-to-qtranslate-x/#update

    weigertj

    (@weigertj)

    The fix works, kuchenundkakao!
    However, my solution outlined above worked all the time, the update didn’t break it.

    csmillie

    (@csmillie)

    Surprised this is still on going and breaking change was introduced.

    Is qtranslate-x committed to supporting this functionality?

    Thanks @kuchenundkakao for the fix and updates.

    Plugin Author Gunu

    (@grafcom)

    @csmillie,

    Is qtranslate-x committed to supporting this functionality?

    if we (John) find time for it, then surely.

    peterreckers

    (@peterreckers)

    So everything seems ok but the switching? I can go to /en/ and find the english menu and in my menu I find a english flag. Flag is not reacting on my frustrated clicking. Also without /en/ it go’s to default (Dutch) with the Dutch flag (also ignoring me). Hope I can help with the troubleshooting.

    Regards

    baga

    (@baga)

    Has anyone noticed that the slugs are not automatically created when using qTranslate X + qTranslate Slug?

    HU ist Sebastian

    (@kuchenundkakao)

    Hey Baga,

    That’s a problem of qtranslate-slug: For creating the slugs, qtranslate-slug uses the function qts_use, which tries to split by the old lang tags (‘<!–:de–>’ etc).

    Just edit the file qtranslate-slug/includes/class-qtranslate-slug.php in line 703 (the function qts_use should start there) and replace the function with this:

    public function qts_use($lang, $text, $show_available=false) {
                return qtranxf_use($lang, $text, $show_available);
            }

    This fixes the Problem (at least at my site ^^).

    baga

    (@baga)

    Thanks Kucheundkakao, it works perfectly!
    You’re my life saver ??

    baga

    (@baga)

    Hi, I wanted migrate today but I just saw this post. Is it possible now to migrate without problems? waiting to hear from you

    Hi, please see kuchenundkakao’s solution above, it’s fine. Without it the hreflang tags are not proper.

Viewing 15 replies - 1 through 15 (of 38 total)
  • The topic ‘Using mqTranslate Qtranslate Slug – do not migrate yet’ is closed to new replies.