Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall
This article is suitable for the object: After installation can not login backstage, enter the username and password still jump to the landing page, unable to enter the background, no error code to display. If your problem is that you cannot log in after the upgrade and the error code is displayed please refer to the http://www.baibanbao.net/?p=165 solution
The following two paragraphs is my solution to the whole process, I am a rookie, also not familiar with WordPress, so the more ridiculous to solve, walked a lot of detours, more nonsense, can skip directly to see the solution behind, if you can also look at the time.
(WordPress, installed yesterday evening, because it is in school, the night 11 o'clock lights out, my notebook is also a quick consumer of electricity, no way school campus network speed slow, not to the lights to upload such as snail, can only use the time after the lights up the site update content, because it is a new site, All aspects of the content must be made manually, too slow, so want to build a blog, first put the content on the blog and then slowly do, decided to install a WordPress, because I am a rookie, WordPress also do not understand, after the upload, uploaded to the WWW directory, spent more than 40 minutes, And then, unfortunately, the battery was left with 10 minutes of power, because of the fear of getting up and then the internet is too slow, I decided to install the first and then, automatically create config step-by-step is also very smooth, but to the most critical step, when installed to the database, suddenly computer shutdown, my heart pulled cool, I don't know if it's loaded, and I go to bed.
The next morning to get up, ready to login to WordPress look, enter the user name and password found that the Web page is jumping back to the landing interface, tried several times is so, I thought it is the user name or password is wrong, the first to look in the mailbox, found that right, and to the database to see the password in the database and that the password is not the same, I tried the password in the database, found or not, I think this must be a sudden interruption of the installation, the database has not been generated to cause, the decision to reinstall, installation, I will automatically generate config, installed to the end actually said I installed, first let me clean the database, I will delete the database and then automatically generate config results or not, let me very depressed, I began to search the Internet solution, after looking at the feeling should be the database name of the problem, or manually write a config, so wrote a, install again, sure enough no longer prompted installation, And landed, incredibly still, I was depressed, and I want to, so the installation of so fast, is still no database, I went to the database looked, found that the database did generate, the database is no problem, I have searched a lap, think of it is not because I installed in the WWW directory, When he logged in, he went outside the WWW, so check the database of SiteURL and home found when the directory set up a problem, changed the directory again after landing, really kung fu, backstage finally appeared in front of me, spent a day finally took it out. )
The following are the specific resolution processes:
1 Open phpadmin First, select xx_opition from the table on the left
2 query in Xx_opition, enter in the query box
SELECT * from ' mn_options ' WHERE ' option_name ' in (' SiteURL ', ' home ') LIMIT 0,30
3 after the query modified SiteURL home point, if you are installed in the WWW directory, and you bind your domain name in the WordPress folder, at this time SiteURL home is generally http:******/wordpress, Delete WordPress only http:****** Left
4 Landing again, should be no problem
Another in this to do a small ad, I blog www.meta-news.cn just started building has not written anything, publicize my other station www.wishhome.com.cn bbs.wishhome.com.cn classical culture station, also just do,
If the above can not be resolved, please contact me QQ543944181 or message
(another enclosed in the white blackboard in the update can not be landed after the solution)
(How I solve the problem of WordPress can not login
Published by Wangpeiat 12:26 am under
Before and after spending three nights, I finally solved the WordPress upgrade, the user name, password are correct, but can not log on. In order to let the later person does not eat two times bitter, does not suffer two stubble crime, I put the detailed process and the idea which the solution, records as follows.
I. Description of the problem
This problem, there are several ways to describe, in order to allow search engines to find this article, I have a variety of commonly used terms are collected as follows:
1, with symptoms named, such as: WordPress can not login, password correct, login, lock to WordPress, you can access, unable to login;
2, has the origin name, for example: WordPress upgrade error, wordpress2.6 upgrade can not login ...
3, there are error statements named, this way the most:
1) warning:invalid argument supplied for foreach () ...
2) capabilities.php on line 31
3) Warning:cannot Modify header Information-headers already sent by (output started. ...)
4, a famous French written solution, is named: Invalid argument supplied for foreach () in Wp-capabilities.php:case cracked!
(It should be pointed out that although this article is a lot of search, but very misleading, killing a lot of people, I think completely in the nonsense!)
5, have to feel the pain of the name: God, I do not log on the blog, Help Ah, snow somersaults kneeling beg ...
Search by this name, snail Girl can not help you.
II. Error Statement
Error message In addition to the statements described above, there are other forms, the trial collection is as follows:
1, my error message:
Warning:invalid argument supplied for foreach () in/homepages/23/d208744272/htdocs/wp-includes/capabilities.php on Line 31
Warning:cannot Modify header Information-headers already sent by (output started at/homepages/23/d208744272/htdocs/wp- INCLUDES/CAPABILITIES.PHP:31) in/homepages/23/d208744272/htdocs/wp-includes/pluggable.php on line 552
Warning:cannot Modify header Information-headers already sent by (output started at/homepages/23/d208744272/htdocs/wp- INCLUDES/CAPABILITIES.PHP:31) in/homepages/23/d208744272/htdocs/wp-includes/pluggable.php on line 689
2, the following are very similar, but there must be this sentence:
Warning:invalid argument supplied for foreach () in/home/user/wp/wp-includes/capabilities.php in line 31
Third, the cause of error
For now, most of this is happening when upgrading to WordPress, not only from 2.5 to wordpress2.6, but also from 2.2 or lower.
There are also cases where this error occurs during installation. This is very rare.
Iv. Causes of the error
I do not understand the technology, the Internet has a variety of statements, there is said to be uft-8 code conversion out of the question, some people say that into the death cycle.
It's not important, it's the solution, isn't it?
Modify the character encoding method, or set names UTF8 method
This approach, the most online. The solution provided is:
The first step: using the phpMyAdmin background, the character encoding is modified to utf-8. Note here, if you are using mySql4.0 words, when you change the character into Utf-8, it will show the next time gb2312, do not take it, in fact, has been changed, my experience is this.
It is also said that the database should also be set "collation" as "utf8_general_ci": Because in the new server to build the database, did not specify it as Utf-8, not set collation, so you need to set the database character set.
To execute a command:
ALTER DATABASE MyBlog
Character set UTF8;
Then in the "Operation" or database phpMyAdmin landing page set collation as "Utf8_general_ci."
Step Two: Modify/wp-includes/wp-db.php this file.
This school of thought, the Fault in the wp-db.php, did not set a good utf-8 for the character set, resulting in a series of tragedies. Therefore, you must modify this file. This school also has subordinate three branch schools:
Genre One: in $THIS->DBH = @mysql_connect ($dbhost, $dbuser, $dbpassword); followed by $this->query ("Set names ' utf8′"); Pay attention to English punctuation.
The school believes that the reason for the error is wp-includes/capabilities.php inside $this->roles This array to get is garbled.
Genre Two: That is, the French people who harm the program, he thought should be in the above agreed position, plus this statement: mysql_query ("SET NAMES ' utf8′");
Genre Three: Others claim $this->query ("Set names ' utf8′"); This statement should be added to another location in the wp-db.php, plus another code. The reason why I have not listed it in detail is that it is ineffective.
I have tried the above three ways, and finally retained the genre one approach.
But I strongly doubt the effectiveness of this approach!!
Six, the law of nonsense, also known as Inspection wp_options table method, also known as the Wp_user_roles method
This method was invented by the French, he said, in the phpMyAdmin, open the Wp_options table, find a wp_user_roles, found a French strange characters, Abonnã©, he thought it was the small hat damage to the process of death cycle, and then change it into English characters , and immediately magically good.
The Frenchman also said a quote from Archimedes: eurêka! , Greek, I found it!
In fact, this approach is the most harmful. I followed the 3-kilometer code carefully and changed all Chinese into English, and the results remained unchanged. I'm not the only one who's been misled into wasting time like this.
Vii. individual success laws, also known as the elimination of cookies
Some people proudly announced that the solution to the wordpress2.6 upgrade can not be landed after the problem is to remove cookies. I tried, and found this method ineffective.
But it inspires me that sometimes your unexpected solution is positive.
Viii. effective method, also known as Turkey patch
In total despair, I did a few things: remove wordpress2.6, change back to wp2.5.
The second attempt database inverted trousers no fruit, I hold to try the way, found this post.
This is a small patch written by the Turks, and he says it works only for the 2.3.X version. But according to my experience, subsequent versions should also be compatible.
So I downloaded this plugin, http://file.dmry.net/blog/01/wp_user_roles_yama.zip
After decompression, place it under the WordPress installation root directory. This is what it looks like: (http://your_blog_url../wp_user_roles.php)
And then typing the above URL: http://your_blog_url../wp_user_roles.php
Display are all strings.
And so the dust settles, I can't believe, I really did, and I can freely login to my beloved WordPress. )