Problems with Human Check and wp-login.php

Deprecated: /home/bobbingw/public_html/wp-content/plugins/oik/includes/ is deprecated since version 3.2.1! Use includes/bw_posts.php instead. Please use includes/bw_posts.php in /home/bobbingw/public_html/wp-includes/functions.php on line 5049

We’ve recently been working on a problem where the user ends up on a White Screen Of Death (WSOD) when the WordPress login form was supposed to have been processing the request.

It happens in the following situations.

  1. User visits a page where the login form’s HTML is similar to that shown below. Note: The values of action=site_url/wp-login.php and method=post.
  2. The “humancheck” cookie does not exist.

HTML for the inline login form

The HTML generated by the standard WordPress login api ( wp_login_form ) is as follows.

<form name="loginform" id="loginform" action="" method="post">
<p class="login-username">
<label for="user_login">Username</label>
<input name="log" id="user_login" class="input" value="" size="20" type="text">
<p class="login-password">
<label for="user_pass">Password</label>
<input name="pwd" id="user_pass" class="input" value="" size="20" type="password">
<p class="login-remember"><label><input name="rememberme" id="rememberme" value="forever" type="checkbox"> Remember Me</label></p>
<p class="login-submit">
<input name="wp-submit" id="wp-submit" class="button-primary" value="Log In" type="submit">
<input name="redirect_to" value="" type="hidden">

Login form looks like this

If you’re not logged in then the login form should be displayed.

Problem workaround

  • For sites with wp-members it’s possible to use the standard WP-members solution to block the post/page. The input from the WP-members form does not get submitted to wp-login.php so it works without being intercepted by the Human Check.
  • Ask the hosting company to remove the cookie logic for this site.


  • The WP-members blocking method doesn’t appear to work on parent pages… which is one reason why we were using – as belt and braces.
  • The problem occurs even if you attempt to ensure that naked domains are redirected to the www version. e.g. gets redirected to

Problem resolution

  • Ask the hosting company to alter the cookie logic so that the “Are you human?” page does appear to this legitimate user.