gurumance

Well i have to wait and see ??
Key points for most of the people that use qtx and qts is migration of slugs easy migration Yoast seo xml sitemap.

https://www.lachambredessecrets.com/i18n-index-sitemap.xml
https://www.lachambredessecrets.com/fr/i18n-index-sitemap.xml
https://www.lachambredessecrets.com/mk/i18n-index-sitemap.xml
you can take a look how it’s done on this links.

Will it support in near future, or did you tried to contact https://www.ads-software.com/plugins/qtranslate-slug/ creators to see if they can integrate q-translate slug with your plugin, i noticed someone mentioned that migration to wpmultilang from q-translate x is possible. But for me and many others migrating w/out slugs is impossible.

Ok github version uploaded on test site and after testing everything went well

So far in testing after updating on main site to wp 4.5 and updating it seems that everything works except the old language redirection problem
404 cause of q-translate slugs when testing trough sitemaps
all of the above plugins work fine ??
Except facebook comments i still have not tested it maybe i never will.

lachambredessecrets.com

If you use Yoast SEo and Title and metas than NO
[:en]English text .[:] [:fr]french meta.[:] [:mk]etc[:]

If it helps i removed language Widget and used added language changer to menu(q-translate-x). Tested several links and something strange happened link opens on the language requested wordpress add the slash /fr/englishslug but no 404 error it opens the link in french language for this example if i change language with language switcher from menu it changes to for example english without /en/ to englishslug then if i go back to french language via language switcher link opens with /fr/frenchslug – that was just for testing but before(when the language switcher was in widgets) i used to get page not found ….

hope it helps
??

i tested it on test site and it seems to work there but in order to test more i need to update it on the second site but i don’t know the safest way to update i tried deleting and updating the plugin but that way i lost all post tag category slug translations so i had to restore from backup

i have site where i can test all of it without worry that something will go bad so if any ideas need testing i am here to try n help

I give one clue .htaccess but how i don’t know ??
Pedro i said it was fixed few months ago but after few more tests i noticed i was wrong.

Somehow we need to tell wordpress that if one hits /fr/postname he need to get to the link /fr/postname not get redirected to /com/postname in different language

I still have this problem, and this is big issue if one wants their site to be recognized by google. The problem you described is like mine i think everyone has this problem, problem is wordpress and there has to be solution why cause wordpress add the hreflang link /da /de /mk /fr in front of the link and you get 404 error
weigertj you can test and see that the same thing happen if you use google search engine you write

your niche and sitename in search bar

you get the links to your posts before hittin one of them open your site in a new tab and change the language to be different than the one you searched your niche on google get back to search tab and hit the link you will get 404 error cause the new link will open with latest hreflang language you handpicked.

Thanks, well i will try to help somehow

This is yoast sitemap output
/mk/kategorija/%d0%b3%d1%80%d0%b0%d0%bc%d0%b0%d1%82%d0%b8%d0%ba%d0%b0/

And this is
mk/kategorija/граматика/(q-translate slug)

how it opens in chrome mozzila ie etc..
So q-translate slug read and translate it properly at least i think it does but when used by some kind of xml sitemap creator i get %d etc
After some changes in q-translate-x there is improvement only small percentage of visitors are greeted with page not found errors with slugs not redirecting properly for returning visitors

Fixed.
If someone get here with similar problem
WordPress database error: [Duplicate entry ‘english-tses’ for key ‘PRIMARY’]
INSERT INTO wp_i18n_slugs (slug, lang, name) VALUES (‘english-tses’, ‘mk’, ”)
Search for draft post it named english-tses was in my case in all languages(slug) removed the post and plugin worked but need some more work until than ??

I did one more try and was greeted with same error message this time i also disabled wp super cache.

First i removed old q-translate x and uploaded qtranslate-x-3.4.7.zip than i disabled q-translate slug went to q-translate x (aka languages) changed category and tags hit save and i went to import q-translate slugs once i ticked q-translate slug import and hit save error appeared. Just to note one of my languages uses Cyrillic alphabet maybe it helps .

And those the active plugins i use

Akismet
Settings | Deactivate | Edit
Google Analytics by Yoast
Settings | FAQ | Deactivate | Edit

HH Quizzes
Deactivate | Edit
Jetpack by WordPress.com
ODude Ecard
Deactivate | Edit
qTranslate-X
Settings | Deactivate | Edit
qTranslate slug
Settings | Deactivate | Edit
Quick Adsense
Setting | Deactivate | Edit
Quiz And Survey Master
Deactivate | Edit
Rapid Quiz
Deactivate | Edit
UpdraftPlus – Backup/Restore
Add-Ons / Pro Support | Settings | Deactivate | Edit
Watu
Activate | Edit | Delete
WP-Pro-Quiz
Deactivate | Edit
WP Super Cache
Settings | Deactivate | Edit
Yoast SEO
FAQ | Premium Support | Settings | Deactivate | Edit
Yoast SEO & qTranslate-X
Deactivate | Edit

If it helps

I tested the 3.4.7 version of the plugin from github on the TEST site and it worked did everything as it was supposed to

but than when i uploaded the plugin to the live site i got this error

WordPress database error: [Duplicate entry ‘english-tses’ for key ‘PRIMARY’]
INSERT INTO wp_i18n_slugs (slug, lang, name) VALUES (‘english-tses’, ‘mk’, ”)

Still has some errors but until q-translate x and slug merge i have to go this way ??
Also yea special characters are used cause cyrillic alphabet but search engines know what it is so no biggie