Maximum number of posts exceeded

Hi there,

The post grid wasn’t initially designed to be the main display of posts on your site, rather used as a section to display latest posts. Also, it uses the WP API and that limits the posts you can retrieve at once.

Large queries can hurt site performance, so per_page is capped at 100 records. If you wish to retrieve more than 100 records, for example to build a client-side list of all available categories, you may make multiple API requests and combine the results within your application.

With the arrival of full site editing this fall, we’ll be able to update this block to be used as a full post display with pagination, etc.

@atomicblocks :

Agreed with @arneby in that we are appreciating Atomic Blocks as helpful supplements to our Genesis ecosystem, and I too was jumping on here to post on this very topic: limited queries via the Posts and Page Grid block.

Curious how you are querying even 100 records. The ab_postgrid_offset value is capped at 20, and changing this doesn’t seem to increase the number of callable records.

With the arrival of full site editing this fall, we’ll be able to update this block to be used as a full post display with pagination, etc.

To lend another feedback voice in this regard: use of this block as a “full post display with pagination” would be incredibly helpful for your users. Would this use-case mean that the block would be a main or secondary query on page load?

And thanks to the SP and WP Engine teams for investing additional engineering resources toward growing AB and GF into even more robust solutions.

OK, I understand now that the limiting factor is actually the WP API. I will find another solution then. Thank you.

@cyborg88 We’re still exploring what kind of query impacts this kind of change would have. At any rate, we’re full steam ahead on Full Site Editing and more advanced blocks! We’ll put out more details into the community as soon as we learn more.