# “仅首帖”筛选器是否考虑事后编辑或合并到分类的情况？ **URL:** \ **Category:** Support\ **Tags:** chat-integration\ **Created:** [2019年六月2日 19:26 UTC](https://meta.discourse.org/t/first-post-only-filter-to-take-into-account-edits-merge-into-category-after-the-fact/119325 "2019-06-02T19:26:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Hooksmith](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hooksmith/32/142826_2.png) [@Hooksmith](https://meta.discourse.org/u/Hooksmith)\ **Post date:** [2019年六月2日 19:26 UTC](https://meta.discourse.org/t/first-post-only-filter-to-take-into-account-edits-merge-into-category-after-the-fact/119325/1 "2019-06-02T19:26:20Z")
Hey all, On our self-hosted Discourse instance with the chat-integration plugin, we have it set up so that new threads in a certain category trigger notifications in our company Slack in a certain channel via “First post only” filter. It sometimes occurs that people post in the wrong place and then edit it into the category after the fact, or sometimes we manually merge some responses into a new thread in that category. Sometimes this is done by staff members, but more often than not by our community members and then we’d still like to see a notification of the thread. Under these circumstances however, we do not see any notifications in Slack. It seems to be that the notifications only get triggered when people actually post it straight in that category, and not from later edits or merge actions. Is this something that could be implemented (perhaps as option), or is this intentionally designed this way? Thanks, Thomas ---
**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\ **Post date:** [2020年一月24日 07:53 UTC](https://meta.discourse.org/t/first-post-only-filter-to-take-into-account-edits-merge-into-category-after-the-fact/119325/2 "2020-01-24T07:53:31Z")
你曾找到过解决这个问题的变通方法吗？ ---
**Author:** ![Hooksmith](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hooksmith/32/142826_2.png) [@Hooksmith](https://meta.discourse.org/u/Hooksmith)\ **Post date:** [2020年一月31日 16:47 UTC](https://meta.discourse.org/t/first-post-only-filter-to-take-into-account-edits-merge-into-category-after-the-fact/119325/3 "2020-01-31T16:47:46Z")
很遗憾，我们并没有这样做。相反，我们已告知社区版主，将分类错误的帖子关闭，并引导用户将其发布到正确的分类中，而不是直接编辑帖子类别。我们的版主通常能在帖子发布后很快发现分类错误的情况，因此目前这种方法对我们来说“可行”，尽管并不太方便。 ---
**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\ **Post date:** [2020年一月31日 18:43 UTC](https://meta.discourse.org/t/first-post-only-filter-to-take-into-account-edits-merge-into-category-after-the-fact/119325/4 "2020-01-31T18:43:21Z")
> [@Hooksmith](#): > > 将分类错误的帖子关闭，并引导用户前往他们应该发布的正确分类，而不是直接将其编辑到该分类中。 这确实令人遗憾。不过，最近有一项变更： > [@Publication of Timed Topics don't trigger new topic notifications](https://meta.discourse.org/t/publication-of-timed-topics-dont-trigger-new-topic-notifications/139335/14?u=downey): > > First of all, thank you for report the issue. I think I fixed that issue in this commit: [FIX: correct notification when tag or category is added (#8801) · discourse/discourse@20e7fb1 · GitHub](https://github.com/discourse/discourse/commit/20e7fb1c958790fa2dafc80bf6fe76b0556a2b92) Basically, I improved a little bit the logic around notification If the user has already seen the post, the type of notification should be edited. The case for that is when for example OP will add category or tag which is watched by another user. However, when the user hasn’t yet seen the post, the type… 你可以再测试一下…… ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2023年十二月22日 13:19 UTC](https://meta.discourse.org/t/first-post-only-filter-to-take-into-account-edits-merge-into-category-after-the-fact/119325/5 "2023-12-22T13:19:48Z")