-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend the utility of pagination blocks #33357
Comments
Hey 👋 - there is |
Thanks for your reply. I didn't see those ones because I was testing with core version 5.8 and had the plugin deactivated. After looking more closely, I see there is also a Table of Contents block that possibly might act as an equivalent to |
Table of contents blocks has some issues that need to be resolved first. Check this PR for more info: #29718 |
Closing as duplicate of #29484 |
There are a number of different pagination template tags that exist, with different purposes.
previous_posts_link
andnext_posts_link
are designed to paginate queries that are! is_singular()
. This is what the Query Pagination block currently does.There are also
previous_post_link
andnext_post_link
, which are designed to paginate queries that areis_singular()
. These currently have no block equivalent, as far as I'm aware.Furthermore, there is
wp_link_pages
. This also paginates queries that areis_singular()
, but does so in terms of intra-post pagination rather than inter-post pagination. The Page Break block is designed to work together with this template tag, but the template tag itself currently has no block equivalent, as far as I'm aware.The easy solution is to add new blocks for these template tags, but it might be worth exploring the viability of simplifying them all into the Query Pagination block and automatically determine which kind of pagination to use in which context.
The text was updated successfully, but these errors were encountered: