1
0
Fork 0
mirror of https://github.com/buddypress/buddypress.git synced 2026-07-20 19:56:12 +08:00
BuddyPress DEVELOPMENT repo. This repository is just a mirror of the development SVN at https://buddypress.svn.wordpress.org/. Please include a link to a pre-existing ticket on https://buddypress.trac.wordpress.org/ with every pull request. https://buddypress.org
  • PHP 75.3%
  • CSS 14.6%
  • SCSS 6%
  • JavaScript 4.1%
Find a file
David Cavins 962f764f16
Some checks failed
Unit Tests / tests (false, , 8.2, 6.4) (push) Has been cancelled
Unit Tests / tests (true, memcached, 8.5, 6.9) (push) Has been cancelled
Unit Tests / tests (false, , 7.4, 6.4) (push) Has been cancelled
Unit Tests / tests (false, , 8.1, latest) (push) Has been cancelled
Unit Tests / tests (false, memcached, 8.3, trunk) (push) Has been cancelled
Unit Tests / tests (false, redis, 8.5, trunk) (push) Has been cancelled
Unit Tests / tests (true, , 7.4, 6.4) (push) Has been cancelled
Unit Tests / tests (true, redis, 8.3, trunk) (push) Has been cancelled
Unit Tests / tests (true, redis, 8.4, trunk) (push) Has been cancelled
Components: Restrict updates to site admins.
Ensure that the current user has the `manage_options` capability before allowing them to change BuddyPress component status.

Special thanks to kasthelord (Lukas Collishaw) who first reported this issue responsibly.

Props emaralive, johnjamesjacoby, espellcaste, kasthelord (Lukas Collishaw), 1353594865qq, jeromewincek (Jerome Wincek), vvh1te3zz.

git-svn-id: https://buddypress.svn.wordpress.org/trunk@14214 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
2026-07-07 20:02:23 +00:00
.github Add PHP 8.5 to our CI matrix. 2025-12-16 15:45:11 +00:00
.phpcs Testing BuddyPress against its own/new PHP Code Sniffer (PHPCS). 2022-09-11 18:22:23 +00:00
docs Docs: Update "BuddyPress PHP Version Support" doc. 2025-12-30 19:56:23 +00:00
src Components: Restrict updates to site admins. 2026-07-07 20:02:23 +00:00
tests Components: Restrict updates to site admins. 2026-07-07 20:02:23 +00:00
.editorconfig Raise the minimum supported WordPress and PHP versions. 2024-09-02 22:45:11 +00:00
.gitignore Migrate from ParcelJS to @wordpress/scripts (Webpack) 2023-04-25 19:11:08 +00:00
.jshintignore Migrate from ParcelJS to @wordpress/scripts (Webpack) 2023-04-25 19:11:08 +00:00
.jshintrc Build: Use tabs for indentaion, follow up to [11946] 2018-04-04 09:53:03 +00:00
.npmrc Add PHP linting to travis:phpunit and commit Grunt tasks. 2018-07-24 01:51:07 +00:00
.stylelintrc Introduce a new Theme Compat feature firstly designed for Block Themes 2023-11-27 22:55:27 +00:00
blueprint.json Improve BuddyPress compatibility with WP Playground previews 2024-11-01 06:07:04 +00:00
bp-loader.php Raise the minimum supported WordPress and PHP versions. 2024-09-02 22:45:11 +00:00
composer.json CI: test against PHP 8.4. 2025-02-16 15:13:17 +00:00
Gruntfile.js Include the V2 of the BP REST API in BuddyPress core. 2024-09-27 21:11:27 +00:00
npm-shrinkwrap.json Update the npm @wordpress/env package to version ^10.8.. 2024-09-28 03:39:47 +00:00
package.json Bump the WP CLI BuddyPress version to 3.0.2. 2025-02-16 16:34:25 +00:00
phpcs.xml.dist WPCS - miscellaneous fixes for the BP Settings component. 2025-04-19 13:12:19 +00:00
phpunit-watcher.yml.dist Adding the phpunit-watcher config file. 2024-02-23 00:18:33 +00:00
phpunit.xml.dist Include the V2 of the BP REST API in BuddyPress core. 2024-09-27 21:11:27 +00:00
README.md Delete the custom wp-env.json file. 2025-02-16 15:22:17 +00:00
SECURITY.md Add README.md and SECURITY.md files to the project 2020-10-09 05:13:56 +00:00

BuddyPress

Unit Tests

Welcome to the BuddyPress development repository! This repository is a mirror of our development SVN repository. Please do not send pull requests here, instead submit patches to our SVN repository. Check out the Participate & contribute page of our Codex for information about how to open bug reports, contribute patches, test changes, write documentation, or get involved in any way you can.

Getting Started

BuddyPress is a WordPress plugin to power you community site. It is a PHP, MySQL, and JavaScript based project, and uses Node for its JavaScript dependencies. A local development environment is available to quickly get up and running.

You will need a basic understanding of how to use the command line on your computer. This will allow you to set up the local development environment, to start it and stop it when necessary, and to run the tests.

You will need Node and npm installed on your computer. Node is a JavaScript runtime used for developer tooling, and npm is the package manager included with Node. If you have a package manager installed for your operating system, setup can be as straightforward as:

  • macOS: brew install node
  • Windows: choco install node
  • Ubuntu: apt install nodejs npm

If you are not using a package manager, see the Node.js download page for installers and binaries.

You will also need Docker installed and running on your computer. Docker is the virtualization software that powers the local development environment. Docker can be installed just like any other regular application.

Development Environment Commands

Ensure Docker is running before using these commands.

To start the development environment for the first time

npm install
npm run wp-env start

Your WordPress community site will be accessible at http://localhost:8888.

To stop the development environment

You can stop the environment when you're not using it to preserve your computer's power and resources:

npm run wp-env stop

To start the development environment again

Starting the environment again is a single command:

npm run wp-env start

Credentials

To log in to the site, navigate to http://localhost:8888/wp-admin.

  • Username: admin
  • Password: password

To generate a new password (recommended):

  1. Go to the Dashboard
  2. Click the Users menu on the left
  3. Click the Edit link below the admin user
  4. Scroll down and click 'Generate password'. Either use this password (recommended) or change it, then click 'Update User'. If you use the generated password be sure to save it somewhere (password manager, etc).