I am not sure what is going on here. There has been some changes in the code, could you please try the latest version from GitHub, which you can download with ‘Download ZIP’ button on GitHub page or press here for the sake of convenience?
Upgraded to the Github version and the problem persisted.
I can’t blame qtranslate-X for that. But I’m not sure what’s the necessary steps to isolate the problem.
Plugin Author
Gunu
(@grafcom)
@viniciusferrao,
the problem is still there?
try the pre-release of versie 3.3 download here
Hello Gunu.
Unfortunately the problem still persists. As I said, I can’t blame qTranslate-X for this. I don’t know if nginx is the one to blame. That’s why I need help debugging this issue.
Gunu, I’ve installed a new VM from the ground and I can confirm that the bug persists. This is definitely an rewrite problem.
I’ve tried using Apache 2.4 instead, things went better, still broken, but appeared to be an Apache problem.
There are any success stories of qTranslate-X with nginx?
Plugin Author
Gunu
(@grafcom)
@viniciusferrao,
this post deals with a different problem, but this user (extremecarver) also appears to use nginx.
Maybe this helps you further.
Have you tried using Portuguese instead Portuguese Brazil?
I’m having loads of problems with qtranslate-x, I managed to get some infinite loop causing error in my server where it redirected to pt-br/pt-br/pt-br/pt-br/pt-br/pt-br/pt-br….
I also at some point managed to get the same problem as you.
In the end just seems qtranslate-X can’t deal with 5 chars language codes… just 2 chars…
Therefore when you try to open https://ferrao.eti.br/pt-br, pt-br is not recognized as language, but as page. So you get redirected to the pt-br page in english :).
(if you get to solve that you may face the permanent redirect problem, which I couldn’t here either)
ps: I believe you guys were in the wrong track as this does not relate Nginx at all, I’m actually on Apache.
@vbkun gave perfect explanation – thanks a lot, and I added sticky post https://ww.wp.xz.cn/support/topic/pt-br-language-code-is-not-supported, which I believe closes this topic?