# פוסטים של משתמשים (תגובות) מופיעים כ"מערכת"
**URL:** https://meta.discourse.org/t/user-posts-comment-replies-showing-up-as-system/273868
**Category:** Bug
**Created:** [3 באוגוסט, 2023, 6:09pm UTC](https://meta.discourse.org/t/user-posts-comment-replies-showing-up-as-system/273868 "2023-08-03T18:09:57Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@meltingmettle\_gh](https://meta.discourse.org/u/meltingmettle_gh)
#### Post date: [3 באוגוסט, 2023, 6:09pm UTC](https://meta.discourse.org/t/user-posts-comment-replies-showing-up-as-system/273868/1 "2023-08-03T18:09:57Z")
Hi all
We just started this new glitch where replies to a post are shown as being from “System” user. (The post is attributed to the correct user, but the reply sometimes is not). I checked with the poster and he was not posting in anonymous mode.
We were running [v3.1.0beta4](https://github.com/discourse/discourse/releases/tag/v3.1.0.beta4) (which did not include any of these changes) up till 10am today, so the issue is probably in that tag.
Possibly related to this bump:
> [@Discourse 3.1 is here!](https://meta.discourse.org/t/discourse-3-1-is-here/273457):
>
> Today, we are pleased to announce Discourse 3.1! Filled with features for members and admins alike, this version includes chat threads, a more customizable sidebar, improved search and numerous other improvements. This release is accompanied by the launch of our Discourse AI plugin, embracing the power of emerging large language models (LLMs) to make your community easier to use and moderate. This is a companion discussion topic for the original entry at [https://blog.discourse.org/2023/08/disc…](https://blog.discourse.org/2023/08/discourse-3-1-is-here)
Or this recent change:
> [@Pull Request: SiteSetting to anonymous users to "like" posts](https://meta.discourse.org/t/pull-request-sitesetting-to-anonymous-users-to-like-posts/268660):
>
> Hi all, I’ve opened a PR to allow anonymous users to “like” posts. It’s a SiteSetting so admins have the option of enabling or disabling the feature. Could I please get a code review? grinning_face_with_smiling_eyes[https://github.com/discourse/discourse/pull/22131](https://github.com/discourse/discourse/pull/22131) Context: I’m part of a 501(c)3 discourse where our accounts are registered under our actual names. We encourage anonymous discussion, as some people want to share about personal experiences and sensitive topics. (mental healt…
Screenshots:
Another screenshot:
The post which they are replying to is attributed to the correct user.
---
### Author:  [@nat](https://meta.discourse.org/u/nat)
#### Post date: [4 באוגוסט, 2023, 3:50am UTC](https://meta.discourse.org/t/user-posts-comment-replies-showing-up-as-system/273868/2 "2023-08-04T03:50:22Z")
> [@meltingmettle\_gh](#):
>
> We were running [v3.1.0beta4](https://github.com/discourse/discourse/releases/tag/v3.1.0.beta4) (which did not include any of these changes) up till 10am today
Can you confirm if you were on `v3.1.0.beta4` when you see this bug, or are you seeing this after upgrading? We’ve not received any reports of this bug, so it is a bit peculiar.
Also I’m noticing your site potentially has some mods (theme/plugins), could you try [safe mode](https://meta.discourse.org/t/53504?silent=true) and see if this is happening?
---
### Author:  [@andrewstucki](https://meta.discourse.org/u/andrewstucki)
#### Post date: [4 באוגוסט, 2023, 3:35pm UTC](https://meta.discourse.org/t/user-posts-comment-replies-showing-up-as-system/273868/3 "2023-08-04T15:35:01Z")
Hi Natalie,
I can give you a bit more info, this was during the upgrade process, but prior to the upgrade actually finishing. We have a deployment upgrade process that, in part, sets a global notice banner that the site will go down shortly and leverages the API, authenticating as the system user to do so. The job actually failed due to an out-of-date part of the build pipeline and left the banner up for ~10 hours before it was fixed and the upgrade finished. All of the comments that appear to be coming from the “system” user appear to have happened roughly around the time that this banner was set and up (yes, this seems quite odd). _After_ the upgrade the problem doesn’t appear to have resurfaced. So, yes, the bug appeared to be surfaced while we were on `v3.1.0.beta4`.
Perusing through the code, the only thing I noticed involving users and notices is an after save hook on users that appears to be potentially clearing a global notice. So this could very well be a theme or plugin causing the issue, but either way my money is that it has something to do with the API request that was authenticating as the system user given the timing and the associated user.