# Klipy issue when "Limit infinite search results" is set

**URL:** https://meta.discourse.org/t/klipy-issue-when-limit-infinite-search-results-is-set/402679
**Category:** Bug
**Tags:** gifs
**Created:** [May 11, 2026, 5:00pm UTC](https://meta.discourse.org/t/klipy-issue-when-limit-infinite-search-results-is-set/402679 "2026-05-11T17:00:37Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [May 11, 2026, 5:00pm UTC](https://meta.discourse.org/t/klipy-issue-when-limit-infinite-search-results-is-set/402679/1 "2026-05-11T17:00:37Z")

</div>

The Klipy categories are not paginated, it’s a single call to get all categories.  
However, there is a `@loadMore={{this.loadMore}}`.

When the “Limit infinite search results” option is enabled, `loadMore` triggers and Klipy gives an error because there is no `q` parameter.

 ![image](https://global.discourse-cdn.com/meta/original/4X/1/8/f/18fb2d35e3e297c9ea3cc426a30fa47a9486baab.jpeg)

Solution:

- remove `loadMore` from the category display, see [PR](https://github.com/discourse/discourse-gifs/pull/133)

---

_[View the full topic](https://meta.discourse.org/t/klipy-issue-when-limit-infinite-search-results-is-set/402679)._