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.)