WordPress.org

Ready to get started?Download WordPress

Forums

Always get ERROR: The username and password field is empty. (9 posts)

  1. jono181
    Member
    Posted 6 years ago #

    The only problem is these always show up when I go to login. I can login and logout perfectly fine and there are no problems except I just don't want to have to look at it every time I go to login.

    ERROR: The username field is empty.
    ERROR: The password field is empty.

    Should I edit wp-login.php to remove the lines or how can I get rid of this for good?

  2. jono181
    Member
    Posted 6 years ago #

    Anyone?

  3. jono181
    Member
    Posted 6 years ago #

    Can anyone help out here.

  4. jono181
    Member
    Posted 6 years ago #

    can i get a help now

  5. Kalen
    Member
    Posted 6 years ago #

    i've had the same problem since i upgraded and received no support/answers.

  6. ccsimmons
    Member
    Posted 6 years ago #

    i'm getting this error now, too. i started out with 2.3.1 just a few weeks ago without the error. i installed several plugins tonight and now here it is: "ERROR: The username field is empty."

    anyone?

  7. fonetik
    Member
    Posted 6 years ago #

    I am seeing this same error after upgrading to WordPress 2.3.2, but only on my production server, not on my localhost machine.

    After some investigation, the actual problem has something to do with the PHP _POST variable, which is one of the variables that allows access of HTTP data from Apache in PHP. Even though normal page requests show up in the Apache log as HTTP GET's (as they should), on these requests the PHP _POST variable is set as if the request was actually an HTTP POST (which is what is used to submit a form, such as a username / password form). So to WordPress when you load wp-login.php for the first time it looks like you already had it loaded and then clicked submit with an empty username and password.

    I have not figured out a resolution for the problem, but it is much more than a superficial aesthetic issue, so merely removing the lines from wp-login.php is not actually a fix.

    I'm not sure how many problems this issue causes, but they are not just limited wp-login.php. I do know that the new Canonical Pretty URL rewriting in 2.3 checks requests for their type and does not attempt to rewrite URL requests that come in an HTTP POST. Since this problem makes all requests look like POSTs, it entirely disables that feature.

  8. fonetik
    Member
    Posted 6 years ago #

    Problem Found
    At least in my case, this problem was caused by Ryan Duff's contact form plugin (wordpress bug). The plugin uses _POST to store data for the plugin, so even when it is not an HTTP POST request, it can look like it is to WordPress.

    Solution
    Of course you can always fix this by simply disabling the plugin. To keep the functionality, the plugin has to be modified so that it uses normal PHP variables for storage instead of storing things in _POST. I'll ping the plugin developer on this front.

  9. fonetik
    Member
    Posted 6 years ago #

    Actually Ryan Duff appears to MIA, web wise, but there are a plethora of Contacts Form plugins by others, so I suggest using one of those.

Topic Closed

This topic has been closed to new replies.

About this Topic