New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The error about "Ignoring unsupported language code." with version 4.6.1 #12256

Closed
janpoem opened this Issue May 14, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@janpoem

janpoem commented May 14, 2016

The version about 4.6.1, pma will show this error: Ignoring unsupported language code.

There are two errors in the file libraries/LanguageManager.php, see as below:

In line 707 & 708:

error one

$this::$_language_data

It is quite obvious clerical error.

Start from line 780, the method about selectLanguage

$langs = $this->availableLanguages();

From this function return, will be languages mapping. In this mapping, the language name is the key and they are converted to the lower case, such as : zh_cn. But in the below process, when you get the language name from env vars, it is mixed case style, such as zh_CN actually.

So we will get $this->_lang_failed_cfg or $this->_lang_failed_cookie or $this->_lang_failed_request as the true finally, and it will show the error "Ignoring unsupported language code.".

Fix them, the error will be gone!

Thanks!

@ibennetch ibennetch added the duplicate label May 14, 2016

@ibennetch

This comment has been minimized.

Show comment
Hide comment
@ibennetch

ibennetch May 14, 2016

Member

Hi and thanks for your research and report.

I believe this is a duplicate of #12118 which will be fixed for the 4.6.2 release, which is expected in just over a week.

Member

ibennetch commented May 14, 2016

Hi and thanks for your research and report.

I believe this is a duplicate of #12118 which will be fixed for the 4.6.2 release, which is expected in just over a week.

@ibennetch ibennetch closed this May 14, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment