This patch addresses an issue where WordPress 6.0 and higher mistakenly tweaks unpaginated queries as comment-paginated, causing indexing issues when using Full Site Editing or themes that prerender Blocks before TSF.
Detailed log
> View code changes.
> No GitHub issues were closed.
For everyone
- Fixed: Addressed an issue where TSF deemed a query comment-paginated when it wasn’t. This is a bug in WordPress 6.0 and higher affecting TSF, WordPress itself, and 200 other plugins.
- This can happen when using FSE (Full Site Editing) or a theme that renders blocks early. With this, the
cpage
(comment-page) query variable always gets rewritten to a greater number than the actual page we’re on; the comment block never adhered to that number, but it told WordPress, TSF, and 200 other plugins to act like we’re on a comment-paginated page. - We couldn’t find a reason for the cause of this issue other than an oversight during local development of Gutenberg’s merger with WP 6.0. To learn more, visit https://core.trac.wordpress.org/ticket/60806.
- Props DreamOn11 and Dmitry for reporting and helping to debug this issue.
- This can happen when using FSE (Full Site Editing) or a theme that renders blocks early. With this, the
For translators
- Changed: Updated translations are available.
- Updated: The POT file contains new and changed translations.
For developers
- Added: Method
tsf()->query()->is_comment_paged()
is now available. - Fixed:
tsfTabs.toggleTab()
(added in TSF v5.0.5) without using the third parameter now works as intended.