# Setting timerange for the Lates Topic first screen for invited users

**URL:** <https://meta.discourse.org/t/setting-timerange-for-the-lates-topic-first-screen-for-invited-users/50941>\
**Category:** Product Support\
**Created:** [1 Octubre, 2016 05:12 UTC](https://meta.discourse.org/t/setting-timerange-for-the-lates-topic-first-screen-for-invited-users/50941 "2016-10-01T05:12:28Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)\
**Post date:** [10 Octubre, 2016 15:46 UTC](https://meta.discourse.org/t/setting-timerange-for-the-lates-topic-first-screen-for-invited-users/50941/14 "2016-10-10T15:46:23Z")

</div>

Found it.

discovery.js.es6 has the following

> <https://github.com/discourse/discourse/blob/5dbd6a304bed5400be481d71061d3e3ebb4d6785/app/assets/javascripts/discourse/routes/discovery.js.es6#L13-L21>

Which then utilizes the `redirect_to_top.period` found in user\_option.rb

> <https://github.com/discourse/discourse/blob/5dbd6a304bed5400be481d71061d3e3ebb4d6785/app/models/user_option.rb#L86-L110>

And that method pulls its value for the time period from `min_redirected_to_top_period`

> <https://github.com/discourse/discourse/blob/5dbd6a304bed5400be481d71061d3e3ebb4d6785/app/models/site_setting.rb#L100-L107>

The site\_setting.rb doesn’t take into account the default time period. It simply returns the first time period that has enough topics to meet `topics per period in top page` site setting

---

_[View the full topic](https://meta.discourse.org/t/setting-timerange-for-the-lates-topic-first-screen-for-invited-users/50941)._