Haldan

Final update: well, I feel a little dumb. After hours of trying to google what the global query context refers to, and digging through the Gutenberg and Tove code, it turns out “inherit query from template” is a misnomer. It doesn’t inherit the query settings from the currently used template (which makes sense, since the query loop block likely lives on the template page itself anyway). If you have this toggle enabled, worpress will ignore any other settings you hard code in the template. What this actually refers to is the global WordPress “Reading” settings in the dashboard. It’s been so long since I bothered to think about those settings, I had forgotten all about them. On this settings screen, it was a simple task to just change the number of posts shown on the home page from 10 to the desired number 21. Easy peasy.

It seems like a real oversight for Gutenberg to use this verbiage, and I’m comforted to know I’m not the only person who has totally misunderstood this. Hopefully this is corrected in future Gutenberg updates, and as importantly, I hope that Gutenberg folks figure out a way to either (a) keep the toggle enabled but offer a way to limit posts in the query by category, etc., or (b) find a way to get search and archive to work within the custom query loop. (or both)

Another update: I think I figured out how this kind of customization is intended to work. I edited the index template manually to include 21 posts in the query, instead of 10, but that hasn’t seemed to work. It’s still showing only 10 posts on the main page. Strange quirk though, inside the site editor it shows a preview of 21 posts–but it doesn’t render that way when published.

I’ve also asked this question on the Gutenberg forum, but if you have any insight, or if you suspect this may be a Tove issue, please do reply. Thanks.

Similar issue, so I thought I’d post it here instead of making a new thread. Do you know if the Archives function of the query loop also doesn’t work? I’m wondering if it suffers from the same issue that the search function does, if perhaps the issue lies in rendering a select group of posts in the query. You can see at the bottom of the page I have an option to display archives by month, but when you click on them, it just returns the homepage–instead of the archived posts.

Aha thanks. Do you know if there are any wp search plugins that work with Gutenberg & Tove? I’ll experiment to see if I can find one. Thanks again.

• This reply was modified 4 years, 6 months ago by Haldan.

Thanks Anders. So just to be clear, your experience is that search doesn’t yet work in Tove correctly because Gutenberg has yet to work out the kinks?

Hi Anders,

That makes sense re: the safari issue. I’m not running the most current version.

Re: the post content, yes that is working fine for me too, but the issue I’m still having (which is what I thought you were referring to above) is the spacing of the navigation elements. Since 0.2.2, the navigation elements are again spaced far apart — and the using the background color thing you suggested initially for that problem no longer works (now when I add bg color, it only affects top and bottom margins on the navigation block, but doesn’t change anything about the spacing between the elements). Is there any way I can reduce the spacing on the spacing on the navigation elements to return to how it was pre-0.2.2?

Thanks again.

Oh and I just noticed, the post content margin fix in 0.2.2 doesn’t seem to change anything in Safari either. Maybe this is just a known problem with the way blocks work in Safari, but again, thought I’d mention it.

I’ve also noticed that since 0.2.2 the margin fix I mentioned above no longer seems to work in chrome. Now, whether or not I have a background color on the navigation block, the margins seem to be too wide, and I can’t seem to get the links to sit closer together again (on chrome only. on safari, they’re still extremely close together.)

• This reply was modified 4 years, 7 months ago by Haldan. Reason: another thing I realized