BuddyPress.org

See our blog post at http://bpdevel.wordpress.com/2011/07/31/maintaining-1-2-compatibility-slugs/, too

alphonse.tan, what is the slug/name of the page that you’ve assigned to the “Groups” component in wp-admin > BuddyPress > Components? Changing that should update menus etc

Forums for Groups and Sitewide Forums are definitely working in WP 3.2.1 and BP 1.5.1 and bbPress 2.0
BP Codex – https://codex.buddypress.org/getting-started/installing-group-and-sitewide-forums/

The BuddyPress demo site at http://testbp.org/ is on:
“This site is running the most recent nightly development versions of BuddyPress and WordPress and should be considered mostly stable with a chance of rain.
WordPress 3.3-aortic-disection
BuddyPress 1.6-bleeding
bbPress 2.1-bleeding”

Per your screencast, you’re using WP 3.3 beta 3. Are you using trunk versions of BuddyPress 1.6 and bbPress 2.1 as well? Having asked that, no guarantees until all are stable.

@davidtcarson bravo to your theme.. i am currently using it with a wp 3.2.1 and bp 1.5.. it’s practically working fine.. and i am very happy with it..

there’s just one thing.. i converted all “groups” into “companies” and with the bp-default theme menus each and every link is working.. but with the frisco sub-menu… (please refer to this page..http://www.entrepnegosyo.com/members/alphonse/companies/) you can see that, it is still saying “Groups” and not “Companies”.. i have been searching from within the bp-default theme and within our great theme.. but to no avail..

Any assistance to point me in the right direction would be most appreciated..

Thanks and more power…

I don’t think it will be an issue later on as bbpress is using the page.php templates and get_template to output content. So as long as page.php is included it should work even better on various screens. The main issue when dealing with mobile and WordPress/BuddyPress is header(nav) and sidebar.

Maybe bp-default should be rebuilt from ground up with mobile in mind for 1.7’s templating?

voted x3 on this too!

The other thing I was thinking about looking at was this….

http://stescodes.com/invitefriends.aspx

a one-off payment but I’m unsure how complex it would be to integrate…when I asked the developer about buddypress/wordpress they said;

“It is very easy to integrate our code, we provide sample code in working condition. Once you run the code by settings the API configuration based on your account, you will be able to integrate with your code easily.

Furthermore, we provide developer guide documentation and also tutorial videos too.

Note: Please let us know if you need any help or further details.”

….not much info lol!

I’m not sure what you mean – but according to https://codex.wordpress.org/Function_Reference/wp_nav_menu you could have ` ‘fallback_cb’ => false,`

I don’t know how you are doing the mobile menu, but couldn’t you just have $current_user logged in and out mobile menus?

If someone can guess the page such as activity, then just hiding the menu won’t stop them getting in anyway.

The essence of what you want is to store a piece of usermeta called something like ‘user_type’, where each user is either ‘player’ or ‘team’. The tricky part for your purposes will probably be that BuddyPress (or WordPress for that matter) is not designed to allow one user to act “on behalf of” another user – or, as you put it, “players interact only through their respective teams”. I take it that means that player1 would be able to send a message and have it come from team1. But this is going to be quite tricky, as it’ll mean, essentially, filtering the current user id in hundreds of places throughout BuddyPress.

Check out this plugin by Boone:
https://wordpress.org/extend/plugins/unconfirmed/

How about the following (in the header?) instead of what’s there (bp 1.5.1)
`// https://codex.wordpress.org/Function_Reference/wp_get_current_user
$current_user = wp_get_current_user();
if ( 0 == $current_user->ID ) {
wp_nav_menu( array( ‘container’ => false, ‘menu_id’ => ‘nav’, ‘theme_location’ => ‘secondary-menu’, ‘fallback_cb’ => ” ) );
// Not logged in.
} else {
wp_nav_menu( array( ‘container’ => false, ‘menu_id’ => ‘nav’, ‘theme_location’ => ‘primary’, ‘fallback_cb’ => ” ) );
// Logged in.
}
`
? (wrapped in “ tags)

okay so I’ve done some digging and found – nav-menu.php
copied it to my child themes folder and created two seperate menus in my admin dashboard.

I found this code for the menu config: here: https://codex.wordpress.org/Function_Reference/wp_nav_menu

---

`<?php
if ( is_user_logged_in() ) {
wp_nav_menu( array( ‘theme_location’ => ‘logged-in-menu’ ) );
} else {
wp_nav_menu( array( ‘theme_location’ => ‘logged-out-menu’ ) );
}
?>`

---

Am I getting warm..?

If so, just two questions remain..

a) where in: nav-menu.php do I add the above code..?

b) Does the above code need to be wrapped at all..?

Kind regards in advance

`’menu_id’ => ‘nav’, ‘theme_location’ => ‘primary’, ‘fallback_cb’ => ‘bp_dtheme_main_nav’ ` pertains to the adoption of the wp_nav_menu function which allows users to create their own menu. This falls back to wp_page_menu and bp_nav_menu.
https://codex.buddypress.org/extending-buddypress/how-to-set-up-your-main-site-navigation-using-the-built-in-wordpress-menus/

Goodbye, headaches. Hello, menus!

Im working in new framework for wordpress+buddyperss for for building web services, the plugin expose functionality of wp and any other plugins installed in wp to other web sites and desktop applications. i will share a beta version soon.

activity/index.php = open it up with a text editor. At the very top of the file,
replace:
`

`

Note that I did not include “ at the top of the file and therefore did not include “ at the bottom of the file.

Save /activity/index.php file and do the same on the remaining 15 files as listed here https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/#tplfiles
… except for /registration/register.php where you do the same at the top of the file but at the bottom of the register.php file, the replacement is:
`
<?php if (get_option('professional_integration_single_bottom') ” && get_option(‘professional_integrate_singlebottom_enable’) == ‘on’) echo(get_option(‘professional_integration_single_bottom’)); ?>

jQuery(document).ready( function() {
if ( jQuery(‘div#blog-details’).length && !jQuery(‘div#blog-details’).hasClass(‘show’) )
jQuery(‘div#blog-details’).toggle();

jQuery( ‘input#signup_with_blog’ ).click( function() {
jQuery(‘div#blog-details’).fadeOut().toggle();
});
});

`

Save all and upload BP folders with revised template files to server wp-content/themes/professional/

Just to clarify
– Was “The Morning After” theme activated when you installed and activated the BP Template Pack plugin and ran Appearance > BP Compatibility?
– Did you use the first method (16 template files change) or the second method (header-buddypress.php etc) to fix alignment? https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/#tplfiles

Open up TMA’s header.php, page.php and footer.php, copy source of each and post to pastebin.com. Click submit and post the generated URL/s here.

The current version of BuddyPress requires WordPress 3.2 and higher; see https://wordpress.org/extend/plugins/buddypress/

I think v1.2.7 is the last version that supported WP 3.0; https://downloads.wordpress.org/plugin/buddypress.1.2.7.zip

I would strongly recommend that you upgrade WordPress.

Thanks for your response @mercime.

I am still confused about how to tell from a plugin’s page whether it is really compatible with 1.5. Looking at one plugin at random at https://wordpress.org/extend/plugins/bp-group-management/ that supposedly passed, it’s page says compatible up to Buddypress 1.2.8. Does one believe the “passed” or the 1.2.8. If it’s only good up to 1.2.8, is there any way to tell how actively it is maintained and when it might be updated (other than noticing who the author is, perhaps)?

A number of the plugins showing “failed” show a date of August, 2011. Is there a planned update to the status of these plugins?

It also seems that only some plugin developers specify a Buddypress compatibility version at all, which seems problematic.

I think we are drifting away from the topic title, but this website would ideally make it easier for users to know the status of 1.5 and its plugins, rather than having to gather incomplete information from multiple sites.

Hi mercime ~ thank you

I put : http://socraticmama.com/feed/ into the Google Reader subscription box & your solution works perfectly, but it doesn’t solve the problem for those who now newly subscribe to SocraticMama. The problem is I will have to tell each new subscriber to enter http://socraticmama.com/feed/ manually into Google Reader. Is there any way to have my RSS feed, not my sitewide activity, as the automatic default for Google Reader?

Another poster had the same problem 6 months ago & a solution was provided by Mikey3D, but I don’t know how to apply the solution in my case:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/trouble-with-google-reader-and-sitewide-activity/
I can’t match it to the advice given by Mikey3D. This is because the terms ‘Blog Posts RSS Feed’ & ‘Blog Posts Atom Feed’ are not in my header.php ~ see here:

<html xmlns=&quot;http://www.w3.org/1999/xhtml&quot; >

<meta http-equiv=&quot;Content-Type&quot; content=&quot;; charset=" />
<title></title>

<link rel=&quot;pingback&quot; href=&quot;" />

<?php
if ( is_singular() && bp_is_blog_page() && get_option( 'thread_comments' ) )
wp_enqueue_script( 'comment-reply' );

wp_head();
?>

<body  id="bp-default">

<div id="header">
<div id="search-bar">
<div class="padder">
<h1 id="logo"><a href=&quot;" title=""></a></h1>

<form action=&quot;" method="post" id="search-form">
<label for="search-terms" class="accessibly-hidden"></label>
<input type=&quot;text&quot; id=&quot;search-terms&quot; name=&quot;search-terms&quot; value=&quot;" />

<input type=&quot;submit&quot; name=&quot;search-submit&quot; id=&quot;search-submit&quot; value=&quot;" />

</form><!-- #search-form -->

</div><!-- .padder -->
</div><!-- #search-bar -->

<div id="navigation">
 false, 'menu_id' => 'nav', 'theme_location' => 'primary', 'fallback_cb' => 'bp_dtheme_main_nav' ) ); ?>
</div>

</div><!-- #header -->

<div id="container">

Using the WordPress 3.2.1 and Buddypress 1.5.1 with default BuddyPress theme. I am also using the multiple groups forums

@jsibley I understand your concern.

For those who are new: whether to install BP 1.5 or not – I recommend installing this version rather than older version. BP 1.5 is a major update with a lot of bug fixes and new features. There was a list compiled by volunteers around the time BP 1.5 was launched https://codex.buddypress.org/releases/1-5-plugin-compatibility/ The list needs to be updated but clicking on most the links of the specific plugins will bring you to the plugin pages where you can see if these have been updated to latest WP/BP versions.

For those with older BP installs: whether or not to upgrade to BP 1.5.
This is a similar question that many Site/Super Admins have asked themselves or regular/multisite WP installs. Should they upgrade to the latest version of WordPress or not because they are dependent on WP plugins which have not been upgraded? Sometimes the Admins wait for the plugin to be upgraded before upgrading to latest WP version if they are assured such plugin will be upgraded. More often, Admins upgrade to latest WP version and find alternative plugin and/or sometimes paying for a premium plugin and/or updating the plugin themselves. Those are the realities in open-source software.

Platform is *supposed* to have BuddyPress support, so I looked at the CSS route via Firebug. Sure enough, some minor tweaks “lifted up” your sidebar to where it’s supposed to be.

Add this to your stylesheet to lift up the sidebar.:
`#buddypress-page #content {
float: left;
width: 600px;
}`

If you want to bring in the BP elements that extend the horizontal border, etc, add following to stylesheet as well to start:
`#buddypress-page #content .padder div.pagination { margin: -20px 0px 0 !important; }
#buddypress-page .item-list li { padding: 1em 0 !important; }
div.item-list-tabs { margin: 25px 0 20px !important; }
div#subnav.item-list-tabs { margin: -15px 0 15px !important; }
ul#members-list, ul#groups-list { list-style-type: none; margin-left: 0; }`

Add other styles to taste.

If the above solution works for you, please close the WP.org forum post as resolved. Cheers.

Per info, latest theme version is 1.8.7 https://wordpress.org/extend/themes/custom-community

Know that when you open up your registration for anyone on single WP or WP multisite, whether you have BuddyPress or not, you will get spammers and sploggers. Only “closed” or by-invitation-only sites have escaped this curse completely.

There have been different solutions using plugins and techniques to prevent this but these bots and humans spammers/sploggers are relentless. Search online and you’ll get many answers/methods
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/fighting-splogs/
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/what-do-your-spam-signups-look-like/
http://www.wptavern.com/forum/wordpress-mu-multisite/2123-anti-spam-plugins.html
https://wordpress.org/support/topic/anti-spam-for-multi-site-educationnon-profit?replies=7
http://wpfeed.com/2011/01/complete-list-of-anti-spam-plugins-and-solutions-for-wordpress/
http://wpmututorials.com/how-to/spam-blogs-and-buddypress/

https://wordpress.org/extend/plugins/bp-moderation/
https://wordpress.org/extend/plugins/wangguard/
https://wordpress.org/extend/plugins/akismet/
https://wordpress.org/extend/plugins/anti-splog/
https://wordpress.org/extend/plugins/wp-anti-spam/?topic_id=20669
https://wordpress.org/extend/plugins/moderate-new-blogs/
https://wordpress.org/extend/plugins/wpmu-new-blog-defaults/
https://wordpress.org/extend/plugins/bad-behavior/
http://itscblog.tamu.edu/bad-behavior-wpmu-2-1-15-released/
https://wordpress.org/extend/plugins/ban-hammer/