Phenomenon:
The phpmyadmin3.5 version (release-date-3.5.0, a configuration-optimized version of Phpmyadmin_3.5_path8.net) has been used, and this version is relatively concise and the newer PMA is a bit bloated. However, the use of php5.5, and php7.0 in Windows, found that the date was displayed as garbled
Scheme:
File libraries/common.lib.php, line 1648 line
$format = __ ('%B%d,%Y at%i:%m%p ');
Change into
$format = '%y-%m-%d%h:%m:%s ';
can be, date format display format Example 2016-01-27 11:49:07
Reason:
The Pma_localiseddate function uses the strftime () function, the first parameter of the Strftime function is a date format, phpMyAdmin the source program uses a format string in Chinese, and the PHP version under Windows, In the format will be turned into garbled. After confirming that Linux does not have this problem, PMA is normal.
Add: phpMyAdmin Chinese garbled problem is very common, mainly UTF-8 and GB2312 encoding can not be displayed correctly at the same time.
Method One:
1. Because MySQL's default encoding is latin1, we first need to modify the phpMyAdmin encoding conversion. Modify the select_lang.lib.php file under the Libraries directory to change ' utf-8 ' => ' utf8 ' to ' utf-8 ' => ' latin1 '.
2. The next step is to modify the encoding of the page to show that the ' zh-gb2312 ' => array (' Zh|chinese simplified ', ' chinese_simplified-gb2312 ', ' zh ') be modified into ' Zh-gb2312-utf-8 ' => Array (' Zh|chinese simplified ', ' chinese_simplified-gb2312 ', ' en '), which is added zh-gb2312 behind the-utf-8, This allows the page encoding to support UTF-8.
3. First select Zh-gb2312-utf-8 into phpMyAdmin, this time browsing GB2312 encoded data is normal, but browse UTF-8 data is garbled. If you browse UTF-8 data, go to the home page, and then choose Zh-utf-8 on the language.
4. The default language encoding is very long, you can annotate other encodings with/**/, leaving only Zh-gb2312-utf-8 and zh-utf-8 two encodings.
Method Two:
You can also modify the inconfig.inc.php configuration file of Phpmyadm, and the problem is solved by changing $cfg[' lang ' = ' en-utf-8 ' to $cfg[' lang '] = ' zh-gb2312 '.