Updating pages/posts with large amount of copy throws error

I am trying to save a large chunk of data to a post via API, but I am getting an error:

Unhandled rejection Error: URI Too Long
superagent/lib/node.index.js:688:17
superagent/lib/node/index:js:911:12

I printed a few things to the console and noticed that all API requests are GET requests. Looking at the API documentation (and as a REST library), it should be using the POST & DELETE request types for creating, update and delete.

http://v2.wp-api.org/reference/pages/ http://v2.wp-api.org/reference/posts/

[kadamwhite]

Thanks, I understand the issue but I need to look into why it wouldn’t be sending things by POST. I will investigate.

[nbyloff]

Ugh. I totally see that now. I didn’t read the docs completely. Glancing at the examples looked pretty straight forward for the small test I was doing. But yes, it works as expected now. It even seems to save my custom meta field data in my original example now. Going to see if it saves the actual CSS data tomorrow instead of my test data.

Personally, I’d like the library to mirror the actual commands, paths, requests, etc. you would see in the API, like you currently have in the library. It would make for a pretty simple one to one mapping for an API call to your method(s). Now that I know the last method on the chain is the actual request type and not referring to an internal WP post command, it’s all clear & simple now.

I would tweak your readme file just a little bit for the skimmers like me to make it a little more clear. Make the comment on get, post, put, delete in the beginning of the examples and probably add a couple that aren’t modifying posts.

Again, sorry for the confusion. Had a launch over the weekend and I am getting diminishing returns last couple days. hah.