Security Alert: 26 BuddyDev accounts compromized in brute force attack.

BuddyDev

Search

[Resolved] Buddypress disabling system

Tagged: 

  • Participant
    Level: Initiated
    Posts: 7
    Peter Fae on June 5, 2020 at 7:12 pm #30506

    I’m having an issue. Whenever Buddypress is disabled, it disables the sites in the network with WSOD.

    Example – BP is network-activated. Yet when I deactivate it, every site in my network goes white with a critical error.

    If I activate it on *specific* sites as compared to network-activation, those sites work, but the others don’t.

    I haven’t been able to discover the cause of it. I’ve tried removing bp-custom, looked through wp-config, deactivated all other plugins, not really sure. Could use some help as it’s messing up my network and i’d like to explore the Multiple Buddypress installs in a multisite plugin here on Buddydev.

  • Keymaster
    (BuddyDev Team)
    Posts: 24706
    Brajesh Singh on June 5, 2020 at 7:32 pm #30507

    Hi Peter,
    Welcome to BuddyDev.

    The reason for WSOD seems related to a BuddyPress depended plugin or theme.

    is there any chance you have some BuddyPress dependent plugin network active? or individually active on all sites?

    Regards
    Brajesh

  • Participant
    Level: Initiated
    Posts: 7
    Peter Fae on June 6, 2020 at 12:53 am #30510

    I have done the technique where one moves all active plugins into a temporary directory and have left only buddypress activated and I still get the error.

    Would you suggest me going into the sub-sites and personally deactivating the plugins there? I thought moving through out of the folder directory is the most efficient.

    (thank you for your quick response. I would very much like to activate the Multiple Buddypress plugin and explore more of Buddydev this has to get dealt with first 🙂 )

  • Keymaster
    (BuddyDev Team)
    Posts: 24706
    Brajesh Singh on June 6, 2020 at 6:02 am #30513

    Hi Peter,
    Thank you for your interest in using our plugins in future.

    Here is a simple way to find out

    1. Open your wp-config.php and look for the following line

    
define( 'WP_DEBUG', false );

    Please change that to

    
define( 'WP_DEBUG', true );

    and add the following line too

    
define( 'WP_SANDBOX_SCRAPING', true);

    Now, if you open the site, It will show you the actual error. Please change back wp-config.php to your original state and let me know the error.

    Regards
    Brajesh

  • Participant
    Level: Initiated
    Posts: 7
    Peter Fae on June 6, 2020 at 6:41 pm #30540

    Well, that was a doozy. What you suggested didn’t do anything but I had an intuition to check in with WPENGINE where we’re hosted. After a bunch of investigation (including checking my wp-config and deleting the bp-custom.php files on the server, we discovered something in mu-plugins that said this –>)

    [Sat Jun 06 18:06:26.540445 2020] [php7:error] [pid 2668] [client 38.140.212.19:55930] PHP Fatal error: Uncaught Error: Call to undefined function bp_loggedin_user_domain() in /nas/content/live/intothemythica/wp-content/mu-plugins/mu.php:12\nStack trace:\n#0 /nas/content/live/intothemythica/wp-includes/class-wp-hook.php(287): {closure}(”)\n#1 /nas/content/live/intothemythica/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)\n#2 /nas/content/live/intothemythica/wp-includes/plugin.php(478): WP_Hook->do_action(Array)\n#3 /nas/content/live/intothemythica/wp-includes/general-template.php(2884): do_action(‘wp_head’)\n#4 /nas/content/live/intothemythica/wp-content/themes/pro/framework/legacy/cranium/headers/views/global/_header.php(15): wp_head()\n#5 /nas/content/live/intothemythica/wp-content/themes/pro/framework/functions/frontend/view-routing.php(182): include(‘/nas/content/li…’)\n#6 /nas/content/live/intothemythica/wp-content/themes/pro/framework/functions/frontend/view-routing.php(55): X_View_Router::render(‘/nas/content/li…’, Array, true)\n#7 /nas/content/live/intothemythica/wp-content/themes/p in /nas/content/live/intothemythica/wp-content/mu-plugins/mu.php on line 12, referer:

    when we removed it, things started working again.

    It was so strange, before, when I was logged in and BP was activated, WSOD. Alternatively, when I was not logged in and buddypress was activated, site worked fine. It was related to login.

    *breathes*. Okay.

    Brajesh you are so helpful. Thank you so much for offering support. You’ve been the most noble and service-compassion driven of the buddypress people i’ve spoken to.

    I respect your expertise deeply. Would you please tell me what that code was doing which was causing the error?

    Also, as I mentioned i’m wanting to create multiple networks within the space and planning on implementing the Multiple Buddypress networks plugin that you created. I’ve opened a ticket in question on this. I would very much appreciate the assistance on that as well just as a ‘pre-sale’ to getting that and working things out as I do not understand BP as well as You *bows*

    other ticket –>https://buddydev.com/support/forums/topic/multiple-bp-networks-on-multisite/

  • Keymaster
    (BuddyDev Team)
    Posts: 24706
    Brajesh Singh on June 7, 2020 at 12:31 pm #30548

    Hi Peter,
    Thank you for the reply.

    I am glad you found the issue. The above suggested code should have printed the error. if they did not, most probably your host puts extra customizations.

    From the above code, All I can guess is there was some code in your mu.php which was injecting something related to BuddyPress in the head tags of the site.

    Regards
    Brajesh

The topic ‘ [Resolved] Buddypress disabling system’ is closed to new replies.

This topic is: resolved