2015-05-19 02:26:22 -04:00
|
|
|
|
en:
|
|
|
|
|
|
js:
|
2017-09-15 13:55:08 -04:00
|
|
|
|
notifications:
|
|
|
|
|
|
alt:
|
|
|
|
|
|
solved:
|
|
|
|
|
|
accepted_notification: "accepted"
|
2021-06-22 14:18:23 -04:00
|
|
|
|
solutions: "Solutions"
|
2017-09-15 13:55:08 -04:00
|
|
|
|
|
2015-06-15 00:24:49 -04:00
|
|
|
|
solved:
|
2016-12-06 01:28:15 -05:00
|
|
|
|
title: "Solved"
|
2015-07-20 18:56:26 -04:00
|
|
|
|
allow_accepted_answers: "Allow topic owner and staff to mark a reply as the solution"
|
2023-04-19 10:14:33 -04:00
|
|
|
|
solved_topics_auto_close_hours: "Auto close topic (n) hours after the last reply once the topic has been marked as solved."
|
2018-01-24 13:37:47 -05:00
|
|
|
|
accept_answer: "Select if this reply solves the problem"
|
2019-07-24 11:01:47 -04:00
|
|
|
|
accepted_description: "This is the accepted solution to this topic"
|
2017-02-27 12:42:58 -05:00
|
|
|
|
has_no_accepted_answer: "This topic has no solution"
|
2018-01-24 13:37:47 -05:00
|
|
|
|
unaccept_answer: "Unselect if this reply no longer solves the problem"
|
2015-07-20 18:56:26 -04:00
|
|
|
|
accepted_answer: "Solution"
|
2015-07-14 02:18:56 -04:00
|
|
|
|
solution: "Solution"
|
2016-12-06 01:28:15 -05:00
|
|
|
|
solution_summary:
|
2018-11-12 13:26:28 -05:00
|
|
|
|
one: "solution"
|
|
|
|
|
|
other: "solutions"
|
2020-06-02 13:15:45 -04:00
|
|
|
|
accepted_html: "%{icon} Solved <span class='by'>by <a href data-user-card='%{username_lower}'>%{username}</a></span> in <a href='%{post_path}' class='back'>post #%{post_number}</a>"
|
|
|
|
|
|
accepted_notification: "<p><span>%{username}</span> %{description}</p>"
|
2019-03-13 15:11:07 -04:00
|
|
|
|
topic_status_filter:
|
|
|
|
|
|
all: "all"
|
|
|
|
|
|
solved: "solved"
|
|
|
|
|
|
unsolved: "unsolved"
|
2021-09-28 11:22:08 -04:00
|
|
|
|
no_solved_topics_title: "You haven’t solved any topics yet"
|
2022-08-18 08:51:28 -04:00
|
|
|
|
no_solved_topics_title_others: "%{username} has not solved any topics yet"
|
2021-09-28 11:22:08 -04:00
|
|
|
|
no_solved_topics_body: "When you provide a helpful reply to a topic, your reply might be selected as the solution by the topic owner or staff."
|
2019-03-13 13:10:54 -04:00
|
|
|
|
|
2021-12-15 10:16:41 -05:00
|
|
|
|
no_answer:
|
|
|
|
|
|
title: Has your question been answered?
|
|
|
|
|
|
description: "Highlight the answer and help others by using the solution button below the correct reply."
|
2023-02-15 08:30:33 -05:00
|
|
|
|
notification:
|
|
|
|
|
|
title: "your post was marked as solution"
|
2021-12-15 10:16:41 -05:00
|
|
|
|
|
2019-03-13 13:10:54 -04:00
|
|
|
|
topic_statuses:
|
|
|
|
|
|
solved:
|
|
|
|
|
|
help: "This topic has a solution"
|
2020-03-05 22:27:38 -05:00
|
|
|
|
|
|
|
|
|
|
search:
|
|
|
|
|
|
advanced:
|
|
|
|
|
|
statuses:
|
|
|
|
|
|
solved: "are solved"
|
2020-09-11 06:15:34 -04:00
|
|
|
|
unsolved: "are unsolved"
|
FEATURE: Publish WebHook event when solving/unsolving (#85)
* FEATURE: Publish WebHook event when solving/unsolving
This feature will publish a post edit webhook event whenever a solution
is accepted or unaccepted.
I went ahead and used the existing post-edit webhook because all the
post custom fields for the solved plugin are already included in the
post-edit serializer.
* Create Solved Event Webhook
This commit adds a solved event webhook that will only trigger when an
answer has been marked as accepted or unaccepted.
It uses 100 as the webhook ID. This way any new webhooks in core can
keep using lower numbers like 11, 12, 13, but plugins can use 101, 102,
etc.
* Removed functionality that was added to core
This [PR][1] to discourse core adds what what removed in this commit.
It is better to have this logic in core so that it is discoverable and
future webhooks won't end up accidentally using the same ID.
[1]: https://github.com/discourse/discourse/pull/9110
* UX: Add "solved" status filter in advanced search page.
And rename `in:solved` to `status:solved`.
* FEATURE: Publish WebHook event when solving/unsolving
This feature will publish a post edit webhook event whenever a solution
is accepted or unaccepted.
I went ahead and used the existing post-edit webhook because all the
post custom fields for the solved plugin are already included in the
post-edit serializer.
* Create Solved Event Webhook
This commit adds a solved event webhook that will only trigger when an
answer has been marked as accepted or unaccepted.
It uses 100 as the webhook ID. This way any new webhooks in core can
keep using lower numbers like 11, 12, 13, but plugins can use 101, 102,
etc.
* Removed functionality that was added to core
This [PR][1] to discourse core adds what what removed in this commit.
It is better to have this logic in core so that it is discoverable and
future webhooks won't end up accidentally using the same ID.
[1]: https://github.com/discourse/discourse/pull/9110
Co-authored-by: Vinoth Kannan <vinothkannan@vinkas.com>
2020-03-06 13:28:29 -05:00
|
|
|
|
|
|
|
|
|
|
admin:
|
|
|
|
|
|
web_hooks:
|
|
|
|
|
|
solved_event:
|
2023-10-08 23:26:29 -04:00
|
|
|
|
group_name: "Solved Event"
|
|
|
|
|
|
accepted_solution: "When an user marks a post as the accepted answer"
|
|
|
|
|
|
unaccepted_solution: "When an user marks a post as the unaccepted answer"
|
2023-02-23 17:00:14 -05:00
|
|
|
|
api:
|
|
|
|
|
|
scopes:
|
|
|
|
|
|
descriptions:
|
|
|
|
|
|
solved:
|
|
|
|
|
|
answer: Accept/Unaccept a solution.
|
2021-11-12 10:00:48 -05:00
|
|
|
|
|
|
|
|
|
|
discourse_automation:
|
|
|
|
|
|
triggerables:
|
|
|
|
|
|
first_accepted_solution:
|
|
|
|
|
|
max_trust_level:
|
|
|
|
|
|
tl1: < TL1
|
|
|
|
|
|
tl2: < TL2
|
|
|
|
|
|
tl3: < TL3
|
|
|
|
|
|
tl4: < TL4
|
|
|
|
|
|
any: Any
|
|
|
|
|
|
fields:
|
|
|
|
|
|
maximum_trust_level:
|
|
|
|
|
|
label: Trust Level
|
|
|
|
|
|
description: Users under this Trust Level will trigger this automation
|
