모바일에서는 정렬 기능이 이미 크게 제한되어 있으므로, 생성 날짜는 정보 제공 목적으로만 기능합니다. 생성 날짜가 뱀프(bumped) 날짜와 다를 경우에만 추가 필드가 표시됩니다.
토픽 목록 썸네일과의 호환성은 제한적입니다. 목록 스타일에서는 정상적으로 작동합니다. 블로그 스타일에서는 생성 날짜가 우하단으로 이동합니다. 그리드 스타일과 메이슨리 스타일에서는 “생성됨” 필터가 선택된 경우에만 생성 날짜가 보이며, 활동 날짜를 대체합니다. 미니멀 스타일에서는 생성 날짜가 숨겨집니다.
Huh. That’s interesting. Looks like it’s just an odd side effect of how the Topic Thumbnails and Created Topic Sort adding to the templates at the same time. Might just be an issue with masonry and grid mode? I’ll see if I can make a suitable adjustment for it in the CSS instead of just hiding it, once i figure out a clean way to detect the theme component usage.
The highlighting for latest and created sounds really weird. Created should only be highlighted when the url has /latest?order=created in it… hmmm…
In blog style, the created date is pulled to the bottom right. I couldn’t find a clean way to get it to be right next to the bump date, so this will have to do. In grid style and masonry style, the created date is only visible when the “Created” filter is selected, and will replace the activity date. I tried to get both activity date and created date to display at the same time, but it made the card feel cramped. In minimal style, the created date is hidden.
Would it be difficult to add a category scope to this? We would love to have it on our announcements section but don’t need it displayed in our general discussion, etc.
Not at all! I’ve just pushed out an update that adds four new settings to help control where the nav bar item and column gets displayed.
Enable nav bar item in home page: Add the “Sort by Created Date” nav bar item in the home page.
Enable column in home page: Add the “Created” column in the home page.
Categories to display nav bar item: List of categories to display in the “Sort by Created Date” nav bar item. Leave empty to display in all categories.
Categories to display created column: List of categories to display the “Created” column. Leave empty to display in all categories.
import { setDefaultHomepage } from "discourse/lib/utilities";
setDefaultHomepage("/latest?order=created");
Adding the option to the Top Menu settings is definitely preferable, but I don’t think there’s a way to do so from a TC, at least from what I last checked. I’ll have to see if something has changed in the interim.
I was able to get around that by doing setDefaultHomepage("latest?order=created&"); But now the problem is, even though all the indicators say so, the actual sorting doesn’t apply.
So I tried the same url using Custom Homepage for Groups and that did work Not sure why that component’s redirect would work differently since I’m pretty sure it using the same method.