Thread Starter
vbkun
(@vbkun)
I managed to get it working…
Everything is running fine and perfect now, aparently qtranslate-X can’t handle 5 chars lang prefixes, in my case pt-br, which came re-configured in it.
After deleting portuguese (pt) and changing pt-br to pt everything is fine, custom fields, regular fields, redirects, etc.
@vbkun: Seems like all your problems came from ACF: https://ww.wp.xz.cn/plugins/acf-qtranslate/. Maybe you should report it on their forum? In any case, there is obviously something special in your setup, which can be figured out with a little patience.
Wow, thank you for letting us know. Yes, indeed it supports two-letter language codes only. The incoming 3.3 version has ‘pt-br’ changed.
Thread Starter
vbkun
(@vbkun)
Hey John 🙂
Thanks for the reply but no, it wasn’t an acf problem.
I had the exact same problems without acf. As I stated above… qtranslate X just ‘colapses’ with the 5 chars ‘pt-br’.
It can’t understand redirects, the content filters fail (custom field or default ones), etc.
But all is soved so far for me
Do we still deserve 1 star only? We lack a better documentation. Many people have trouble in the first install, but we are here to help.
Thread Starter
vbkun
(@vbkun)
John just a side note… nice if you guys could add some big warning on it asap….
While trying to solve my errors I found a bunch of people on the forums that seemed to have the exact same problem as me… but were not even near to find out the pt-br was the problem 🙁
Thread Starter
vbkun
(@vbkun)
Nah I’ll change 😐
I wouldn’t say due support thou… I mean in the post it was clear something was acting up and it was the language code (thanks god that post existed, its what saved me :D), but no one was near to guess the guy’s problem was the language… 🙁
But I don’t want to be too critic here… I know how something like this get trought… specially when pt-br is the only exception, its not the most commom language and well, you guys are coding from previous works… so I understand how it can go trough 🙂
And well, not really a ‘better documentation’ case… it was the built in setting I never dealt with :|. I mean, I didn’t set ‘pt-br’, it was there from the install :(. When i suspected of the code… the own verification of the field did not allow me to set pt-br, nothing better than verification fields :).
Btw, thanks again for the hard work, really ^^
Thread Starter
vbkun
(@vbkun)
(ok can you help me on how to edit this rating? oo)
—edit
done 🙂
I have put a sticky post about pt-br: https://ww.wp.xz.cn/support/topic/pt-br-language-code-is-not-supported, but it is only for a coupole of days, since 3.3 is on the way to be released.
Well, I suggest you to read this: https://qtranslatexteam.wordpress.com/2015/03/30/release-notes-3-3/, try this version from GitHub: https://github.com/qTranslate-Team/qtranslate-x and then you will hopfully decide to change it to 5 star 😉 Remeber, this is community project in progress, we are not done yet.
