发送给已删除用户的电子邮件中显示 Ruby hash 语法

Richie · 2025 年9 月 12 日 07:39

当用户因其第一篇帖子被拒绝而被删除时，他们会收到一封主题为“您的帐户已被删除”的电子邮件。

电子邮件的正文/内容存在一个错误，它似乎在电子邮件的中间部分显示了某种 Ruby 哈希语法：

你好，

这是一封来自 SITE NAME 的自动消息，通知您此电子邮件地址关联的用户帐户已被工作人员删除。

{:off_topic=>“您的帖子被标记为无关主题：社区认为它不适合当前由标题和第一篇帖子定义的该主题。”, :inappropriate=>“您的帖子被标记为不当：社区认为它具有冒犯性、辱骂性、仇恨性言论或违反了我们的社区准则。”, :illegal=>“您的帖子被标记为非法：社区认为它可能违法。”, :spam=>“您的帖子被标记为垃圾邮件：社区认为它是一个广告，性质上过于促销，而不是像预期的那样有用或与主题相关。”, :notify_moderators=>“您的帖子被标记为需要版主注意：社区认为帖子的某些内容需要工作人员手动干预。”, :responder=>{:off_topic=>“帖子被标记为无关主题：社区认为它不适合当前由标题和第一篇帖子定义的该主题。”, :inappropriate=>“帖子被标记为不当：社区认为它具有冒犯性、辱骂性、仇恨性言论或违反了我们的社区准则。”, :spam=>“帖子被标记为垃圾邮件：社区认为它是一个广告，性质上过于促销，而不是像预期的那样有用或与主题相关。”, :notify_moderators=>“帖子被标记为需要版主注意：社区认为帖子的某些内容需要工作人员手动干预。”}}

请查阅我们的社区准则以获取详细信息。

重现步骤：

确保 Discourse 要求批准每个用户的第一个帖子
创建一个新用户
使用新用户创建一个新帖子
使用管理员帐户，选择“删除用户”选项拒绝该帖子
新用户会收到包含上述内容的电子邮件

Richie · 2025 年9 月 12 日 07:41

如果这有帮助的话，这是被拒绝帖子的管理员视图的几张截图：

删除用户之前：

拒绝和删除之后：

selase · 2025 年11 月 18 日 11:45

帖子已拆分为新主题：修复已删除用户邮件处理的暂存用户

selase · 2025 年9 月 12 日 18:24

这看起来是 flag_reason 在此处生成时存在一个 bug：

github.com/discourse/discourse

app/mailers/user_notifications.rb

1aa055cee


      
          def account_deleted(email, reviewable)
            post_action_type_id =
              reviewable.reviewable_scores.first&.reviewable_score_type ||
                PostActionTypeView.new.types[:spam]
            build_email(
              email,
              template: "user_notifications.account_deleted",
              flag_reason: I18n.t("flag_reasons.#{PostActionTypeView.new.types[post_action_type_id]}"),
            )
          end

PostActionTypeView.new.types 不包含 :needs_approval 标志（该标志在上述流程中创建）。因此，翻译键解析为 flag_reasons.（没有后缀），这将返回整个 YAML 部分而不是单个条目。这就是为什么会出现 Ruby 哈希而不是标志原因的原因。

github.com/discourse/discourse

config/locales/server.en.yml

1aa055cee


      
          flag_reasons:
            off_topic: "Your post was flagged as **off-topic**: the community feels it is not a good fit for the topic, as currently defined by the title and the first post."
            inappropriate: "Your post was flagged as **inappropriate**: the community feels it is offensive, abusive, to be hateful conduct or a violation of [our community guidelines](%{base_path}/guidelines)."
            illegal: "Your post was flagged as  **illegal**: the community thinks it might be breaking the law."
            spam: "Your post was flagged as **spam**: the community feels it is an advertisement, something that is overly promotional in nature instead of being useful or relevant to the topic as expected."
            notify_moderators: "Your post was flagged **for moderator attention**: the community feels something about the post requires manual intervention by a staff member."
            responder:
              off_topic: "The post was flagged as **off-topic**: the community feels it is not a good fit for the topic, as currently defined by the title and the first post."
              inappropriate: "The post was flagged as **inappropriate**: the community feels it is offensive, abusive, to be hateful conduct or a violation of [our community guidelines](%{base_path}/guidelines)."
              spam: "The post was flagged as **spam**: the community feels it is an advertisement, something that is overly promotional in nature instead of being useful or relevant to the topic as expected."
              notify_moderators: "The post was flagged **for moderator attention**: the community feels something about the post requires manual intervention by a staff member."

同样，这可能也会影响自定义标志，因为它们的翻译也会丢失。

Moin · 2025 年9 月 12 日 18:43

我敢肯定会的。我五月份就提到了这一点

selase · 2025 年11 月 18 日 11:51

我们已合并对 OP 中问题的修复。我已将与分阶段用户相关的报告移至其自己的主题，以便在等待修复时更容易跟踪。

github.com/discourse/discourse

FIX: Missing/incorrect flag reason in `account_deleted` emails

main ← fix/deleted-user-email

opened 04:43PM - 24 Sep 25 UTC

s3lase

+89 -8

`UserNotifications#account_deleted` builds a localized flag reason from the revi…ewable’s first `reviewable_score` (falling back to `spam` if none is found). Currently, some score types (e.g. `needs_approval`) are not covered. In cases where a "Needs Approval" flag led to an account deletion, the lookup key could end up as `flag_reasons.`, causing the entire `flag_reasons` section to be rendered instead of a single entry. This change adds support for additional score types (like `needs_approval`). If no translation exists (e.g. custom flags), the flag’s description will be used if available, before falling back to the default `spam` reason. More context: https://meta.discourse.org/t/ruby-hash-syntax-being-displayed-in-emails-sent-to-deleted-users/382411

话题		回复	浏览量
User deleted email is sent even when deletion failed Bug review-queue	0	56	2025 年5 月 30 日
Flag reason/s Support	4	510	2022 年11 月 10 日
Can we turn off emails to deleted users and stop contacting our spammers? Support email	11	126	2025 年9 月 17 日
Feedback on the new Review Queue (2019) Announcements new-feature , review-queue	262	17430	2023 年3 月 11 日
Link to guidelines in email about user deletion for private forums UX review-queue	1	76	2025 年7 月 10 日

发送给已删除用户的电子邮件中显示 Ruby hash 语法

相关话题