qTranslate-X breaks the Site Language #98
Comments
|
Has that started happening after an update, or you are the first time user? What did you use before -qTranslate-X? Do you see the menu language switcher on the top-right corner of admin bar? q-X takes control of the site language and normally menu at the top-right works. The default language is changed to English after q-X install. You have to add Italian to the list of languages, and then you can switch to Italian via menu at top-right. This is a know imperfection, we will adjust soon. |
|
Ok I've seen it. |
|
Yes, we lack a good documentation. Also working on it. |
|
Again here sorry. I tried one of the blog with a different computer and different browser and.. the problem is the same, it is in english. Is it a cookie related thing? Is there a way to change it permanently to Italian? |
|
Yes, it keep the current selection in cookie. If cookie is not set, then it On Wed, Mar 25, 2015 at 8:18 AM, alberto notifications@github.com wrote:
|
|
I think yes. Mainly because if I deactivate qTranslateX the wp admin is in italian. But I cannot be sure because with qTranslateX activated if I try to change the language under "Settings > General > Site Language" dropdown menu my choice is ignored and qTranslateX se always en_US as I explained in the first issue post. I had before mqtranslate, but I have checked the "import configurations from mqtranslate" in Import/export setting panel. |
|
I mean default in -X configuration. |
|
where do I set it? |
|
-X configuration page, Settings/Languages: On Wed, Mar 25, 2015 at 9:11 AM, alberto notifications@github.com wrote:
|
|
Yes it is: Italian is the first and checkboxed. |
|
If I have understood correctly: |
|
I am not sure, maybe it does not do anything then, just keeps language from WP. If you deactivate -X, what language is shown on page /wp-admin/options-general.php? Set it to Italian too and do not change it manually when q-X is active. |
|
Indeed the default was taken from WP instead of q-X default. This is supposed to be improved now in 3.2.9.3. If you wish to try it: https://github.com/qTranslate-Team/qtranslate-x/archive/3.2.9.3.zip |
|
OK, this new version resolve the global language roblem but it is breaking the qTranslate-SLUG plugin (it does not work and it does not recognize that qTranslateX is installed) |
|
(I don't know if this issue has visibility due to its closed status, if no feedback I will open a new issue for qtranslate slug support in the next days..) |
|
Yes, I still get e-mails and notifications even if issue is closed. Slug issue is known to us and to -slug developers: not-only-code/qtranslate-slug#108, and is on the list. Opening a new issue would not accelerate the things. |
|
hi! i've updated our code to fix this issue. the language widget now has the url with the lang. for example, if fr is your default language, the links in the menu now have
then its redirected to
its a workaround, but hey, its sunday :)) |
Wednesday Mar 25, 2015 at 09:18 GMT
Originally opened as qTranslate-Team/qtranslate-x#98
Hi!
I have done a massive upgrade from mqtranslate to qtranslatex (more then 10 wordpress sites).
I've read and followed the migration notes and all configurations and translations are good so far.
But the mail language is broken in the admin panel: in english and not in italian.
On "Settings > Languages > General Settings" the default language checkbox is Italiano.
On "Settings > General" there are icons of languages and Italiano is selected.
On "Settings > General > Site Language" the Site Language dropdown menu is en_US. If I change it in Italiano the page is refreshed, there is a message on the top of the page about good setting saving ("Impostazioni salvate") but the admin panel is still in english, and the dropdown menu Site Language is setted to en_US while I'm expecting to see Italiano.
If I deactivate the qTranslate-X plugin the admin panel is in Italian. If I activate the qTranslate-X plugin the admin panel is in english and there is no way to change it.
What can I try?
The text was updated successfully, but these errors were encountered: