Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author bettercodes

    (@bettercodes)

    What does the Webserver error log says?

    I have the same issue. When WP debug is enabled, these are the errors I get…

    Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of call_user_func(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /path-to-site/httpdocs/wp-content/plugins/bc-oauth/lib/php-openid/Auth/OpenID/Consumer.php on line 1184

    Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of call_user_func(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /path-to-site/httpdocs/wp-content/plugins/bc-oauth/lib/php-openid/Auth/Yadis/Manager.php on line 416

    In my php.ini I set allow_call_time_pass_reference = On and I’m still getting the blank white screen. Also, I’m running WordPress 3.1 and PHP 5.2.6.

    The only other messages I’m getting are generic deprecated notices.

    Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /path-to-site/httpdocs/wp-includes/functions.php on line 3303

    Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /path-to-site/httpdocs/wp-includes/functions.php on line 3303

    Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /path-to-site/httpdocs/wp-includes/functions.php on line 3303

    Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /path-to-site/httpdocs/wp-includes/functions.php on line 3303

    Maybe the querystring variables aren’t being properly registered with WordPress and are being lost/ignored?

    Finally got a chance to poke around and the white screen fix is VERY easy.

    In bc-oauth-loader.php (btw, proper naming convention for this file should be bc-oauth.php), you simply need to add the following hook:

    add_action('init', 'bc_oauth_init');

    The problem is that the login action is trying to use wp-load.php, but there is no hooked function there to catch the login request. The init function, bc_oauth_init(), is hooked to wp_ajax, which only used by requests sent to /wp-admin/wp-ajax.php – since I don’t know if that’s actually used or not, I simply added an extra hook that allows bc_oauth_init() to catch requests from wp-load.php.

    Everything works great, now.

    ??

    Thread Starter alexef

    (@alexef)

    Thanks Veraxus!

    Did you add:

    add_action('init', 'bc_oauth_init');

    directly above:

    add_action('wp_ajax_bc_oauth', 'bc_oauth_init');

    enderandrew,

    Yes, putting it directly above add_action('wp_ajax_bc_oauth', 'bc_oauth_init'); will work fine.

    Plugin Author bettercodes

    (@bettercodes)

    Thanks you both alexef and Veraxus. I implemented your bugfixing solution into the current version.

    hxmws

    (@hxmws)

    Hi All,

    Thanks for developing a great plugin for authentication I have a quick question for you. We are looking to use the Gmail login option, but would like to limit this so that only users within our googleApps account can authenticate. Is this possible and if so could you please confirm the steps that we would need to take to enable this.

    Thanks
    Matt

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Plugin: BC oAuth] BC auth blank page’ is closed to new replies.