[Query Pagination] Move all instances to a pattern

[justintadlock]

The goal is to move any instance of the Query Pagination block to a pattern. This allows us to manage the pagination output from a single file. This is a very good thing for long-term maintenance (fewer potential bugs and no inconsistencies across usages). It would also make it more easily swappable with alternate pagination patterns on the templating side (swapping shouldn't be an issue in the editor).

Currently, pagination patterns are broken in WordPress. With the following fix, they can be included, but they do not use the correct /page/* links on inherited queries:

• Allow placing Query pagination inside groups and other containers WordPress/gutenberg#58602

Related issues:

• Query pagination doesn't work when inside a template part. WordPress/gutenberg#38684
• Block: Query Pagination: Pagination inserted as a template part or pattern does not work WordPress/gutenberg#48296

[carolinan]

This seems to have been fixed "somewhere in Gutenberg 18.x" if you don't mind testing it again.

[justintadlock]

@carolinan - This is still giving me the ?query-page=2 URLs on Gutenberg 18.3.

[codersantosh]

I'm still facing the same issue with the current Gutenberg version (19.3.0).

<!-- wp:pattern {"slug":"theme-slug/pagination"} /-->

Since many core/query block patterns are using the same pagination design, I’m temporarily resolving the issue in PHP by requiring pagination.php:

require 'pagination.php';