Changeset 14026 for trunk/docs/contributor/code/README.md
- Timestamp:
- 09/27/2024 09:11:27 PM (15 months ago)
- File:
-
- 1 edited
-
trunk/docs/contributor/code/README.md (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/docs/contributor/code/README.md
r13769 r14026 111 111 ``` 112 112 113 You should see that your `~/Plugins/buddypress` directory now contains 1 or 2 more sub directories: `/node_modules` and `/vendor` if you installed the composer packages.113 You should see that your `~/Plugins/buddypress` directory now contains 1 or 2 more subdirectories: `/node_modules` and `/vendor` if you installed the composer packages. 114 114 115 115  … … 121 121 ``` 122 122 123 The first time you’ll execute this command it will take some time to run and you’ll see that 2 downloads will start: 124 125 - [BP REST](https://github.com/buddypress/BP-REST): it’s the plugin we use to develop the BP REST API. 123 The first time you’ll execute this command it will take some time to run, and you’ll see that the following download will start: 124 126 125 - [WordPress](https://core.trac.wordpress.org/browser/trunk): it’s the WordPress development version. 127 126 … … 176 175 ### Customizing your BuddyPress local development environment 177 176 178 To develop BuddyPress we use the development version of [WordPress](https://core.trac.wordpress.org/browser/trunk), the development version of the [BP REST API](https://github.com/buddypress/BP-REST)and we set two debugging constants:177 To develop BuddyPress we use the development version of [WordPress](https://core.trac.wordpress.org/browser/trunk), and we set two debugging constants: 179 178 180 179 ```php … … 190 189 { 191 190 "core": "WordPress/WordPress#master", 192 "plugins": [ ".", "buddypress/ BP-REST#master", "buddypress/bp-classic#trunk" ],191 "plugins": [ ".", "buddypress/bp-classic#trunk" ], 193 192 "config": { 194 193 "WP_DEBUG": true, … … 206 205 ## Patching BuddyPress 207 206 208 Let’s work with a real bug example (It might ha sbeen fixed when you’ll read this page!) to understand how to suggest a fix to the BuddyPress development team. First, open the `~/Plugins/buddypress` directory into your favorite code editor.207 Let’s work with a real bug example (It might have been fixed when you’ll read this page!) to understand how to suggest a fix to the BuddyPress development team. First, open the `~/Plugins/buddypress` directory into your favorite code editor. 209 208 210 209 
Note: See TracChangeset
for help on using the changeset viewer.