- Issue created by @ricovandevin
I got the same error and for me it turned out that I didn't have the parameters set in the services.yml file. I had to add the following to the parameters in services.yml:
jsonapi_page_limit.size_max:
/jsonapi/taxonomy_term/my_taxonomy_term: 100My last post doesn't address the issue when you try to limit the page, but you haven't set a max in the services.yml file. This still triggers that error. So I'm posting a patch here that I think fixes this issue.
- Status changed to Needs review
12 months ago 9:46pm 1 December 2023 This seems to be still an issue in 1.1, so I've changed the version to 1.1, and am moving the status to needs review, for someone to take a look at the patch and see if it solves the problem.
- 🇷🇴Romania CatalinMatea
I encountered this issue and the case was that the parameter page[limit] was changed to page[size]
- First commit to issue fork.
- Merge request !11#3362958: Error for page that do not have an explicit page size set → (Merged) created by Eli-T
- 🇬🇧United Kingdom Eli-T Manchester
We came across this converting a site to multilingual - we had a limit in services.yml for /jsonapi/* routes but not /cy/jsonapi/*.
This patch fixes that issue.
(we're going to add a limit for the other language anway).
Thanks everyone!