Skip to content

Commit b9cb501

Browse files
committed
Update outmoded "WP REST API" references in documentation
1 parent 6e5e2cf commit b9cb501

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

CONTRIBUTING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The unit tests can be run without any additional setup with `npm run test:unit`,
1414

1515
### Integration Tests
1616

17-
In order to run the integration tests you will need to run a local WP REST API instance in a virtual machine as described in [wpapi-vagrant-varietal](https://github.com/kadamwhite/wpapi-vagrant-varietal). Full instructions are provided there, and once that VM is running the integration tests will pass. (You can run the integration suite specifically with the command `npm test:integration`).
17+
In order to run the integration tests you will need to run a specifically-configured local WordPress instance in a virtual machine as described in [wpapi-vagrant-varietal](https://github.com/kadamwhite/wpapi-vagrant-varietal). Full instructions are provided there, and once that VM is booted and running the integration tests will pass. (You can run the integration suite specifically with the command `npm test:integration`).
1818

1919
### Adding Tests
2020

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@ wp.posts().create({
200200
})
201201
```
202202

203-
This will work in the same manner for resources other than `post`: you can see the list of required data parameters for each resource on the [WP REST API Documentation Website](https://developer.wordpress.org/rest-api/reference/).
203+
This will work in the same manner for resources other than `post`: you can see the list of required data parameters for each resource on the [REST API Developer Handbook](https://developer.wordpress.org/rest-api/reference/).
204204

205205
### Updating Posts
206206

@@ -225,7 +225,7 @@ wp.posts().id( 2501 ).update({
225225
})
226226
```
227227

228-
This will work in the same manner for resources other than `post`: you can see the list of required data parameters for each resource on the [WP REST API Documentation Website](https://developer.wordpress.org/rest-api/reference/).
228+
This will work in the same manner for resources other than `post`: you can see the list of required data parameters for each resource in the [REST API Developer Handbook](https://developer.wordpress.org/rest-api/reference/).
229229

230230
### Requesting Different Resources
231231

@@ -851,7 +851,7 @@ More robust authentication methods will hopefully be added; we would welcome con
851851
852852
### Cookie Authentication
853853
854-
When the library is loaded from the frontend of the WordPress site you are querying against, you can utilize the build in [Cookie authentication](https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/#cookie-authentication) supported by WP REST API.
854+
When the library is loaded from the frontend of the WordPress site you are querying against, you may authenticate your REST API requests using the built in WordPress [Cookie authentication](https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/#cookie-authentication) by creating and passing a Nonce with your API requests.
855855
856856
First localize your scripts with an object with root-url and nonce in your theme's `functions.php` or your plugin:
857857

0 commit comments

Comments
 (0)