• Resolved shawfactor

    (@shawfactor)


    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

    (@shawfactor)

    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

    (@imath)

    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

    (@imath)

    This will be fixed at the next plugin release:
    See 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.