Skip to content

Archive page > QL is tied to reading setting's Blog Max Post and can generate 404 through pagination rel next (block setting vs old classic way) #79822

Open

Description

@Marc-pi

What problem does this address?

Adding a query loop block into an archive template make the pagination be tied to the Reading's Setting Max Post
despite we are under the FSE Paradigm.

Example : Add a QL into an archive page, with 15 items, set the Item per page block setting to 25
In this case, the page 2 URL is generated

generating a 404 error, since the page cannot be generated, there is no data to show since 15 < 25

Despite the pagination block is deleted, the block still generates the link rel="next"

The explanation : the pagination use the old way despite there is a block dedicated setting
Settings > Reading > Blog pages show at a most (10 is the default value on fresh installs)

Can be linked to this issue #63028

What is your proposed solution?

Stop using the Reading's Blog Max Post to Show !!!
it's time to move to full full FSE ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions