You can set the badge’s name in the plugin’s settings:
Also, see: https://meta.discourse.org/t/discourse-yearly-review/105713#features-3
3 Likes
Thanks. Just to confirm - I can choose for example ‘anniversary’ and it’ll show 15 people who received it?
2 Likes
Yes, the users who received the badge will be shown in the topic.
5 Likes
Thank you I missed it
1 Like
This plugin option doesn’t provide any context.
Add user-identifying stats to the first post of the review topic
What kind of user-identifying stats are we exactly talking about? Usernames?
1 Like
The stats are:
Have a look at 2021: The Year in Review to see the review topic that was generated on Meta for 2021.
2 Likes
I know what it could generate, I just wonder what kind of influence that toggle has. When disabled, the plugin will not work at all? What would be the difference exactly?
1 Like
With that off, you will just see stats highlighting the top topics in the top categories. Users will still be associated with those, of course, but you won’t get statistics and totals like number of hours read, and so on.
3 Likes
Why the result doesn’t follow my language setting even if the plugin translation is done? Do I need some extra settings?
1 Like
I’m not sure. I am assuming you published the topic by running Jobs::YearlyReview.new.execute(force: true). If that is correct, it is possible that translations are not getting loaded when the topic is published by running that command from the console. I would expect the language to be correctly set if the topic is published in the normal way, by waiting until January 1 for the topic to be automatically published.
1 Like
Great plugin, very easy to use!
Just one comment and a question.
The “Featured Badge” is a bit vague
My initial understanding after reading this was that this badge would be awarded if you were featured in the Yearly Review. But in actuality it lists users who received that badge in the review. Maybe this could be clarified in the plugin settings.
Either way I ended up creating a badge and bulk awarding it to the featured users anyway 
The question I have is what “popular” means in this context (ie. How is it calculated? )
2 Likes
It ranks topics based on their yearly_score. That is the value that is used for creating Discourse’s Top topic lists. For example: https://meta.discourse.org/c/community/65/l/top
2 Likes
Thanks! I disabled the option and a more privacy friendly overview is now indeed shown. My forum isn’t that active, so the review is quite short. But I like it.
2 Likes
Hmm, on one instance Year in Review topics are generated but on the second Discourse instance still not. Do I need to wait for more?
1 Like
I don’t know it’s currently 11:55AM for me on the 1st of January 2023 and my 2022 recap has not been generated yet, I’m just going to wait and if it’s not here by around 17:00 I will manually generate it.
1 Like
I added this to the wiki when I discovered it tricky to edit the automatically generated post:
1 Like
This is very cosmetic one and I’m just curious, but
- is
Jobs::YearlyReviewreally timed to run twice every day - is time counted from last try
The time was 9:44 AM and was done 14 hours earlier. Next try would be 10 hours later meaning something like 7:44 PM. I expected quite soon after midnight and once a year as cron would work.
2 Likes
Mine just ran and posted now!
1 Like
Mine did it too after triggering job.
1 Like
The job is scheduled to run once every 24 hours for the month of January: discourse-yearly-review/yearly_review.rb at main · discourse/discourse-yearly-review · GitHub. If a topic is found on the site that has a title that matches the review topic’s title, the job will not be re-run. That means that only 1 review topic will be generated, unless you edit the title of the review topic after it is created.
4 Likes