Hi,
Is it possible to have a cache or something for the ‘recent-replies’? It’s looks like its always fetch the infos in every page refresh
Hi,
Is it possible to have a cache or something for the ‘recent-replies’? It’s looks like its always fetch the infos in every page refresh
I have this same issue. It for sure used to be ordered correctly and it doesn’t look like I can use the order parameter for this list.
thanks for confirming, thought maybe my imagination
There was a bug that would only manifest itself in some cases, for example if a single digit date event was added after a multiple digit date event. So in most cases, it was working properly, but sometimes, like in your screenshot, it would show 31 before 3 within the same month.
This should fix it once it is merged: FIX: Correctly order events in upcoming events list by pmusaraj · Pull Request #34526 · discourse/discourse · GitHub
Thanks Penar! what a great job tracking down such an obscure buggy
Later when the dates changed and it worked properly I thought I was losing it ![]()
A little minimal-gamification-leaderboard tip:
I wanted to add a suffix – e.g. YR, MO, QTR – to the title of the sidebar leaderboard to indicate which timeframe it shows (which is based on the default period set in Gamification):

But the sidebar gets that block heading directly from the leaderboard title in Gamification. The full leaderboard accessed from the main menu can show several date ranges, so I didn’t want to put a suffix in the title:
I was able to do this with a bit of custom CSS targeting the leaderboard block in the sidebar:
.leaderboard h3::after {
content: " - QTR";
}
(Of course if I change the default leaderboard period, I’ll have to edit the CSS – but that should be rare.)
What do I need to enter in “Show in routes” to show sidebar on all /tag/ pages?
Also, and even better, how can I get route of any page?
Thank you! Any page, of course.
Yeah haha I need to know which pages you’re thinking of so that I can let you know what to fill in. I think not all pages are supported. Below is a good list:
For example, all categories and all topics.
If it’s not supported, I can easily check by trying - the question is, how do you know that categories page is discovery.categories, or that all tag pages is tag.show? How do I get this route value by myself or at least see full list of routes?
I would use this as a kind of list: discourse/frontend/discourse/app/routes/app-route-map.js at main · discourse/discourse · GitHub. Though I am not convinced this is the type of list you asked for.
It is a little complicated. The reason why it starts mostly with discovery is because the sidebar is inserted in an outlet in the discovery route here in the core app:
Then the following is a check that is done on each page to determine if the blocks should show up:
And these “routes” are ember routes. @Moin is right by looking at that file, so you can glean off things like:
etc. But the examples I quoted above are pretty much the main routes this TC would be useful in.
Thanks, guys. Yeah, it is very non-user friendly, but it’s something I can tinker with ![]()
The theme component is made only to show up in places where there is a list of topics.
So I think the list in the description is actually pretty much all we get.
I usually just log the routes to the console. You could use a simple theme component I personally use for that: Manuel Kostka / Discourse / Helpers / Development · GitLab
How to display the right sidebar on the topic page?
In the admin setting admin → right sidebar blocks → show in routes
just add the route you wish the sidebar to show in ![]()
What is the route for every topic page?
just leave it default blank