_paging.links empty?

[wa-rren-dev]

Having an issue where a basic request as below:

 wp.posts().perPage(2)
  .then((data) => {
    console.log(data)
  }

isn't returning a populated links object. The total and totalPages are coming in as expected but links is empty.

data = [
  { post },
  { post },
  _paging: {
    links: {},
    total: "26",
    totalPages: "13"
}]

Running WordPress 4.8 and node-wpapi 1.1.2.

[nikosolihin]

I'm experiencing this too. Have you been able to solve it @warrenkeith?

[wa-rren-dev]

@nikosolihin Nope afraid not! Project took a different direction so was moved off WordPress unfortunately.

I have this issue too, so I'm unable to use the getAll function reported in https://github.com/WP-API/node-wpapi. How can I do to fetch all the posts?
wpapi 1.1.2, WordPress 4.9, the "rel next" link is returned as an header

[computamike]

I am experiencing this issue - here's what I have found :

Here is a trace of the response coming back from wordpress

The docs say that a collection object should be enriched with a _paging property
and http-transport.js does seem to show a _paging property being set - however it also seems to be checking for headers x-wp-totalpages. Now I've only just found this but if the header doesn't exist then this returns a null - which may explain why it's not work - I've not confirmed this yet but I imagine this is a case issue.

Need to confirm with Wordpress docs what headers it should or could be returning. Have forked and may look at creating a check ignoring case.

[kadamwhite]

While I do not expect #408 to fully address this issue, I've added some safeguards which may improve things; they will be included in the next released version of the library, as will a change which will use a consistent (and different) library to parse links. I'm going to provisionally close this, and we can revisit after the next release if the issue persists.