heliogabal23

@gunu,

well, I gave up and uninstalled qtranslate-slug, now at least I can have both /team and /en/team show correctly. Of course, that leads to the other slugs not being translated, so I get /kompetenz and /en/kompetenz, which is not perfect for SEO purposes, but for now I can live with that.

It has the nice added benefit that I don’t even have to change the links in the translated version, as qtranslate X is smart enough to redirect to the right language.

Still looking forward to a compatible version / merge, as I think for a full blown localization solution it is absolutely necessary to be able to have both the possibility to have the same slug on different languages as well as being able to localize the slugs.

But looking at the tremendous work you already did with qtranslateX, I am confident that there is going to be a solution to this sooner or later. Thanks for this well-thought through, complex but simple to handle plugin!

hi John,
thanks for your detailed explanation, helped a lot to understand how this is working. So this is apparently not as trivial to solve as I was hoping. I understand the original idea and that was the first thing I thought myself when looking at it and wondering why this is showing in the translated language instead of the one I’m looking at. If I can’t make any sense out of the language label, I probably won’t understand whats translated anyway. From the context, I can deduct that this must be some different language that I’m looking at, if I understand it or not.

In the case where there are several translations, it gets more obvious to the visitor what’s going on, but in a lot of cases, there will be just two languages and someone looking at it might just think: Why is that suddenly in a different language? Is that an error?

So an option to choose in which language the language should be shown would just give an implementer the possibility to adapt perfectly to his/her use case.

Anyway, it really is a minor annoyance and totally ok as a feature request with (very) low priority. I just wanted to mention it because it made me wonder as to why it is the way it is and I thought it might be helpful to someone else if I raise the question here.

I’m no programer, so unfortunately I can’t help with an actual solution, but I hope just discussing such questions might be beneficial as well.

Thanks for looking into this! I think it might not even be our team nor qtranslate-x but qtranslate-slug that’s the culprit here, I can’t seem to make them work together in any case. It might be different independent bugs (or just my plain ignorance), so I’ll try to explain as detailed as possible what has occured to me.

I didn’t use any multilingual plugin before, so this is a clean qtranslate-x installation.

All pages and menus are working now, except the one that is rendered by our team plugin. This is actually an empty page with a different template file where this is loading the content:

<?php do_action( 'woothemes_our_team', array(
    'orderby' => menu_order,
    'order' => ASC,
    'per_row' => 3,
    'limit' => 100 )
    );
?>

The page is showing fine in the default language, but I get the redirect error from my first post. I can’t really tell you step by step because I didn’t build the site but only tried to implement qtranslate-x.

Here’s some hints that might help: This only happens with

Use Pre-Path Mode (Default, puts /en/ in front of URL). SEO friendly.

, if I

Use Query Mode (?lang=en). Most SEO unfriendly, not recommended.

, the page loads fine.

If I install qtranslate-slug, it also works with pre-path-mode, but I can’t have the same slug (team should be used in german and english) in both languages. That might be a bug in qtranslate-slug.

Don’t know what else could be helpful, let me know.

This would be a very nice option to have indeed. After looking at Post 5 of the mentioned link, I found the corresponding hooks for qtranslate-x:

qtranxf_useCurrentLanguageIfNotFoundShowAvailable
qtranxf_useCurrentLanguageIfNotFoundUseDefaultLanguage

but when I try adding these to my themes’ functions.php like this, there’s no difference at all:

remove_filter('the_content', 'qtranxf_useCurrentLanguageIfNotFoundShowAvailable', 100);
add_filter('the_content', 'qtranxf_useCurrentLanguageIfNotFoundUseDefaultLanguage', 0);

Do I have to do anything else or is this supposed to work? Or should the Compatibility Functions be enabled and the original hooks be used?

qtrans_useCurrentLanguageIfNotFoundShowAvailable
qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage

first steps with wordpress here, so maybe I missed something obvious?