# Search does not find a particular post (except when searching within topic)

**URL:** https://meta.discourse.org/t/search-does-not-find-a-particular-post-except-when-searching-within-topic/76941
**Category:** UX
**Created:** [December 29, 2017, 8:38pm UTC](https://meta.discourse.org/t/search-does-not-find-a-particular-post-except-when-searching-within-topic/76941 "2017-12-29T20:38:12Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [December 29, 2017, 10:31pm UTC](https://meta.discourse.org/t/search-does-not-find-a-particular-post-except-when-searching-within-topic/76941/3 "2017-12-29T22:31:44Z")

</div>

> [@Mittineague](#):
>
> You may not be seeing the topic for “relevance” but for “most viewed” it’s the third result and for “most liked” it’s the first.

Good point. It didn’t occur to me that changing the _sorting_ would yield different _results_. But I still don’t understand why the search yields the results it yields. So here’s my thinking:

To start with, I assume that the “sort by” field is for, well, sorting whatever was found in a particular order, i.e. that it does not change _what_ was found.

I also understand that [discourse limits the maximum number of (displayed?) search results to 500](https://meta.discourse.org/t/search-results-limited-to-50-each-time/34270/12) (up until earlier this year it was 50). So, I can see that, in principle, the displayed search results can differ because the top 500 may differ depending on the sorting criteria.

But! This is only the case if there is an actual 501st post that is being cut off. If there are only a few posts that contain the search string (as is the case in my example), then the displayed search results should be identical regardless of the sorting order. Discourse clearly is not doing that because in the OP example, the number of hits actually differs, depending on the sort order. I don’t understand it.

To put it in more UX terms: discourse says at the end of maybe two dozen hits: “No more results found” which is either trivial (because we’re at the end of the results list) or wrong (because there clearly are more posts containing the search term).

In the old days, when discourse limited the total number of hits and cut off everything below the top whatever-it-was, I can see But

---

_[View the full topic](https://meta.discourse.org/t/search-does-not-find-a-particular-post-except-when-searching-within-topic/76941)._