@MariusOoms – no need to apologize. It’s the price we pay to use open source. If it’s a mission critical feature, upgrades can be done on a test server or backups allow for rolling back until all is good to go live. It’s appreciated that you got this plugin established. Anything you can do in the future will also be appreciated.
When upgrading for bp 1.2, take a look at JJJ’s comments regarding hooking dependent plugins in to bp_int. It sounds like it’s the preferred way (over what I posted earlier) to load bp first:
https://buddypress.org/forums/topic/important-plugin-devs-read-this
Best of luck with your move!
@nonegiven – I’m now having no problems with groupblogs. Old Group Blog pages are recognized and all the Blog Menu Options within the Group are associated with the correct group blog. I’d also love to see the groupblog function as part of the core bp.
@Andy – Still confused by your comment but it may not matter given the change JJJ has made to the trunk.
Ok, I found the reason and am not sure if it could possibly be a bug in bp 1.2, maybe someone more knowledgable could have a look?
Basically it was caused by the groups_add_forum_fields_sql, groups_add_forum_tables_sql and groups_add_forum_where_sql filters being applied to other components as well – which I think is not correct or at least I don’t see what sense it would make.
The code which looks wrong is on line 60 of bp-groups-filters.php:
if ( ( $bp->groups->current_group && ‘public’ == $bp->groups->current_group->status ) || !$bp->groups->current_group ) {
When removing the “!$bp->groups->current_group” (which looks wrong to me) part it works for my component. I first tried to remove the filters but somehow that did not work.
I FIXED my issue by following Andy’s instructions here:
https://buddypress.org/forums/topic/important-plugin-devs-read-this
Quick solution:
Add the following to the top of groupblog.php:
/*** Make sure BuddyPress is loaded ********************************/
if ( !function_exists( 'bp_core_install' ) ) {
require_once( ABSPATH . '/wp-admin/includes/plugin.php' );
if ( is_plugin_active( 'buddypress/bp-loader.php' ) )
require_once ( WP_PLUGIN_DIR . '/buddypress/bp-loader.php' );
else {
return;
}
}
/*******************************************************************/
I am seeing this issue on a new install… I would have thought it would be fixed in the core by now?
Hm, I had to re-install my forum after upgrading. Perhaps it’s in the instructions somewhere, or maybe I did it wrong.
But if anyone else’s forum broke, perhaps they should check if their forums are installed correctly.
“Fatal error with no indication of what the error is.”
Errors are usually suppressed on the front end. did you check your server’s error logs?
“Here is my post on another thread regarding the same issue: https://buddypress.org/forums/topic/cannot-activate-bp-12-fatal-error-cannot-redeclare-bp_loader_activate”
The phrase in there with the big clue is “cannot redeclare” Which means it is being called twice.
Which means likely – stab in the dark guess here – you have two copies of the plugin.
“How come nobody can give me any insite into whats going on”
because you have two posts within 7 hours during a timeframe where a large portion of the volunteers here are sleeping. 
They do that sometimes.
Now I tried reinstalling buddypress and I am still getting the problem. Fatal error with no indication of what the error is. Its messing up my site. Could it be a WPMU problem.
Here is my post on another thread regarding the same issue: https://buddypress.org/forums/topic/cannot-activate-bp-12-fatal-error-cannot-redeclare-bp_loader_activate
How come nobody can give me any insite into whats going on. I’m seriously getting stuck and wanting to abandon buddypress for some other system. 
Arturo ~ It isn’t exactly that simple and this question is more appropriate for in the BBpress forums since you’re working with a standalone BBpress install. Have you investigated this bbpress plugin? The code you’re referring to for bp is bp_member_last_active() & bp_get_member_last_active() in bp-core/bp-core-templatetags/ (#250) it requires the global $members_template from within BP and the bp-forums-templatetags. I don’t have the time to investigate a full solution but I went to the effort of testing a couple functions this morning inside of a standalone for you to see if I could come up with an easy solution, but there isn’t one at the moment other than using the functions inside of _ck_’s members online but you may be sacrificing future compatibility in doing so.
no one can help me? Andy or mods can tell me how to have “active 12 hours, 12 minutes ago” on the forum? thanks!
I am having major problems with spam as well. Ironically it started as soon as I put my link in the showcase thread on this forum. I think the spam bots are looking there for easy targets as well.
Why do people make spambots that don’t even advertise stuff and just waste everyone’s time filling sites with meaningless crap. Is it like they are trying to sabotage Buddypress?
How does one submit domains and sites and IP addresses to spam traps.
@haloid if you want to jump the gun, wrap the elements that are calling “bp_get_total_friend_count” with the following:
<?php if ( function_exists( 'friends_install' ) ) : ?>
{{ li item here }}
<?php endif; ?>
As far as I know, the calls are made in the following places (inside the new default):
/plugins/buddypress/bp-themes/bp-default/activity/index.php
/plugins/buddypress/bp-themes/bp-default/members/index.php
I’m with your brother. Friending is wack for niche networks. Fingers crossed that this is abolished in place more advanced grouping https://buddypress.org/forums/topic/friends-and-groups-for-buddypress-13
UPDATE: I forgot about /group/create.php, which relies heavily on a users “friends” for the invite stage. Lame!!
Thanks for the reply, Windhamdavid. The thing is, I already got forums working fine with my custom component in BP 1.1.3. I just can’t figure out how to convert it to be compatible to the new bp 1.2 even after hours of searching around.
Temporary solution or put
if (!is_user_logged_in())
GO AWAY
on every template page.
It’s beta now?! Whoa! And I see now this happened 2 days ago I’m outta the loop! That’s what I get for bookmarking the forums and bypassing the homepage all the time 
this thread may help – if you’re posting to bb_topics outside of bp via this custom component, then you may need to make some other adjustments.
Also, as per Windhamdavid’s post, continue discussion in https://buddypress.org/forums/topic/how-to-access-to-bbpress-admin-from-buddypress
I’m closing this as we seem to have many threads concerning this exact subject in the last few days.
Thanks, I’m still not seeing a bbpress admin panel, and actually there are bb-config.php files in
The bb-config.php that lurks in /bp-forums/ is intentionally NOT the regular bbPress config file. Open it in a text editor and have a look.
Hi,
I have installed the latest version of buddypress version 1.2 beta and im using this on wordpress 2.9.1. I would like to know how i integrate bbpress v3.1 with wordpress/buddypress. I’ve read many articles on this but all see to take about WordPress MU which i’m not using.
Any help would be appreciated.
Thankyou.
Murphy
bbPress is only up to 1.0.2 so I have no idea what you’re talking about. It’s probably best to make a new thread.
Hi,
I have installed the latest version of buddypress version 1.2 beta and im using this on wordpress 2.9.1. I would like to know how i integrate bbpress v3.1 with wordpress/buddypress. I’ve read many articles on this but all see to take about WordPress MU which i’m not using.
Any help would be appreciated.
Thankyou.
Murphy
Hi,
I think I found tour support request at the MU forums. I just wanted to update the forum over here, too.
The suggested solution to return 400 errors and not 500 for non-existing directories is to search for:
RewriteRule . – [L]
in your .htaccess file and to comment it out:
#RewriteRule . – [L]
This solved the problem for me. But the question is, if this is breaking something else? It seems to work for me so far….
‘M’ gave a solution to fix plugins that broke between 2.8.6 and 2.9.1 at the end of this thread. Haven’t had time to try yet…
This issue was resolved by ensuring that my WPMU wp-config and bbPress bb-config settings matched those described here:
https://bbpress.org/forums/topic/login-integration-issues-bbpress-and-wordpress-mu#post-62274
No sweat. Marked as resolved.
