You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a page called "Blog" which I have configured as the "Posts Page" via WP Settings -> Reading. This page's ID is 20. I then have a couple of test posts created, with the intention of building a post archive template from this data.
However, when I query the endpoint better-rest-endpoints/v1/page/20, I get the following response:
{
id: 25,
title: "Pluto is definitely a planet",
slug: "pluto-is-definitely-a-planet",
permalink: "domain/pluto-is-definitely-a-planet/",
template: "default",
content: "<p>TRUST ME! Don’t listen to Neil DeGrasse Tyson.</p> ",
parent: false,
acf: null,
yoast: null,
media: false
}
This is actually the data pertaining to the most recent post which would be shown within that archive, as opposed to what you'd expect to return (the data for the actual archive page itself, i.e. { id; 20, title: "Blog", slug: "blog", permalink: "domain/blog/", etc etc. }). When I visit the default WP REST API endpoint for this page (wp/v2/pages/20) I do get the correct object in response.
The text was updated successfully, but these errors were encountered:
I have a page called "Blog" which I have configured as the "Posts Page" via WP Settings -> Reading. This page's ID is 20. I then have a couple of test posts created, with the intention of building a post archive template from this data.
However, when I query the endpoint
better-rest-endpoints/v1/page/20
, I get the following response:This is actually the data pertaining to the most recent post which would be shown within that archive, as opposed to what you'd expect to return (the data for the actual archive page itself, i.e.
{ id; 20, title: "Blog", slug: "blog", permalink: "domain/blog/", etc etc. }
). When I visit the default WP REST API endpoint for this page (wp/v2/pages/20
) I do get the correct object in response.The text was updated successfully, but these errors were encountered: