discourse-solved/spec
Osama Sayegh 77c07edf82
FIX: Don't allow TL4 users to unconditionally accept solutions (#305)
A while ago the `accept_all_solutions_allowed_groups` setting was introduced to replace the `accept_all_solutions_trust_level` setting and to make the plugin more flexible by allowing admins to choose groups that are allowed to accept solutions instead of trust levels.

The new group-based setting includes the TL4 group by default. However, removing the TL4 group from the setting doesn't actually remove TL4 users permission to accept solution.

The reason for this bug is that the `can_accept_answer?` guardian method calls `can_perform_action_available_to_group_moderators?` which always allows TL4 users to perform category moderator actions:

56524f4bdf/lib/guardian/topic_guardian.rb (L342-L348)

This commit fixes the bug by checking if the user is a moderator on the topic's category (by calling the `is_category_group_moderator?` guardian method) instead of checking if the user can perform category moderator actions. In our case, `is_category_group_moderator?` is equivalent to `can_perform_action_available_to_group_moderators?` except for the TL4 check which is what we need.

Internal topic: t/134675.
2024-08-09 14:59:28 +03:00
..
components DEV: Fix new Rubocop offenses 2024-03-06 10:25:26 +01:00
fabricators FIX: granular webhooks (#248) 2023-10-09 03:26:29 +00:00
integration FIX: when deleting users with solved posts (#297) 2024-06-17 12:41:13 +02:00
lib FIX: Don't allow TL4 users to unconditionally accept solutions (#305) 2024-08-09 14:59:28 +03:00
models Revert "FIX: Use Guardian.basic_user instead of new (anon) (#270)" (#271) 2023-12-06 16:26:40 +10:00
requests DEV: Update linting (#275) 2024-01-16 17:50:43 +01:00
serializers Revert "FIX: Use Guardian.basic_user instead of new (anon) (#270)" (#271) 2023-12-06 16:26:40 +10:00