Pedro Carvalho

Hi elenavera, thanks for using QTS!

the flags at the top are in a widget? they don’t seem to be working at all ??

are you using qts widget right?

Hi everyone!

can you please test the latest version on github?

i believe it is fixed, but please let me know what you think:

https://github.com/not-only-code/qtranslate-slug

thanks!

Hi, thanks for using QTS. nice catch!

the next version will fix that, among other things.

if you wish to test before hand, the latest code is here:
https://github.com/not-only-code/qtranslate-slug

Hi! So, I was working on this issue, and I was able to fix it!!

Please, can you both test the latest code on github?

https://github.com/not-only-code/qtranslate-slug

i really appreciate it ??

terms are still not translating right, but custom posts, pages and posts are.

There’s one difference now: if the user was on the main language and clicked on a link to a secondary link, the page will show in the secondary language.

later on, I’ll make sure it stays in the main language.

There’s no problem if the user was on secondary language and clicked on a link in main language. it will show the link in the secondary language.

let me know how if its fixed for you!

p.

yes, I was wrong too ??

well, if we don’t redirect, people that want to change language can’t do that.

Hi everyone!

yep, that’s a big issue for me too, but i don’t think is related to hreflang.

1. user visits the site
– qtranslate-x sets cookie for lang “mk”

2. user clicks in a link to a different language ( google, in facebook etc )
– site.com/de/slug-de

3. error because it tries to find site.com/mk/slug-de

Solutions?

1- reset the cookie.

2- parse the cookie first, then redirect. <– how?

any ideias?

WPBot, thanks for using QTS.

you’re right.

but unfortunately, i don’t have a solution. all the rewrites are there, even for category-name/page/n .

i need to dig deeper ??

Hi nicomoka,
I didn’t quite understood what you are trying to do.

when are you filtering the url?

do you have access to the id? if so, you can get the correct url by using:

$the_slug_in_lang = qts_get_slug( $id, $lang );

if not, QTS has a private version of get_page_by_path,

for example, i did this:

global $qtranslate_slug;
$this_post = $qtranslate_slug->get_page_by_path(basename( untrailingslashit( qts_get_url() )));
$this_id = $this_post->ID;
var_dump($this_id);

To do that, i had to change the function get_page_by_path signature to public. its in file inc/class-qtranslate-slug.php, line 1225.

I might create a public function to do that, if there’s a need for that, so you don’t have to keep changing the function.

Hi nelsonamaya, thanks for using QTS and giving it 5 starts ??

it really means a lot to us.

enjoy!

Hi Yumejo, I’m glad the problem is gone!

thanks for reporting, I’m always happy to get feedback from users like you!

enjoy!

Hi camrinp, thanks for using QTS and taking your time to report a bug.

I stand with weigertj, AIOS is a great alternative that plays well with everyone.

Even without QTS, I can’t translate meta description since yoast 3.0., including fb and twitter fields.

yoast SEO 3.03 has deprecated some valuable sections of their plugin, so, even without QTS, you will have trouble translating your content.

i see… it’s a puzzle ??

fixed in v1.1.18!

thanks!

its here!

thanks for using QTS!

Hi weigertj, thanks for the bug report!

i can’t figure why those specific links are being wrongly redirected.

if you create a new post, does it have the same problem? are those old links?