Multisite with Buddypress: Community Add-on crashing top site

Very sorry with letting this slip by so long without response. My apologies.

Curious if you have BuddyPress network enabled as well or if that’s just on the main site. It may be a case of needing to leave it activated just on the same site that BuddyPress is in. However, I also have to wonder if that’d prevent the badges from being available in the ways you want.

Regarding the odd redirecting behavior, that’s really really odd because the Community Add-on shouldn’t be doing anything that should affect such things. So I’m at a loss with that part.

Thanks for your followup.

We have Buddypress as part of the COmmons inm a Box Package. So the Buddypress plugin isn’t actually listed in our plugins area, but in the CBOX plugins, whichis Network Activated.

I have BADGE-OS Networks Activated.

But when I go to Network activate the Community Plugin, it redirects me to a subsite again. I am not able to get to the commons.uaa.alaska.edu main site or even the dashboard.

I have to go back into the Network Admin to de-activate and then my Commons main site comes right back up.

Any ideas?

Micheal,

An alternate test is that I deactivated Badge OS Networkwide, and activated it just on the Commons top site. I then activate Community on the Commons top site, and it crashes the site again. Send me to another subsite. The fix is then that I have to go into network Admin and delete community plugin (since I cant get into Commons Dashboard). Then I can immediately access Commons.

We have pulled both Badge OS and community completely out and reinstalled a few times to no avail.

I am testing this all in our staging environment, and can give you access if you would like to check this out (please?). Thanks!

I frequently try not to get to that point, but this crashing has me very curious.

Since there’s apparent high risk of crashing and php errors that could lock out of the admin as well, I’d request some level of ftp access just in case, plus the ability to turn on WP_DEBUG.

If you could email me those details and create an admin, maybe super admin, account for me, I can take a look. just use “michael” for the WP user name, [email protected] for all parts, and do a random password that I can log in and change later.

Resuming support here.

I am definitely seeing a lot of issues going on, but I’m admittedly not 100% sure it’s just from BadgeOS. The problem with that theory is that I am not daring enough to deactivate all of the plugins to see if it behaves afterwards. I’m also curious if the the lack of full network upgrade may be affecting it at all.

I’m very likely to bring in one of our BadgeOS developers to see if we can figure out what’s going on together. Hopefully a little bit tonight but I can’t guarantee with the weekend looming.

Strange that I’m not seeing any errors, it’s just changing a lot of things in the background.

scfrick, does this sound like what you’re dealing with?

https://github.com/opencredit/BadgeOS-Community-Add-on/issues/11

Yes. Sound exactly like what is happening.

yes. Although I don’t know if it happened after I changed the BadgeOS menu settings like the other user pointed out, but I did enable that setting.

Found a solution to this issue off-forum. Should be going out in next major release.

I did a whole new setup, and I haven’t checked this little box. The plugin works. It might come from that definitely.
On my side I still need to have the badges, points and achievement activity available for the whole community and sub sites.
With this curent setup. BadeOS is working but badges are specific to each website.
Hope that helps, looking forward to the release.

Having one set of badges for each site in a network is never going to be an easy thing because of how post types work. Each site gets their own posts/postmeta table, and thats where the achievements are stored. I think we have one user trying to do something with this by copying data between the sites, but I have no hands on experience with that or knowledge of how well that’s going.