PhpMyAdmin installation and problem summary

1/The mcrypt extension cannot be loaded. Check the PHP configuration;
2. The configuration file now requires a top secret phrase password (blowfish_secret );
3/#2003-the server does not respond.
The latest phpMyAdmin version has been updated to 2.11.5.1. Many of the Configuration Methods circulating on the Internet are earlier versions and are not suitable for the new version; so flymorn also listed the configuration steps of phpMyAdmin2.11.5.1 below. For the convenience of switching and debugging PHP, I used windows and local debugging.
1. First download the phpMyAdmin installation package:
To foreign official website http://www.phpmyadmin.net, click the navigation bar on the Downloads page, select “all-languages.zip version to download to local, decompress the file to the system specified virtual root directory phpmyadmin folder (can be customized folder name ), for example, the local storage location of flymorn is D: \ www \ phpmyadmin.
2. Find the/libraries/config. default. php file in the phpmyadmin folder (the old version is the config. inc. php file under the root directory) and open it with a tablet that supports UTF-8 encoding for editing.
3. Search for $ cfg ['pmaabsoluteuri ']
Modify the phpMyAdmin URL that you will upload to the space
For example, $ cfg ['pmaabsoluteuri '] = 'HTTP: // www.piaoyi.org/phpmyadmin /';
Here, because I am local debugging, I changed it to $ cfg ['pmaabsoluteuri '] = 'HTTP: // localhost/phpmyadmin /';
Note: Do not miss the last backslash (/) and http at the beginning.
4. Search for $ cfg ['servers'] [$ I] ['host'] = 'localhost'; (the default value is usually used, and there are exceptions. You do not need to modify the value)
5. Find $ cfg ['servers'] [$ I] ['auth _ type'] = 'config ';
Debug config in your own machine; if the space on the network uses cookies, now that we have added a URL before, we will change it to a cookie.
My personal suggestion: both on the local network and on the network, we recommend that you set the cookie to be the first in security.
At the same time, when the auth_type value is set to cookie, there is also a need to make the appropriate changes:
$ Cfg ['blowfish _ secret'] = '';
Change to: $ cfg ['blowfish _ secret'] = 'www .blog.com;
Www.blog.com can be defined at will, with no more than 46 characters. If this field is left blank, the above 2nd error will occur: "the configuration file now requires a top secret phrase password (blowfish_secret )".
6. Search for $ cfg ['servers'] [$ I] ['user'] = 'root'; // MySQL user (user name, root in your machine; this is generally your ftp user name on the Internet, which the VM provider will tell you. Do not change it)
7. Search for $ cfg ['servers'] [$ I] ['Password'] = '2016 '; // MySQL password (123456 changed to the user password used to connect to your MYSQL database)
8. find $ cfg ['defaultlang '] = 'zh'. (select the language. zh indicates the meaning of Simplified Chinese) $ cfg ['defaultcharset'] = 'gb2312)
Now, phpMyAdmin has been configured. You can enable http: // localhost/phpmyadmin/to access the convenient and convenient graphical management software phpMyAdmin. For other options in the configuration file that are not mentioned in this article, you don't have to worry about it or modify it. The specific operations on phpMyAdmin are not covered in this article. However, the graphical interface is easy to understand and will be used for a while.
The following describes three problems that flymorn encountered during phpMyAdmin installation and configuration.
The first problem: "The mcrypt extension cannot be loaded. Check the PHP configuration ".
1. the Mysql database is not correctly installed, and Mysql-related services are not started in the system service.
2. libmcrypt is missing in the system32 (C: \ windows \ system32) Directory of the system. dll file. The solution is to find libmcrypt under the php Directory. dll, and libmcrypt. copy the dll to the C: \ windows \ system32 directory and restart the Web service.
3. PHP under the php Directory. in the INI file, the previous ";" in "; extension = php_mcrypt.dll" is not removed, so the corresponding function cannot be used. The solution is to open php. INI file, find it; replace extension = php_mcrypt.dll with extension = php_mcrypt.dll // remove the previous one to make it take effect.
4. the Mysql directory has no read permission. The correct directory permission is as follows:
Full administrator control
Full system control
User reading and running
All other user permissions can be deleted (or retained, but the security is not high, it is recommended to delete), and then restart the MYsql service and Web Service (it is recommended to modify this item and then restart the server ).
5. If none of the above methods works, use this method: desktop> my computer> right-click Properties> advanced> environment variables> system variables> New
Name: phpdir
Value: C: \ php (what directory is your PHP)
Second question: "the configuration file now requires a top secret phrase password (blowfish_secret )"
Make sure that the correct settings are made in the config. default. php file:
$ Cfg ['servers'] [$ I] ['auth _ type'] = 'cooker ';
At the same time
$ Cfg ['blowfish _ secret '] = 'www .blog.com'; // (you can leave this value empty if you want to write it)
In fact, this problem is really depressing. If I did it according to the configuration method I mentioned above, it would not prompt this error. After more than two hours of modifying the config. default. php configuration file, I always indicated this error, almost reaching the edge of the crash.
Then, Ling Guang suddenly found that when I changed the auth_type authentication method to http and changed it to config, this error always occurred when I opened the page. That is to say, the authentication mode has changed and does not work for phpmyadmin, is phpmyadmin affected by other configuration files?
I immediately came to the phpmyadmin root directory and found that a config. sample. inc. php file exists under the root directory, and a config. inc. php file exists !! This is a configuration file of the old version. It turns out to be a ghost of this file. Immediately delete config. inc. php and go to the debugging page. The error disappears! Solve the problem.
It seems that the config. inc. php configuration file Priority Ratio/libraries/config. default. the php configuration file is high. The system first calls the configuration file in the root directory, and then the configuration file in the libraries folder. This problem has been so long and I am sorry. The solution is always done. Just breathe a sigh of relief.
Third question: "#2003-the server has not responded ".
Most of these problems occur when the MYSQL database is not started. We recommend that you directly start MYSQL in the control panel-management tools-service. You can run a process such as running mysqld-nt.exe on the task manager. If yes, mysql is started.
These problems will not happen. However, for new users, for example, if I first encountered a solution, I usually searched everywhere. If a lot of methods on the Internet are not applicable, I feel helpless. I suggest you read the document carefully and refer to the solutions provided by our predecessors. Although they may not be used, they will inspire you. If you have more hands-on and more tests, you can be overwhelmed without any problems. I am optimistic about you ^__ ^
Problems:
Cannot start session without errors, please check errors given in your PHP and/or webserver log file and configure your PHP installation properly.
Change the value of session. auto_start in php. ini to 1 (start). The default value is 0 (disabled)
The following error occurs when you open phpmyadmin:
Cannot start session without errors, please check errors given in your PHP and/or webserver log file and configure your PHP installation properly.
Other programs are connected normally and the environment is 2003 II6.
Create a folder tmp in the php Directory
Find the session. save_path line in php. ini and set it to session. save_path = "C:/php/tmp" to remove the semicolon. OK
None of the materials found on the Internet are correct. All those people thought it was a problem with extension = php_mbstring.dll !!!