Ryan McCue

FWIW, I don't think Heartbeat itself is a good candidate for the REST API; it's not a good conceptual fit, and provides a totally different API of its own. In...

Just as a note to the future, some quick thoughts on how we could do locking: edit locks are probably best implemented via a custom action, something like `/posts/%d/lock` as...

Note: `context` is _not_ a magic parameter, just a strong convention in the API. Magic parameters start with `_` are relate to the routing/infrastructure layer of the API, and those...

This is anything that could redirect or otherwise interrupt requests. We should recommend users pass `?_envelope` when dealing with "untrusted" HTTP clients and handle the responses themselves.

You can internally run requests quite easily: ``` php $request = new WP_REST_Request( 'GET', '/wp/v2/categories' ); $server = rest_get_server(); $response = $server->dispatch( $request ); ``` This is way cheaper than...

Added in [core recently](https://core.trac.wordpress.org/changeset/36529) per [this ticket](https://core.trac.wordpress.org/ticket/35329).

Ideally, everything should have it; at this stage, only General Settings works, and date/time requires a core patch at the moment.

Try setting it without the URL parameters (`http://localhost:8080/`) and see if that helps. You'll need the trailing slash too, I think.

It's an issue in the OAuth callback validation: the URLs aren't being normalised.

@pinksharpii Your callback URL needs to be exactly wherever the example client is hosted (must match scheme, host, port, and path). Are you hosting the example client at `https://website.com/success/`?