更改內部配置設定

更改內部配置設定

Codex Home → Getting Started → Customizing → Changing Internal Configuration Settings
Changing Internal Configuration Settings

N.B: This article lists deprecated settings as well as current ones
 
There are many internal configuration settings that can be changed by adding a configuration definition line to your wp-content/plugins/bp-custom.php file or use a filter if available. Here』s a list of the current configurations that can be changed:
 
Avatar Configurations
Avatar specific settings can be changed:
define ( 'BP_AVATAR_THUMB_WIDTH', 50 );
define ( 'BP_AVATAR_THUMB_HEIGHT', 50 );
define ( 'BP_AVATAR_FULL_WIDTH', 150 );
define ( 'BP_AVATAR_FULL_HEIGHT', 150 );
define ( 'BP_AVATAR_ORIGINAL_MAX_WIDTH', 640 );
define ( 'BP_AVATAR_ORIGINAL_MAX_FILESIZE', $max_in_kb );
define ( 'BP_AVATAR_DEFAULT', $img_url );
define ( 'BP_AVATAR_DEFAULT_THUMB', $img_url );

 
Cover Image Configurations
To customize cover images please visit this link: https://codex.buddypress.org/themes/buddypress-cover-images/
 
Advanced Configurations
Put profiles in the root — http://example.org/username/
define ( 'BP_ENABLE_ROOT_PROFILES', true );
add_filter( 'bp_core_enable_root_profiles', '__return_true' );
N.B. If you use BP_ENABLE_ROOT_PROFILES there might be a situation where some user profiles get the same url as some posts or pages rendering either of them inaccessible. This might also be true of sub-sites if you』re running multisite with subdirectories. See ticket #1426 for more information.
Change the default tab opened when looking at a user』s profile (default is activity):
define( 'BP_DEFAULT_COMPONENT', 'profile' );
(Note: if you change the URL slug of xprofile, say, define ( 'BP_XPROFILE_SLUG', 'info' );, you would have to change it here accordingly,  define( 'BP_DEFAULT_COMPONENT', 'info' );  otherwise, link to the profile page would always jump to homepage.)
Change the default tab opened when looking at a group (default is home):
define( 'BP_GROUPS_DEFAULT_EXTENSION', 'members' );
Disable the admin bar / buddybar at the top of every screen:
define ( 'BP_DISABLE_ADMIN_BAR', true );
Swap the Buddybar for the WordPress toolbar: (default in buddypress 1.6)
define ( 'BP_USE_WP_ADMIN_BAR', true );
Disable the custom header functionality on the default BuddyPress theme:
define( 'BP_DTHEME_DISABLE_CUSTOM_HEADER', true );
Disable the 「You』ll need to activate a BuddyPress compatible theme…」 warning message in the WordPress administration screens:
define( 'BP_SILENCE_THEME_NOTICE', true );
Enable support for LDAP usernames that include dots:
define( 'BP_ENABLE_USERNAME_COMPATIBILITY_MODE', true );
Disable auto-joining of a group when non group member performs group activity:
defined( 'BP_DISABLE_AUTO_GROUP_JOIN', true );
Ignore all deprecated code (don』t load it):
define ( 'BP_IGNORE_DEPRECATED', true );
add_filter( 'bp_ignore_deprecated', '__return_true' );
 
Forum Configurations
Change the parent forum to use for all BuddyPress group forums:
define ( 'BP_FORUMS_PARENT_FORUM_ID', $forum_id );
 
Database Configurations
Set a custom user database table for BuddyPress (and WordPress to use):
define ( 'CUSTOM_USER_TABLE', $tablename );
Set a custom usermeta database table for BuddyPress (and WordPress to use):
define ( 'CUSTOM_USER_META_TABLE', $tablename );
 
Multisite Configurations
Allow BuddyPress to function on multiple blogs of a WPMU installation, not just on one root blog (More details about BP_ENABLE_MULTIBLOG):
define ( 'BP_ENABLE_MULTIBLOG', true );
add_filter( 'bp_is_multiblog_mode', '__return_true' );
Set which blog ID BuddyPress will run on:
define ( 'BP_ROOT_BLOG', $blog_id );
add_filter( 'bp_get_root_blog_id', 'filter_root_blog_id' ); // return blog ID integer
 
Deprecated Configurations
Change the URL slugs of BuddyPress components:
The references to slug Constants are deprecated, this section requires updating.
define ( 'BP_ACTIVITY_SLUG', 'streams' );
define ( 'BP_BLOGS_SLUG', 'journals' );
define ( 'BP_MEMBERS_SLUG', 'users' );
define ( 'BP_FRIENDS_SLUG', 'peeps' );
define ( 'BP_GROUPS_SLUG', 'gatherings' );
define ( 'BP_FORUMS_SLUG', 'discussions' );
define ( 'BP_MESSAGES_SLUG', 'notes' );
define ( 'BP_WIRE_SLUG', 'pinboard' );
define ( 'BP_XPROFILE_SLUG', 'info' );
define ( 'BP_REGISTER_SLUG', 'signup' );
define ( 'BP_ACTIVATION_SLUG', 'enable' );
define ( 'BP_SEARCH_SLUG', 'find' );
define ( 'BP_HOME_BLOG_SLUG', 'news' );

論壇 (Forums)

論壇 (Forums)

Codex Home → Legacy Docs → Archived Section: Getting Started → Forums
Forums

Archived file. Good only up to BP 1.5 version

bbPress 2.2+ Update
Using bbPress 2.2+ with BuddyPress

BuddyPress 1.5 Update
: Installation of BuddyPress 1.5+ Group Forums and Sitewide Forums

Introduction for Forums in BP 1.2+
BuddyPress 1.1 introduces a new way of thinking about how forums function around a social setup. Instead of having a categorical, separated top-down list of forums, they are now fully integrated and attached to groups that can be created and controlled by any registered user. The included default theme shows all recent topics regardless of their group (public groups only).
With previous versions of BuddyPress, integrating bbPress often required special attention and little voo-doo magic. Even getting basic functions like shared logins and template styles working together on both sides was not an easy task. In BuddyPress 1.1 this all works with one click. Thanks to a robust set of classes and functions, BuddyPress controls your forums transparently, eliminating all previous integration pains. No more cookie headaches, no more 「deep integration」 because bbPress』s functions are available right within BuddyPress.
Another benefit of this approach is an integrated theme. There is no need to create a completely separate bbPress theme for your forums. Your existing BuddyPress enabled WordPress theme will control the design.
Extensions to bbPress and BuddyPress forum support can be added through WordPress plugins. Some existing bbPress plugins that do not require an admin interface can be added via the mu-plugins folder in WordPress MU. They can also be converted to a standard WordPress plugin.
Previous Installations
If you』d prefer to use the previous integration method for your existing forum setup, this is still possible. In this scenario BuddyPress will use its own internal bbPress files for group forum support, while your existing external bbPress installation will continue to work as it did. Both sets of bbPress files will use the same existing database tables. However, you will need to go through the upgrade instructions below before BuddyPress group forums will work again.
Upgrading from 1.0 to 1.1
After upgrading BuddyPress to 1.1, head to the 「WP-Admin ? BuddyPress ? Forum Setup」 menu and a wizard will run you through the re-connection process. BuddyPress will create a bb-config.php file at the root of your WordPressMU installation. This file is automatically generated and will not require additional editing for your group forums to function.
Existing or New installation?
If you have an existing bbPress installation or a previously integrated BuddyPress1.0 setup, do not choose to create a new installation as this will break your existing group forums. Instead choose existing installation, so that your old bbPress database will be retained.
If you do not have an existing bbPress installation, select new installation and BuddyPress will take care of everything for you.
If you have an external bbPress database that does not use the same database as your WordPressMU installation, this is considered an atypical installation and is not currently supported by the BuddyPress1.1 upgrade process.
Process for installing bbPress included with BuddyPress
(1) Install bbPress within the wp-admin panel
In the wp-admin panel > BuddyPress > Forums Setup
(2) Each group now has access to enabling a forum. Go to Group Settings for each group Group > Admin > Edit Settings. There is a checkbox for enabling the forum. Once enabled then the link for a forum for that particular group becomes available

論壇主題迴圈

論壇主題迴圈

Codex Home → Developer Resources → Loops Reference → Forum Topics Loop
Forum Topics Loop

The forum topics loop can be used to output a list of forum topics.
Standard Loop

<tr class="">

<a class="topic-title" href="" title=" - ">

<a href="">

<a href="">

<a href="" title="">

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

type optional
List forum topics by type.

Accepted arguments: newest,popular,unreplied,tags (if type equals 「tags」, define the 「search_terms」 argument and list the tag you wish to filter by)
Default value: newest

forum_id optional
Return only forum topics from a specific group forum.

Default value: false

user_id optional
Return only forum topics that this user has started.

Default value: false

per_page optional
Number of forum topics to display in the loop.

Default value: 20

page optional
The page to display.

Default value: 1

max optional
The total number of forum topics to return.

Default value: false (no limit)

no_stickies optional
Return 「false」 if you do not want stickies listed at the top of the forum loop.

Default value: all

search_terms optional
Return only groups that match these search terms. When used in conjuction with 「type=tags」, can use search_terms to define the tag name.

Default value: false

Examples
Modifying the forum loop to list forum topics by most popular:

構建 BP 預設主題的子主題

構建 BP 預設主題的子主題

Codex Home → Legacy Docs → Archived Section: Theme Development → The BuddyPress Default Theme → Building a Child Theme of the BP Default Theme
Building a Child Theme of the BP Default Theme

Archived file. The BP Default theme will no longer be activated in new installations and will be retired in the near future. http://bpdevel.wordpress.com/2013/11/13/the-future-of-the-bp-default-theme/

This is an approach to child theming based on the BuddyPress Default theme. You may opt to choose a regular WordPress theme and take advantage of the BuddyPress Theme Compatibility introduced in version 1.7 which allows for nearly all WordPress themes to run BP templates within it』s theme and child themeing or customizing your BP templates by copying them to your theme/child theme easy to accomplish!
Should you then still prefer to create your own child theme for the BP Default theme, read on

The bp-default theme packaged with the BuddyPress plugin is a robust parent theme which includes network-centric template files in addition to special template files similar to what you would find in a regular WordPress theme.
You can easily create your own unique site design or theme based on the bp-default theme, thanks to the Parent-Child functionality available in WordPress that was implemented in the BuddyPress default theme. This step-by-step guide will help you build your own custom bp-default child theme.
Child Themes: What is the point? Why not just create a brand new theme?
Creating a bp-default child theme is the easiest and most future-proof way of building a BuddyPress theme. Aside from taking advantage of bp-default theme』s functionality, you can tweak it to suit your own needs. By extending the bp-default theme, you inherit all of the templates, JS, AJAX and if you wish, the CSS, all while preserving the core bp-default theme files.
When new versions of BuddyPress are released with an updated default theme, your theme will automatically be updated along with it! You can override any Parent theme template simply by either (1) copying it into your child theme and tweaking it or (2) creating a new, 「same-name」 template file in your Child theme directory. You can also add your own CSS, JS and AJAX features.
Stylesheet changes
As of BuddyPress 1.5, BuddyPress Default Theme (bp-default) uses a function, bp_dtheme_enqueue_styles, to enqueue its stylesheets as shown below.
if ( !function_exists( 'bp_dtheme_enqueue_styles' ) ) :
/**
* Enqueue theme CSS safely
*
* For maximum flexibility, BuddyPress Default's stylesheet is enqueued, using wp_enqueue_style().
* If you're building a child theme of bp-default, your stylesheet will also be enqueued,
* automatically, as dependent on bp-default's CSS. For this reason, bp-default child themes are
* not recommended to include bp-default's stylesheet using @import.
*
* If you would prefer to use @import, or would like to change the way in which stylesheets are
* enqueued, you can override bp_dtheme_enqueue_styles() in your theme's functions.php file.
*
* @see https://codex.wordpress.org/Function_Reference/wp_enqueue_style
* @see https://codex.buddypress.org/releases/1-5-developer-and-designer-information/
* @since 1.5
*/
function bp_dtheme_enqueue_styles() {

// Bump this when changes are made to bust cache
$version = '20130629';

// Register our main stylesheet
wp_register_style( 'bp-default-main', get_template_directory_uri() . '/_inc/css/default.css', array(), $version );

// If the current theme is a child of bp-default, enqueue its stylesheet
if ( is_child_theme() && 'bp-default' == get_template() ) {
wp_enqueue_style( get_stylesheet(), get_stylesheet_uri(), array( 'bp-default-main' ), $version );
}

// Enqueue the main stylesheet
wp_enqueue_style( 'bp-default-main' );

// Default CSS RTL
if ( is_rtl() )
wp_enqueue_style( 'bp-default-main-rtl', get_template_directory_uri() . '/_inc/css/default-rtl.css', array( 'bp-default-main' ), $version );

// Responsive layout
if ( current_theme_supports( 'bp-default-responsive' ) ) {
wp_enqueue_style( 'bp-default-responsive', get_template_directory_uri() . '/_inc/css/responsive.css', array( 'bp-default-main' ), $version );

if ( is_rtl() )
wp_enqueue_style( 'bp-default-responsive-rtl', get_template_directory_uri() . '/_inc/css/responsive-rtl.css', array( 'bp-default-responsive' ), $version );
}
}
add_action( 'wp_enqueue_scripts', 'bp_dtheme_enqueue_styles' );
endif;

What this means is that the function bp_dtheme_enqueue_styles() enqueues stylesheets in the following order:
a) bp-default theme』s main stylesheet, default.css
b) bp-default child theme』s stylesheet, style.css (if the activated theme is a bp-default child theme)
c) right-to-left CSS stylesheet, rtl.css, and
d) screen responsive stylesheet, responsive.css
Let』s Start Building!
The bp-default theme is located in the BuddyPress plugin folder at /wp-content/plugins/buddypress/bp-themes/ so it can be updated along with the plugin. WordPress knows where it is, even though your own child theme folder is in /wp-content/themes/.
A. Create a new theme folder
The first step is to create a new theme folder and give it a unique name. For this example, the theme is called 「BuddyPress Dusk」 and so we』ll name our folder bp-dusk. We』ll be uploading the bp-dusk child theme folder to wp-content/themes/
B. Create a style.css file
1. Create a new file and save as style.css in the bp-dusk child theme folder i.e. /bp-dusk/style.css. This will be your child theme』s stylesheet.
2. Open up the new style.css file and add the following code to the top of the file, replacing necessary details with your own.
/*
Theme Name: BuddyPress Dusk
Theme URI: http://example.org/themes/dusk/
Description: Dark theme for BuddyPress.
Version: 1.0
Author: John Doe
Author URI: http://example.org/
Template: bp-default
Tags: buddypress, two-column, grey, dark
*/

Two important items:

Template: bp-default – this tells WordPress that we want to use the BuddyPress default theme (bp-default) as the parent theme, and inherit all templates from it.
Tags: buddypress – this tells BuddyPress that you are using a BuddyPress-compatible theme so it won』t nag you in the admin area.

3. Save the style.css file.
4. At this point, upload bp-dusk folder to wp-content/themes/ in server. In the WordPress admin area > Appearance > Themes, you should see your new theme among the list of themes.
If you don』t see your child theme in the list of themes and your installation is Multisite, make sure you』ve enabled your BuddyPress Dusk theme in Network Admin > Themes.
5. Go ahead and activate your new child theme.
6. Check your home page of your site. You』ll notice that the design and layout of your child theme mirror those of the BuddyPress Default theme.
Congratulations! This means your new child theme is working correctly and inheriting all of the styles and template files.
(2) Inheriting CSS (or not!)
At this point you have an important decision to make:

you can inherit the default theme』s CSS and work from there, or
you can start writing your own CSS from scratch.

1. Inherit the default theme』s CSS and work from there
If you simply want to change the color scheme, and perhaps alter the layout a bit, it is highly recommended to inherit bp-default theme』s CSS. In BP 1.5+, you don』t have to do anything! Just start writing your new styles in your child theme』s style.css file and when you』re done, continue to section 3!
2. Start writing your own CSS from scratch.
If you plan to create a radically new theme design, you might want to start with a fresh slate. If you』re using BP 1.5+ and you decide you do not want to inherit the CSS, create a functions.php file in your child theme folder and add the following to your child theme』sfunctions.php:

This tells BuddyPress not to queue up the default styles. Now, you can start designing to your heart』s content!
Remember though, you still need to get your child theme』s style linked to your template files. You can do this by either:
a) Copying over the header.php file from the bp-default theme into your child theme』s folder, bp-dusk. Then add the link to your theme』s style.css file in header.php between bp_head and pingback_url like so:

<link rel="stylesheet" href="" type="text/css" media="screen" />
<link rel="pingback" href="" />

OR
b) enqueueing your child theme』s stylesheet in your child theme』s functions.php like so:
if ( !function_exists( 'bp_dtheme_enqueue_styles' ) ) :
function bp_dtheme_enqueue_styles() {

// You should bump this version when changes are made to bust cache
$version = '20130629';

// Register stylesheet of bp-dusk child theme
wp_register_style( 'bp-dusk', get_stylesheet_directory_uri() . '/style.css', array(), $version );

// Enqueue stylesheet of bp-dusk chid theme
wp_enqueue_style( 'bp-dusk' );
}
add_action( 'wp_enqueue_scripts', 'bp_dtheme_enqueue_styles' );
endif;

You can also enqueue bp-default theme』s rtl.css and responsive.css or create your own and add to the function above.
Continue on to section 3!
For BP 1.2 bp-default child themes:
If you』re still using BP 1.2.x and you want to inherit the bp-default theme』s CSS, will need to add the following lines to your 「style.css」 file (below the comment header):
/* Inherit the default theme styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
/* Inherit the default theme adminbar styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );

Once you』ve added these lines, try reloading your home page again. You』ll notice that the design has gone back to the design of the default theme. This is perfect, you can now start making design adjustments in your own theme by adding your own CSS styles below this line.
If you』ve decided that you do not want to inherit the CSS, then you can just start adding your own styles right below the header comment.
(3) Overriding BuddyPress』 Template Files
By default, your new child theme will inherit all the template files from the BuddyPress Default theme.
Most design and layout changes can be done in the CSS, but what if you wanted to change some of the HTML markup?
It』s now time to override some template files!
Let』s say I wanted to override the header.php template file.
The first step is to navigate to the BuddyPress plugin folder (usually /wp-content/plugins/buddypress/) and then to the BuddyPress Default theme folder — bp-themes/bp-default.
In this folder you should see the header.php file, copy this file and paste it directly into your child theme』s folder (the same place as your style.css file).
You can now make any edits to the HTML you wish and these will be reflected in your child theme. The header.php file in your child theme is essentially replacing the one from the BuddyPress Default theme.
You can do this with any template file from the BuddyPress Default theme. However, if you want to override a template file that is in a subfolder, you must also recreate the subfolder in your child theme.
(4) functions.php
There is one exception to the template override rule — functions.php.
If you create a blank functions.php file in your child theme, the parent theme (or in our case, the BuddyPress Default theme) functions.php will still be loaded.
This will allow you to inherit existing functions from BuddyPress Default, but you can also add your own customized code in here as well!
You must make sure you give your child theme functions a unique name, otherwise they will clash with the parent.

And that』s it! That is really all there is know about creating your brand-new child theme powered by the BuddyPress Default theme!
If you need help with anything listed in this tutorial, please post a question on our support forums:
https://buddypress.org/support/topics/

升級 BuddyPress

升級 BuddyPress

Codex Home → Legacy Docs → Archived Section: Getting Started → Upgrading BuddyPress
Upgrading BuddyPress

Upgrading from an earlier version of BuddyPress? No problem, please follow the instructions that match your situation.
BACKUP – this cannot be emphasized enough! Make a copy of your database and all files before upgrading. There have been major changes in the latest version of BuddyPress and you will want a copy of your existing setup to fall back on if needed.
Upgrading from 1.5.x to 1.6
BuddyPress 1.6 requires WordPress 3.4 and has its own upgrade page, with information and advice about the upgrade process. You may also be interested in BP 1.6』s list of features and fixes.
Upgrading from 1.2.x to 1.5
BuddyPress 1.5 has its own upgrade page, with information and advice about the upgrade process. You may also be interested in BP 1.5』s list of features and fixes.
Upgrading from 1.1.x to 1.2.5

Deactivate any BuddyPress plugins and then deactivate BuddyPress.
If you are not going to use the new default theme, please download, install and activate the BuddyPress backwards compatibility plugin.
Upgrade BuddyPress automatically, or download BuddyPress and overwrite your existing copy.
Delete 「bp-default」 and 「bp-sn-parent」 from your themes directory.
If you are using your own custom theme from 1.1, you will need to add define( 'BP_CLASSIC_TEMPLATE_STRUCTURE', true ); to your wp-config.php file above the 「stop editing」 line.
Activate BuddyPress. You do not need to move any themes in this version.

Upgrading from 1.0.x to 1.2.x
To upgrade from BuddyPress 1.0 to 1.2 you will first need to download version 1.1 and upgrade manually by overwriting the existing BuddyPress plugin folder. Once you are running 1.1, please follow the instructions for upgrading from 1.1.
It』s important to note that if you are still using the old two theme setup (member theme & home theme) then this will no longer work in version 1.2. You will need to merge your theme into one. If you are running a standard WordPress theme as the home theme, you may want to read this guide to running BuddyPress on a sub blog. If you are running a bbPress integration you will need to run through the bbPress connection wizard under 「BuddyPress > Forums Setup > Use Existing install..」 in your wp-admin area after upgrading to 1.2.

群組設定和角色

群組設定和角色

Codex Home → Administrator Guide → Group Settings and Roles
Group Settings and Roles

BuddyPress allows any member to create a group around a common interest or purpose. Here are some basic settings that will help you get your BuddyPress groups up and running.
Privacy Options
When creating a group, you have the option of making your group Public, Private, or Hidden.

Public groups are visible in all group directories. The contents of the group – activity updates, forum posts, and any additional group functionality you might add through plugins – is publicly accessible. Anyone in your BuddyPress community can join a Public group.
Private groups are also visible in group directories. The group name and group description remain available for all to see. However, the contents of the group are accessible only to members. Moreover, group membership is controlled: members of your broader BuddyPress community must request membership, which can only be granted by a group administrator.
Hidden groups are invisible to non-members. These group names and descriptions are not listed in sitewide directories, and their contents are accessible only to members of the group. Because the group is unlisted, users cannot request membership. Instead, individuals can only join the group by invitation.

Group administrators can change a group』s privacy settings at any time by visiting the group』s Admin tab > Group Settings.
Group roles
BuddyPress group members have three roles available to them.

Members: By default, when a user joins a group, he or she has the role of member. What does it mean to be a member of a BuddyPress group? That depends on what kind of group it is.

In a public group, members are able to post to that group』s forums, as well as submit content to other parts of the group (for instance, group members can upload documents in conjunction with the BuddyPress Group Documents plugin). When a user posts to the discussion forum of a public group, the user automatically becomes a member of the group. Additionally, being a member of a group means having the group』s activity aggregated in your Activity > My Groups activity stream.
In a private group or a hidden group, members have all the same privileges as members in a public group. Additionally, being a member of a private group means that you get to see who else is a member of the group, and that you』re able to send invites to other users.

Moderators: When a group member is promoted to be a moderator of the group, it means that the member receives the following additional abilities:

Edit group details, including the group name and group description (see: #4737)
Edit, close, and delete any forum topic or post in the group
Edit and delete other kinds of content, as produced by certain plugins

Administrators: Administratorshave total control over the contents and settings of a group. That includes all the abilities of moderators, as well as the ability to:

Change group-wide settings (Admin > Settings). For instance, administrators can turn group forums on or off, change group status from public to private, and toggle on or off various other group functionality provided by plugins
Change the group avatar (Admin > Group Avatar)
Manage group members (Admin > Manage Members). More specifically, only group administrators have the power to promote members to moderators, or to ban individual users from the group
Delete the group (Admin > Delete)

The individual who creates the group is automatically the group』s first administrator. As a result, each group must have at least one administrator, though the first admin can choose to appoint others.

報告錯誤

報告錯誤

Codex Home → Participate and Contribute → Reporting Bugs
Reporting Bugs

Thanks to people like you, the BuddyPress community grows stronger each day. More and more people are testing or using BuddyPress for their websites. Naturally this means we are getting more bug reports, feature suggestions and other enhancement ideas than ever.
Please read this useful information on how to report bugs and features, and how you can help fix them.
Overview of Bug Reporting and Resolution

A user finds a bug that appears to be in the core of BuddyPress (not in a Theme or Plugin).
The user tries to make sure it is actually a bug; they can post on our forums if they are not sure.
If it is determined to be a bug, the user submits the bug report, called a ticket, to Trac (the BuddyPress bug tracking system).
A BuddyPress developer (who could be a volunteer like you) confirms that the bug does actually exist, and that it should be fixed, and marks it as such in the ticket. See Trac Keywords list (below).
A BuddyPress developer (which could be you) decides to fix the bug. The developer may choose to take responsibility for the bug by clicking on the Accept ticket option near the bottom of the ticket, though this is not required. Then the developer fixes the bug, creates one or more patch files, and uploads them to Trac.
Other BuddyPress developers may check the patch to see if it fixes the bug and doesn』t break anything else. They add comments and keywords to the ticket to indicate their results. See Trac Keywords list (below).
Andy Peatling (the only BuddyPress developer with authority to modify the official BuddyPress source code) will then commit the patch to the core code.  This means the fix will be included in the next release of BuddyPress.

Details of Bug Reporting and Resolution
The sections below add details to some of the steps outlined above.
Before You Report a Bug
Your bug may have already been reported. It』s very important to check to be sure it』s not already in the system before you submit it. If you are new to reporting bugs in BuddyPress or WordPress, it is also a good idea to discuss the issue with more experienced developers before reporting it. Please follow the steps below.

Search for your bug or feature request in Trac.

If your issue has already been reported, please do not report a duplicate bug. If you have further information to contribute, log in and add a note to the existing bug.
If your issue is similar, but not quite the same as another issue, you may decide whether to add a note to the similar issue, or report a new one. It can be difficult to decide whether your issue warrants a new submission, but in general if you just have more information to contribute to a current, open issue, simply add a note to that issue. If you have a different enough issue, or if you are experiencing a recurrence of an issue that was previously resolved, report a new bug.
If your issue was recently reported and then closed, and you do not agree with the resolution, you can also reopen the ticket and add a comment as to your reasoning.

To discuss a bug before reporting it in Trac (e.g. to figure out if it is really a bug in the core of BuddyPress and not in a Plugin or Theme), you can post a question on the BuddyPress Support Forum or discuss your issue on the #buddypress-dev IRC channel (irc.freenode.net).

Reporting a Bug
To report a bug, read Before You Report a Bug (above), and verify that you have a new bug that is appropriate to report.

Log into BuddyPress Trac using your forum username and password and select New Ticket in Trac to reach the bug reporting page.
Fill in the following fields on the new ticket page.

Short Summary
Make the summary short but informative and accurate, as this is the ticket title that will be displayed in search results.

Full Description
Fill in a full description of your bug or feature request. Include a description of the problem, steps someone else would have to take to reproduce the problem and maybe an example of the bug in action (i.e. a URL) or a screenshot. The better your description, the easier it is for a developer to find the bug.

Priority
Unless it is a critical bug, this is best left to the default as developers will usually rank the bug』s priority.

Assign to (optional)
You can also take responsibility for the bug yourself, by putting your username here.

Milestone
By what version this issue should be resolved, at the latest. Do not change this. This is an option that a BuddyPress developer will set.
Keywords
Keywords identify the areas the bug affects. An example might be 『wire』 for a bug involving the Wire component. Also, there are some standard keywords used to flag your bug』s status (see Trac Keywords below).
CC (optional)
Who bug information and updates should be sent to. If you want to be kept informed, enter your email address. You will then be notified by email any time a change is made to this report, or a note to the bug is added. Note: If you are the bug』s reporter, you will already get messages, so no need for CC.

Trac Keywords
There are a number of keywords with defined meaning used in Trac that are commonly used.

reporter-feedback
A response is needed from the reporter. Further investigation is unlikely without a response to the questions from someone experiencing the problem.
has-patch
A solution to the ticket has been attached, and it is ready for review and/or committing.
needs-testing
Someone needs to test the solution.
2nd-opinion
Another person is needed to express an opinion about the problem or the solution.
dev-feedback
A response is wanted from a developer (not commonly used).
tested
The patch has been tested. When adding this tag please comment with the patch filename that was tested, how the patch was tested, and which version of BuddyPress was used.
needs-patch
The ticket has been reviewed, found to be desirable to solve, and marked as especially needing a patch, or the submitted patch doesn』t work and needs to be redone.

Finding Bugs to Fix
Please view this forum post as it continues links to a number of Trac reports, allowing you to see which bugs are still awaiting a fix.

已棄用

已棄用

Codex Home → Developer Resources → Deprecated
Deprecated

The following functions are considered deprecated as of BuddyPress 1.1. They will still work, but have been replaced by newer, more powerful functions. In the future, codex documentation will link current and deprecated functions together so you can see the differences and understand how to migrate from one to the other.

常見問題

常見問題

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.

官方標誌和字型

官方標誌和字型

Codex Home → Official Logos and Typeface
Official Logos and Typeface

Need an official BuddyPress logo? Want to show your BuddyPress pride with a button on your blog? You』ve come to the right place. When you need the official BuddyPress logo for a web site or publication, please use one of the following. These are the real deal.
BuddyPress Logo Font
Fontin from the exljbris font library.
BuddyPress Logo (Vector PDF)

BuddyPress Logo (PNG)

BuddyPress Text Logo (PNG)

BuddyPress Disc Logo (PNG)

Large Icons (.psd)

Menu Icons (.psd)

Colors
Bright Red: #d84800
White: #FFFFFF
BuddyPress Wallpapers

BuddyPress Logo with Light Background

640×960 Smartphones
1024×768
1440×900
2048×1536 iPad
2560×1400
2880×1800 for Retina display

 
 
BuddyPress Logo with Blue Background

640×960 Smartphones
1024×768
1440×900
2048×1536 iPad
2560×1400
2880×1800 for Retina display

BuddyPress Logo (SVG)

Dashicons Icons

BuddyPress Logo: content: "f448"; – class="dashicons dashicons-buddypress-logo"
BuddyPress Activity: content: "f452"; – class="dashicons dashicons-buddypress-activity"
BuddyPress Community: content: "f307"; – class="dashicons dashicons-buddypress-community"
BuddyPress Friends: content: "f454"; – class="dashicons dashicons-buddypress-friends"
BuddyPress Groups: content: "f456"; – class="dashicons dashicons-buddypress-groups"
BuddyPress PM: content: "f457"; – class="dashicons dashicons-buddypress-pm"
BuddyPress Tracking: content: "f???"; – class="dashicons dashicons-buddypress-tracking"