Skip to content
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: Make users aware that Query Loop might be overriding "Posts per page" setting #64527

Open
alaczek opened this issue Aug 15, 2024 · 1 comment
Labels
[Type] Enhancement A suggestion for improvement.

Comments

@alaczek
Copy link

alaczek commented Aug 15, 2024

What problem does this address?

We have "Posts per page" setting in Settings > Reading, which can also be accessed in the Editor, when editing template such as home.html:
image

Query Loop block can override that setting though by disabling "Inherit query from template" option in block settings. In that case a custom "Posts per page" setting is available on the block level. This is confusing for the customers, because:

  • the Query Loop custom posts per page setting is somewhat hidden, accessible only from the floating toolbar.
  • there is no mention anywhere that global "Posts per page" setting is being overridden.
posts-per-page-2.mp4

What is your proposed solution?

I'm not quite sure what the solution is. Could the global and the custom "posts per page" settings be aware of each other, so that we can let users know that their settings are being overridden?

Perhaps we could include a message here?
image

Another thing that might be useful is making the Query Loop's block "Posts per page" setting more visible by putting it in the block settings in the sidebar too?

@nirav7707
Copy link
Contributor

Do we need to added static info. or need to compare both post per page, and only display notice if both are different ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

2 participants