Sheath rule
statamic-incompatible-query-parameters
Statamic result queries cannot combine incompatible pagination, chunking, and
limiting parameters.
#Why
Statamic's guarded query path rejects paginate with chunk. Numeric
pagination also conflicts with a nonzero limit.
#Examples
#Bad
{{-- paginate conflicts with chunk and with a nonzero limit. --}}
<s:collection:articles paginate="10" chunk="2" />
<s:collection:articles paginate="10" limit="20" />
{{-- Fluent calls use the same compatibility rules. --}}
{{ Statamic::tag('collection:articles')->paginate('10')->chunk('2') }}
#Good
{{-- Boolean pagination can be combined with a limit. --}}
<s:collection:articles paginate limit="20" />
#Scope
The restriction applies to collection and taxonomy result methods, dictionaries, queries, form submissions, search results, user listings, and other core methods that support these result controls.
Count methods and unrelated tag methods are not checked.
#Notes
Dynamic values are skipped when their numeric or boolean meaning cannot be known. Conditional attributes are evaluated per reachable render path, so mutually exclusive parameters are not treated as one query.
#See Also
Related rules cover narrower query contracts:
- statamic-assets-path-requires-container: Require an asset source for path queries
- statamic-collection-method-compatibility: Check collection navigation methods