作者：诗语

Codex Home → Getting Started → Frequently Asked Questions
Frequently Asked Questions

Registration
I don’t see the register button on my BuddyPress site!
Login to the WP admin area, navigate to “Settings > General”, and make sure “Anyone can register” is checked.
If you’re using WordPress in network mode, login to the WP admin area, navigate to “Super Admin > Options”, and under “Allow new registrations”, select any option but “Disabled”.
BuddyPress isn’t sending out emails (eg. activation emails, email notifications)
This appears to be a problem with certain web hosts (Bluehost primarily).
Members of the BP community have had success using:

Mail From Plugin
WP Mail SMTP Plugin
Configure SMTP Plugin
WP-Better-Emails Plugin

WP Mail SMTP and Configure SMTP can send a test email which often provides useful debug information. Check also with your webhost’s tech support for more information.
Activity Stream
BP 1.2 Default Theme – Set the Activity Stream as front page, blog posts on another page
1) Login to the WP backend, navigate to “Pages > Add New”. Create an empty, new page called “News” or “Blog” or whatever you want. This page will contain the blog updates.
2) Under “Settings > Reading”, set front page to “Activity Stream” and your posts page to the new page that you just created.
How do I disable activity stream comments for blog and forum posts?
1) Login to the WP backend, navigate to “Buddypress > General settings”.
2) Under “Disable activity stream commenting on blog and forum posts?” Select “Yes”.
Extending BuddyPress
Avatars
Why can’t I upload avatars on my server?
This could be a number of things, but make sure you have the GD image library installed.   It might also be permissions, so make sure the web server has correct permissions.

上次修改 2021.12.31

Codex Home → Getting Started → IIS7 web.config
IIS7 web.config

Not sure how correct or valuable this is, but this is currently the web.config file that I use for local Windows 7 II7 development.

上次修改 2021.12.31

Codex Home → Developer Resources → Action Reference → Extended Profiles
Extended Profiles

bp-xprofile.php

xprofile_screen_display_profile
xprofile_screen_edit_profile
xprofile_screen_change_avatar
xprofile_screen_notification_settings
xprofile_new_wire_post
xprofile_delete_wire_post
xprofile_format_activity
xprofile_format_notifications
xprofile_updated_profile

bp-xprofile/bp-xprofile-templatetags.php

xprofile_profile_group_tabs

上次修改 2021.12.31

Codex Home → Developer Resources → Action Reference → Private Messaging
Private Messaging

bp-messages.php

messages_screen_inbox
messages_screen_sentbox
messages_screen_compose
messages_screen_notices
messages_screen_notification_settings
messages_format_notifications
messages_send_message
messages_send_notice
messages_delete_thread

上次修改 2021.12.31

Codex Home → Getting Started → Customizing → Customizing Labels, Messages, and URLs
Customizing Labels, Messages, and URLs

Do you want to change various labels and messages in BuddyPress, but don’t want to hack the core files to do so? This page explains how to use a language translation file to customize BuddyPress labels, messages, and URL slugs.

Note: This is not intended for full language translations. If you intend BuddyPress to be used in a language other than English, see the Language Translations page.

Why use a language file?

The most compelling reason to use this method of changing labels and messages is to avoid hand-changing labels and messages in plugin and theme files. Even though theme customizations are recommended and encouraged, it is nice to have your customizations in one place. Overall, creating a custom language file is a better long-term solution than hand-changing plugin or theme files since you can make changes in one place for all labels and messages used in BuddyPress.

Labels and Messages

Here are the steps to create your own custom messages and labels without doing a full language translation.

This example uses en_US as the sample language definition and thus buddypress-en_US.mo is the name of the language file you will create. You’ll need to replace ‘en_US’ with the locale of your WordPress site.

1. Create a customized PO file

Open the POT file in wp-content/plugins/buddypress/buddypress.pot, make a copy of the file and rename it to buddypress-en_US.po.

Then make the changes you want in a text editor or by using a specialized language localization editor like PoEdit (this is recommended if you are not comfortable using a text editor to make changes to the .po file).

Save your .PO file and generate a .MO file. The .MO file should be similarly named – buddypress-en_US.mo.

2. Uploading the PO and MO files

Now that you have generated your .MO file, move both the PO and MO files to /wp-content/languages/plugins/ on your server.

If the /wp-content/languages/plugins/ folder does not exist, create it!

3. Load the MO language file

WordPress 4.6 changed how language files are enqueued, preferring the GlotPress-provided “canonical” language file over a custom language file. The simplest way to make sure your new .mo file will be used is via a plugin available on the WordPress plugin repository: WPT Custom Mo File. Once you’ve activated the plugin, visit WP Admin > Tools > WPT Custom Mo File to upload your custom .mo file.

4. Test and verify your changes by loading BuddyPress.

Translating with PoEdit

PoEdit is a lightweight application for editing and creating .po and .mo files.

If you are not comfortable working at the command line then it is highly recommended to use this application.You can download PoEdit from http://www.poedit.net/download.php.

1) Download, install and start PoEdit

2) Select the BuddyPress translation file

On the main menu select “File > New catalog from POT file”, navigate to the BP languages folder (/wp-content/plugins/buddypress/bp-languages/)and select the ‘buddypress.pot’ file.

This will open a settings dialog and you will be asked to fill in some details such as project name which we’ll skip.

Click on ‘OK’ and you’ll be asked to save your language file.

Save your language file as “buddypress-en_US.po”. If you’re using a different language on WordPress, change “en_US” to the locale of your WordPress install.

3) Changing strings and saving the changes

Now, you will see a list of all the BuddyPress language strings you can modify.

Click on any string you wish to change and make the adjustment in the bottom half of the screen.

Go ahead and repeat this process for the other labels you want to change and when you’re done, hit “Save”.

4) Uploading the PO and MO files

Follow steps #2 and #3 above.

Updating your custom language file

When a new version of BuddyPress is released, a new BuddyPress POT file is generated.

To remain up-to-date, you will need to merge this new file with your custom .po catalog.

You can do this by following these instructions:

1) Start PoEdit and go to “File > Open”. Select your custom .po catalog file you created.

2) Now, go to “Catalog > Update from POT file…”, and navigate to the /plugins/buddypress/buddypress.pot file (For older versions of BuddyPress, this file is located at /plugins/buddypress/bp-languages/buddypress.pot).

3) Opening the file will show an “Update Summary” window, which shows you the new strings added and the obsolete strings that will be removed. Click on “OK” and these changes will be merged into your .po file.

4) Then, simply save your catalog file once more to generate a new .mo file.

Slugs

For example, if you are running a sports website with BuddyPress, you could rename the URL slug example.com/members to example.com/players by changing the url of the corresponding component page in the WordPress admin -> pages.

To change slugs on the sub nav on a member page add these defines to a file bp-custom.php and place this file in /plugins/bp-custom.php

define( ‘BP_SETTINGS_SLUG’, ‘settings’ );
define( ‘BP_XPROFILE_SLUG’, ‘profile’ );

Loco Translate – Plugin solution

Loco Translate allows site admins to modify WordPress translations files of any theme and any plugin within the WordPress Dashboard. It also provides localization tools for developers, such as extracting strings and generating templates.

Go to Loco Translate plugin page

Notes

This is not intended for full language translations. If you intend BuddyPress to be used in a language other than English, see the Language Translations page.

This solution is arguably better than using the define ( ‘WPLANG’, ”); declaration in your wp-config.php file since we are really just trying to customize BuddyPress and not WordPress MU as a whole.

This page was inspired by a forum topic on BuddyPress.org called I want to speak Spotlish. View that thread for discussion and other suggestions.

上次修改 2021.12.31

Codex Home → Getting Started → User Submitted Guides → Deprecated Guides → Modifying the Toolbar
Modifying the Toolbar

Note: Modifying the Admin Bar requires a basic understanding of WordPress Hooks,Actions and Filters. If you aren’t familiar with these items, you can find more information on the WordPress Plugin API page.
The admin bar is a collection of individual functions, each of which implements a specific top level menu item that is displayed. If you look at the code in: /bp-core/bp-core-adminbar.php you’ll see these funcitons such as bp_adminbar_blogs_menu(). That creates the ‘My Blogs’ menu item and all the items within the drop down menu.
We’re going to modify the ‘My Blogs’ menu without changing the core code, thus helping to assure that our modifications don’t break when upgrading. We are going to sort the ‘My Blogs’ menu items to have them appear in a specific order and eliminate the items that show up as ‘Subscriber’.
The admin bar is triggered by wordpress ‘actions’. These ‘actions’ are events that are triggered throughout wp and bp. The admin bar responds to the action ‘wp_footer’ which wp themes trigger at the end of each page in the theme footer. The admin bar registers it’s need to do something with the call to:
add_action( ‘wp_footer’, ‘bp_core_admin_bar’, 8 );

When the action ‘wp_footer’ is triggered it will call the function named ‘bp_core_admin_bar’. Looking at the function:
function bp_core_admin_bar() {
global $bp, $wpdb, $current_blog, $doing_admin_bar;

$doing_admin_bar = true;

if ( (int) get_site_option( ‘hide-loggedout-adminbar’ ) && !is_user_logged_in() )
return false;

echo ‘<div id="wp-admin-bar">’;

// **** Do bp-adminbar-logo Actions ********
do_action( ‘bp_adminbar_logo’ );

echo ‘<ul class="main-nav">’;

// **** Do bp-adminbar-menus Actions ********
do_action( ‘bp_adminbar_menus’ );

echo ‘</ul>’;
echo ‘</div>’;
}

At first glance it doesn’t seem to do much. It does though. It defines its own action and triggers that action at the end of the function:
// **** Do bp-adminbar-menus Actions ********
do_action( ‘bp_adminbar_menus’ );

At the bottom of bp-core-adminbar.php you’ll notice a collection of add_action() calls that respond to ‘bp_adminbar_menus’.
add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_login_menu’, 2 );
add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_account_menu’, 4 );
add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6 );
add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_notifications_menu’, 8 );
add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_authors_menu’, 12 );
add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_random_menu’, 100 );

Each of the individual menu items responds to ‘bp_adminbar_menus’. The one we are going to change is bp_adminbar_blogs_menu().
To change a function that is triggered by an action you have to unhook the current function that responds to the action and supply your own function that replaces the core function and then replace the add_action() call with one that responds to the same hook as the original function. This is how we’ll do that:
Original action hook:
add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6 );

Remove the action hook:
remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6);

Replace the original action hook:
add_action(‘bp_adminbar_menus’, ‘my_adminbar_blogs_menu’, 6);

Create a replacement function:
function my_adminbar_blogs_menu() {
if ( is_user_logged_in() ) {
global $bp;

if ( function_exists(‘bp_blogs_install’) ) {

if ( !$blogs = wp_cache_get( ‘bp_blogs_of_user_’ . $bp->loggedin_user->id, ‘bp’ ) ) {
$blogs = get_blogs_of_user( $bp->loggedin_user->id );
wp_cache_set( ‘bp_blogs_of_user_’ . $bp->loggedin_user->id, $blogs, ‘bp’ );
}

$blogs = filter_blogs_by_role($blogs);

[snip] the rest of the original function [snip]
}

I’ve made one change to the original function.
$blogs = filter_blogs_by_role($blogs);

After the call to get_blogs_of_user() we get an array of ‘blog’ objects back from wp where the user has any role. I want to sort these blog objects to my liking and then just allow the rest of the function to run and display them.
I’ve decided to call my sort function filter_blogs_by_role() and it takes the array of blog objects, does something to them and then returns that filtered array of user blog objects. The rest of the function goes happily along to display our filtered results.
I’m not going to delve into what the filter_blogs_by_role() function does. I’ll just repeat it here. It sorts the blog objects by role with ‘Admin’ appearing before all the other roles.
// sort array of blog objs by $blog->role according to the order of $blog_roles
// roles not included in $blog_roles array will not be displayed
function filter_blogs_by_role($blogs){
global $bp, $blog_roles;

$blog_roles[] = __( ‘Admin’, ‘buddypress’ );
$blog_roles[] = __( ‘Editor’, ‘buddypress’ );
$blog_roles[] = __( ‘Author’, ‘buddypress’ );
$blog_roles[] = __( ‘Contributor’, ‘buddypress’ );
$blog_roles[] = __( ‘Subscriber’, ‘buddypress’ );

// get roles
foreach ($blogs as $blog){
$blog->role = get_blog_role_for_user( $bp->loggedin_user->id, $blog->userblog_id );
}

// eliminate roles not in $blog_roles
foreach ($blogs as $key => $value){
if (!in_array($value->role, $blog_roles))
unset($blogs[$key]);
}

// sort by $blog_roles sequence if there are any left
if ($blogs){
usort($blogs, ‘compare_roles’);
}

return $blogs;
}

// helper function
function compare_roles($a, $b){
global $blog_roles;

foreach($blog_roles as $key => $value){
if($a->role==$value){
return 0;
break;
}

if($b->role==$value){
return 1;
break;
}
}

Now we have a replacement function called my_adminbar_blogs_menu(). We’ve got to hook it up so that it actually does replace the orignal call to bp_adminbar_blogs_menu();
Any custom code that we create can be placed in a file called bp-custom.php. It gets loaded with all the rest of bp automatically by bp during each page load. If you don’t have one already then create one in /wp-content/plugins/. So we’ll pretend that we have done just that and that our three new functions are going to be loaded with the rest of bp.
bp-custom.php

So we have our shiny new replacement function and we now need to determine how best to hook it up to the rest of the universe and make it work. There really isn’t a ‘best’ way to do this. There are several ways to do it though.
I like to keep all my custom bp code in bp-custom.php so that’s how I’m going to implement this. Since the admin bar responds to ‘wp_footer’, I’m going to hook that event and do some things before the admin bar is displayed.
In bp-custom.php:
function my_alter_bp_adminbar(){
remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6);
add_action(‘bp_adminbar_menus’, ‘my_adminbar_blogs_menu’, 6);
}
add_action(‘wp_footer’,’my_alter_bp_adminbar’,1);

I’ve told wp that when it triggers the action ‘wp_footer’ call the function my_alter_bp_adminbar() and do it with a priority of ‘1’. A priority of ‘1’ makes sure that it gets called before other functions that respond to ‘wp_footer’.
If I add that to the other three functions I just stuffed into bp-custom.php then it will replace the original menu function with my new menu function and alter the behavior of bp when it displays the ‘My Blogs’ menu.
Confusing enough for you? Welcome to event driven programming.
Other Articles on Modifying the Admin Bar
Limit Blog Creation to Admins

上次修改 2021.12.31

Codex Home → Developer Resources → Loops Reference
Loops Reference

Just as you use “The Loop” to loop through posts in WordPress, each content type in BuddyPress has its own custom loop.
By using these loops in your template, you can output any kind of information and really customize how content is displayed within your BuddyPress theme.
The default BuddyPress template files makes use of all the loops avaliable in BuddyPress. It provides a good example of using the loops in real use situations.

上次修改 2021.12.31

Codex Home → Developer Resources → Loops Reference → Activity Loop
Activity Loop

The activity loop can be used to output a list of sitewide, member or member’s friends activity.
Standard Loop

Accepted Parameters
The bp_has_activities() function will accept a number of parameters that will manipulate the data being returned.

scope optional
Pre-defined filtering of the activity stream. Show only activity for the scope you pass (based on the logged in user or a user_id you pass).

Accepted arguments: just-me, friends, groups, favorites, mentions
Default value: $bp->current_action

display_comments optional
Whether or not to display comments along with activity items. Threaded will show comments threaded under the activity. Stream will show comments within the actual stream in chronological order along with activity items.

Accepted arguments: false, threaded, stream
Default value: threaded

include optional
Pass an activity_id or string of comma separated ids to show only these entries.

Default value: false

sort optional
Sort the stream chronologically ascending or descending.

Accepted arguments: ASC, DESC
Default value: DESC

per_page optional
Number of activity items to show per page.

Default value: 20

page optional
Which page to return based on the number per page value.

Default value: 1

max optional
The limit on number of activity items that can be returned

Default value: false

show_hidden optional
Show items that have been hidden site wide? For example private or hidden group posts.

Default value: false

search_terms optional
Return only activity items that match these search terms

Default value: false

Filtering Options
Using filtering you can use the activity loop to return any specific information that has been recorded on the entire site. For example you could use it to return all of the latest comments site wide.
Listed below are the parameters you can use to filter the activity stream.

user_id optional
Limit activity items to a specific user ID. You can also pass in a comma separated string of user ids – see example below.

Default value: false (no filter)

object optional
The object type to filter on (can be any active component ID as well as custom component ID’s)

Example arguments: groups, friends, profile, status, blogs
Default value: false (no filter)

action optional
The action type to filter on (can be any active component action as well as custom component actions)

Example arguments: new_forum_post, new_blog_comment new_blog_post, friendship_created, joined_group, created_group, new_forum_topic, activity_update
Default value: false (no filter)

primary_id optional
The ID to filter on for a specific object. For example if you used groups as the object you could pass a group_id as the primary_id and restrict to that group.

Possible arguments: Any specific object ID
Default value: false (no filter)

secondary_id optional
The secondary ID to filter on for a specific object. For example if you used blogs as the object you could pass a blog_id as the primary_id and a post_id as the secondary_id the list all comments for that post using new_blog_comment as the action.

Possible arguments: Any specific object ID
Default value: false (no filter)

Filtering Examples
Filtering the activity loop to show only activity updates in the activity stream:

Use ‘user_id’ to filter the activity loop to show only you and your friends in the activity stream:

Adding Commenting Support
Adding commenting support to your activity loop is pretty straightforward. You will first need to pass the “display_comments=threaded” parameter to your loop (see above).
Second you need to wrap all your activity code in a div with an “activity” class in order to make the ajax comments to work.
Finally, add the following code inside your loop, below “activity-content” div and above the closing list item tag: