-
Notifications
You must be signed in to change notification settings - Fork 42
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
[HelpHub] [6.4] Query Loop Block #1223
Comments
Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels. |
Heads up @femkreations - the "block editor" label was applied to this issue. |
@Leonardus-Nugraha Assing this to me |
@femkreations "Enhanced pagiation" is now "Force page reload" with RC3. |
My comment is related to this issue. "Force page reload" (earlier Enhanced pagination) is in the query loop block's settings, not in pagination block. |
Thank you for clarifying @anandau . @femkreations or @Leonardus-Nugraha would you be able to update the issue please and move the items to the Query block issue? Thank you. |
Hello @anandau how are you getting on with this update please? There is also a new dev note on the main query loop for reference https://make.wordpress.org/core/2023/11/13/main-query-loop-handling-for-block-themes-in-6-4/ |
Hi @abhansnuk I was away from work last week due to Diwali celebration. I will get it ready for review in next couple of days. |
Thank you for the update @anandau . Diwali and Sal Mubarak. |
New section to add after Sticky posts section Force page reloadThis option defined the behavior of the pagination block used within the query block. |
Heads up @docs-reviewers - the "[Status] Review" label was applied to this issue. |
@anandau @Leonardus-Nugraha |
I do not have the bandwidth to work on this issue, so I am removing myself. |
Article: https://wordpress.org/documentation/article/query-loop-block/
Updates for 6.4
General
Good first issues
If you are looking for simpler tasks, take a look at related good first issues:
The text was updated successfully, but these errors were encountered: