-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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: show correct posts after setting "Inherit query from template" #42675
Comments
I see this issue too. |
That's a quite hard problem.. For example if we have a Query Loop block in |
Yeah, this seems really tricky to think through. I'd be keen to hear from @WordPress/gutenberg-design in this sense as it does feel like a design problem almost. How do you indicate something has changed but that it might not perfectly reflect what you're seeing in the editor, especially when it aims to be WYSIWYG? |
Similarly it would be nice if the Archive Title block displayed a more contextual placeholder. E.g. in the |
This is still a problem with WordPress 6.2. |
Hi @annezazu, I think this issue has been fixed and we missed closing it. Can you confirm if things now work well for you? Thank you in advance 😊 |
It works! Here's a video: works.mov |
Description
After creating one of the new templates (categories, tags, date, author, etc), adding a Query Loop block, and setting it to "Inherit query from template", it's not clear that the query loop will correctly show posts based on the template. Instead, nothing changes in the editor (same posts are shown), despite the query loop working correctly on the front end. I understand this might be intentional for a template like Author or Date since that'll depend on which author is being viewed but for templates around categories or tags this proves to be confusing.
This was found as part of the fifteenth call for testing for the FSE Outreach Program.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: