bp_nav was called incorrectly

  • Resolved Daniel

    (@ddumondgmailcom)


    6 years, 6 months ago

    Hello,

    I recently noticed an error in my member list at the bottom of the second paginated page that read:

    There has been a critical error on your website.

    Learn more about debugging in WordPress.

    When I activated debugging I get the notice “bp_nav was called incorrectly”

    After some research, I learned it’s due to depreciated code in a plug-in.

    When I deactivate “BP XProfile WordPress User Sync” the error goes away.

    Does anyone know what might be causing this?

    Thanks in advance.

    Dan

    • This topic was modified 6 years, 6 months ago by Daniel.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Christian Wach

    (@needle)

    6 years, 6 months ago

    @ddumondgmailcom This plugin does not call bp_nav so I’ll need you to do a bit more digging to discover why this is happening for you and why disabling this plugin might cause the notice to disappear.

    First off, a PHP notice will not cause “a critical error”. If you enable WP_DEBUG in your wp-config.php file and also add:

    define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );

    then you will find detailed logs in wp-content/debug.log. This should help you identify the source of the fatal error.

    Second, which version of BuddyPress are you using? Any other plugins? If so, what versions are they on?

    Thread Starter Daniel

    (@ddumondgmailcom)

    6 years, 6 months ago

    Hi Christian,

    I owe you a big apology for jumping the gun on this one… The debug log was a HUGE help.

    Deactivating your plugin did resolve the error, HOWEVER with your plugin active and another disabled, the error was ALSO resolved.

    This was the problem:

    PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 81920 bytes)

    So it looks like I’m pushing my resources here.

    As you suggested, the bp_nav issue was not related to a critical error, rather the culprit to this was my bp-custom.php file which I did not consider when troubleshooting.

    I humbly retract my original post and thank you for your time and guidance in pointing me towards the right direction.

    Best regards,
    Dan

    Plugin Author Christian Wach

    (@needle)

    6 years, 5 months ago

    @ddumondgmailcom Happy to hear you’ve solved the problem Dan.

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

The topic ‘bp_nav was called incorrectly’ is closed to new replies.