This refactor makes for easier testing and makes things
more organised, the guardian extensions had no testing
whatsoever and I need some to make the TL -> group change.
Many consumers of Discourse solved may want solved topics to show up more
prominently in search. New setting `prioritize_solved_topics_in_search` (default off) allows
bumping these topics to the top.
Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com>
This is necessary, because seeding badges with a translated name will result in duplicate badges whenever the default locale changes. The static name solves this.
Moreover, it's not necessary to set the description during seeding. The serializer will localize the names and descriptions at runtime.
The DB migration tries to rename the existing badges by looking them up by their translated time.
`allow_accepted_answer` should be `allow_accepted_answers` (with an `s` at the end) in the `TopicAnswerMixin`.
The `enable_solved_tags` setting description seemed to be using the description intended for `allow_solved_on_all_topics`. Both descriptions have been updated.
This PR adds a site setting called `enable_solved_tags`. Solved will be enabled for topics containing these tags, just like we do for specific categories.
* Make it possible to disallow topic starters to accept a solution
* Make adding QAPage schema markup optional
* Address @eviltrout's comments
Co-authored-by: Richard <richard@communiteq.com>
* FEATURE: Add helpdesk and tech support badges
When plugin is installed, we should create helpdesk and tech support
badges.
Both badges should be disabled by default
Martin Brennan
Sam
Gerhard Schlager
Joffrey JAFFEUX
tshenry
Roman Rizzi
Bianca Nenciu
Osama Sayegh
communiteq
Arpit Jalan
Vinoth Kannan
Simon Cossar
Krzysztof Kotlarek
Guo Xiang Tan
David Taylor
Régis Hanol