-
Notifications
You must be signed in to change notification settings - Fork 809
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
Blocks: Related Posts block displayed wrong on Page templates #39720
Comments
Looks like it accidentally worked before due to the style imploding, and broke when #39486 turned it off. cc @kraftbj @sergeymitr The real problem is that the styles and scripts only get enqueued on posts, specifically jetpack/projects/plugins/jetpack/modules/related-posts/jetpack-related-posts.php Lines 1889 to 1906 in 702274e
while the block itself gets rendered regardless. Something like this might work for a fix:
Looks like the 'jetpack_relatedposts_filter_enabled_for_request' filter could be used as a workaround. |
I'll put in a patch to allow it to be enqueued on pages as well. My understanding is the RP system will still kick out related posts on pages so let's continue to support that. |
Impacted plugin
Jetpack
Quick summary
The Related Posts block is missing styles on Page templates after the latest Jetpack update. It still works as expected on Single post templates. On Pages, the Related Posts are displayed as a simple vertical list, while on Posts, they are correctly shown in a three-column layout, as intended.
This was reported by a user here: https://wordpress.org/support/topic/related-posts-block-on-page-template-broken-style-since-last-update/
Steps to reproduce
A clear and concise description of what you expected to happen.
No response
What actually happened
No response
Impact
Some (< 50%)
Available workarounds?
No but the platform is still usable
If the above answer is "Yes...", outline the workaround.
No response
Platform (Simple and/or Atomic)
No response
Logs or notes
No response
The text was updated successfully, but these errors were encountered: