-
Notifications
You must be signed in to change notification settings - Fork 78
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
Query loop not working with more than 3 results or changing results number in the block #1220
Comments
How strange— it looks like changing the "items per page" value is also changing the
Increasing the offset just added to it:
Off the top of my head, I don't know what could be interfering there. |
Yes, it's very strange. I made a test in another multisite (that it isn't a WordCamp multisite) and the Query Loop works without any problem (and works with the number as integer and as string). |
I'd imagine it's some filtering |
In my testing, the offset was The strange part to me is that the API request is what's changed, so the API response is correct (to what it's asked for) but somewhere in the "fetch posts" logic it's changing the query. |
Oh, it's not math but concatenation — |
Oh, fantastic news, but WordCamp.org could be updated to 17.2? or we have any solution to this to finish our team design and go live? |
Gutenberg has been updated to 17.5.1, which resolves the issue. |
It looks like that upgrade broke the query-filter block on events.w.org, see #1225 for details |
Unfortunately we've had to temporarily roll back Gutenberg to 17.1.4 to fix the above issue with the Events homepage query filters, so this issue will be present again. We plan to ship another fix asap. Sorry for any inconvenience caused. |
The WordCamp network has been updated to Gutenberg 17.6, so this should be fixed again. |
Query loop block it's not working if we change the number of results to show because saves as string and only works as string.
This happens in the WordCamp multisite. Checked in another multisite non-WordCamp and working fine.
To reproduce
Steps to reproduce the behaviour:
We have the problem with our staging website https://wceutest24.wordcamp.org/2024/ and also live website https://europe.wordcamp.org/2024/
A recorded a video with several tests and the bug: https://video.tabernawp.com/conversations/fa2cdc82-7f9a-570d-9769-b2e351641649
The text was updated successfully, but these errors were encountered: