@allenmcgraw – check out this post:
http://is.gd/cTrBB
Locking this thread.
for posts made within a group or outside the buddypress context?
Perplexing? lots of back slapping 
on that link announcement yet 1.2.4 does not work particularly well with 3.0 or particularly badly (to be fair) Why? not necessarily criticizing just rather bemused by BP development and testing.
just taken from the dev meeting logs and 1.2.4 announcement (https://buddypress.org/2010/05/buddypress-1-2-4/)
“This highly anticipated version provides fixes to 74 reported tickets and adds improved support for WordPress 3.0 to help ensure a safe and worry free upgrade.”
So it was supposed to be ready? Very interesting. We’ll there’s at least two of us who know the truth about that statement. It’s too bad. I just started with BuddyPress and with so much attention I expected to see something a little more polished. Am I expecting too much given it’s maturity? I’ll have to evaluate that question a little closer.
remove the plugin completely then, actually I thought it was called bp-twire?
Tweatstream is an option but not necessarily better, it has a fatal showstopper bug that to my knowledge hasn’t been resolved so for a few of us is not an option as it simply does not work!
@nuprn1
Ahhh, that must be it then! Does this go in the bp-custom.php file too or elsewhere and if it does go in custom.php should it be before or after your code?
Thanks!
This is in local testing finding a code solution but thanks for the response.
(…and technically 1.2.4.1 was suppose to be WP 3.0 ready while BP1.3 dependent on features of WP3.0 )
I’d recommend not using Twire.
Try Tweetstream instead:
https://wordpress.org/extend/plugins/tweetstream/
I’ve got something to help you out.
Wait until BuddyPress is 3.0 compatible.
I actually thought it would be out of the gate considering the time frame of the WordPress 3.0 development and the popularity of BuddyPress.
I just tried an upgrade and it was a failure to say the least. One of the issues is what your encountering.
I changed the file name to ‘bp-twire” and then got another fatal error saying that the header is now the problem.. not sure what to do
@walid3 – Could be an incompatibility with WP 3.0. I haven’t checked this to confirm though.
Can anyone else who’s using WP 3.0 with root profiles verify?
[EDIT]
Just upgraded to WP 3.0 and root profiles are working for me.
You could try re-saving your permalink structure to see if that will have any effect.
@aishing – Try putting the code after the register_sidebars code in your theme’s functions.php. Then see if you get an error. Can you please paste the error if you get one?
Btw, you should be creating a child theme to add custom code snippets, otherwise when you upgrade BP, you’ll lose your changes.
nevermind – adding that will cause all 404 pages to default to the activity stream
Hi,
You can remove the Visit random user/group by removing the links in the bp-core-adminbar.php file, found in /wp-content/plugins/buddypress/bp-core/ Its best to remove the lines of code:
<li class="align-right" id="bp-adminbar-visitrandom-menu">
<a href="#"></a>
<ul class="random-list">
<li><a href="root_domain . '/' . BP_MEMBERS_SLUG . '/?random-member' ?>"></a></li>
<li class="alt"><a href="root_domain . '/' . $bp->groups->slug . '/?random-group' ?>"></a></li>
<li><a href="root_domain . '/' . $bp->blogs->slug . '/?random-blog' ?>"></a></li>
</ul>
</li>
This code appears between lines 221-237. Leave the opening function in place, just remove the code between, and including, the <li> and </li>. Save the file, reload the page and the visit links should now be gone.
All the best,
Shane.
@r-a-y
well, actually the define like have no effect at all now, it change the links for all users everywhere in the site to root:
site.com/user
but when I visit it: ” The page you were looking for was not found. ”
seems this define line have a bug, don’t know I f I should give up the all thing or there is another way to make it?
Hi. Thanks for your reply. I apologize if I wasn’t clear. What I mean is that I would like to add items to the CSS using existing CSS elements. For example, The CSS contains the item (div#item-header). I would like to add additional graphics to this such as quotation marks. Do I need to create a new item based on the original element. Say, something like (div#item-header.quote). If I do create a new CSS item based on an existing div element, do I also need to reference this in the html? I am also having difficulty finding the default buddypress template html.
I hope this makes more sense and once again thanks for your assistance.
All the best,
Shane.
@r-a-y thanks for this and I have seen this code before and tried it several times but I cant get it to work…I know its me….Im just not putting it in the right place on the functions.php page. Ive put it at the very start of the page. For example:
function sh_walled_garden()
{
global $bp;
if( bp_is_register_page() || bp_is_activation_page() )
return;
if( ! bp_is_blog_page() && ! is_user_logged_in() )
bp_core_redirect( $bp->root_domain .’/’. BP_REGISTER_SLUG );
}
add_action( ‘get_header’, ‘sh_walled_garden’ );
/* Stop the theme from killing WordPress if BuddyPress is not enabled. */
if ( !class_exists( ‘BP_Core_User’ ) )
return false;
/* Register the widget columns */
register_sidebars( 1,
array(
‘name’ => ‘Sidebar’,
‘before_widget’ => ‘
‘,
‘after_widget’ => ‘
‘,
‘before_title’ => ‘
‘
blah blah……….
Is that correct? Because when I do this I get an error reading.
I just need to know “exactly” where to put it on the page. For example put it between “x” and “y”.
Thanks for getting back to me promptly though…appreciate it.
I’m going to assume you have a stock BuddyPress setup and just enabled the BP Component ->”bbPress Forums – Activates bbPress forum support within BuddyPress groups or any other custom component.” to allow group forums – then no. You can change the BuddyPress templates via a child theme though. ( bp-default/forums and bp-default/groups/single/forum/ )
If you disable
BuddyPress -> Component Setup -> “bbPress Forums – Activates bbPress forum support within BuddyPress groups or any other custom component.”
You won’t be able to post any group forum topics
If you disable
BuddyPress -> General Settings -> “Disable global forum directory?:”
That will remove the tab and /forums index
