Title: wp-login.php issues
Last modified: May 5, 2022

---

# wp-login.php issues

 *  Resolved [shawfactor](https://wordpress.org/support/users/shawfactor/)
 * (@shawfactor)
 * [4 years ago](https://wordpress.org/support/topic/wp-login-php-issues/)
 * Any functionality that calls bp_current_component() is throwing an error on wp-
   login.php. I understand why bp_parse_query has not run. BUT throwing errors for
   this makes no sense as bp_parse_query will never run in many wordpress contexts
   and getting a sensible answer for bp_current_component() may be required
 * I realise this is just a warning but I always run debug everywhere and getting
   errors (that are not really errors) in the frontedn makes no sense
 * do_action(‘login_form’), WP_Hook->do_action, WP_Hook->apply_filters, LH_Facebook_login_plugin-
   >add_login_button, bp_is_register_page, bp_is_current_component, apply_filters(‘
   bp_is_current_component’), WP_Hook->apply_filters, BP\Rewrites\bp_is_current_component,
   BP\Rewrites\bp_current_component, BP\Rewrites\_was_called_too_early.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [shawfactor](https://wordpress.org/support/users/shawfactor/)
 * (@shawfactor)
 * [4 years ago](https://wordpress.org/support/topic/wp-login-php-issues/#post-15617166)
 * Note unlike my other support posts, fir this one I do have plugins other than
   Buddypres and Bp rewrites.
 * The point I am trying to make is that what they are trying to do is depeendient
   on knwing if th the current request is for a buddypres component, Obviously thsi
   could be avoided by using different functions for adding functionality to buddypress
   screens but that seems overkill so having bp_current_component() return a sensible
   value everywhere makes sense to me
 *  Plugin Author [Mathieu Viet](https://wordpress.org/support/users/imath/)
 * (@imath)
 * [4 years ago](https://wordpress.org/support/topic/wp-login-php-issues/#post-15620959)
 * Hi thanks for your report. I agree BP Rewrites shouldn’t display a notice there.
 * On the other hand, it makes no sense to check for BuddyPress globals when hooking
   to `do_action('login_form')` as these globals are not defined into this context
   at all, with or without BP Rewrites.
 *  Plugin Author [Mathieu Viet](https://wordpress.org/support/users/imath/)
 * (@imath)
 * [4 years ago](https://wordpress.org/support/topic/wp-login-php-issues/#post-15634043)
 * This will be fixed at the next plugin release:
    See [https://github.com/buddypress/bp-rewrites/pull/38](https://github.com/buddypress/bp-rewrites/pull/38)

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘wp-login.php issues’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/bp-rewrites_ececec.svg)
 * [BP Rewrites](https://wordpress.org/plugins/bp-rewrites/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/bp-rewrites/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/bp-rewrites/)
 * [Active Topics](https://wordpress.org/support/plugin/bp-rewrites/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bp-rewrites/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bp-rewrites/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Mathieu Viet](https://wordpress.org/support/users/imath/)
 * Last activity: [4 years ago](https://wordpress.org/support/topic/wp-login-php-issues/#post-15634043)
 * Status: resolved