# Editing category settings causes category to be muted for the current user
**URL:** https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972
**Category:** Bug
**Created:** [9월 13, 2017, 3:01오후 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972 "2017-09-13T15:01:47Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [9월 13, 2017, 3:01오후 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972/1 "2017-09-13T15:01:47Z")
I think this is quite a serious bug:
1. Go to a category
2. Look at the buttons in the top right, notice I have “normal” notification level
3. Click edit
4. Don’t change any settings
5. Click “save”
6. Page refreshes, observe notification level has changed to “Muted”
I am running the absolute latest tests-passed (updated 10 mins ago), and can replicate this on every category on my forum.
Looking at my dev tools, it looks like a POST is being sent to the notifications endpoint immediately after clicking save on the category settings.:
(ignore poll/results items, they’re messagebus/mini-profiler respectively)
I’ve noticed a few support requests on meta that are probably caused by this. For example, [this topic](https://meta.discourse.org/t/posts-from-a-particular-category-missing-from-homepage-just-for-the-admin-user/69734).
I am also seeing some random topics change to a muted state, but can’t reproduce this consistently. The root cause might be the same.
The extra POST request makes me think this is a client-side issue rather than server-side. @j.jaffeux could this be related to the select-box changes for notification levels?
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [9월 13, 2017, 3:03오후 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972/2 "2017-09-13T15:03:35Z")
Well this would be very unlikely caused by the component… but nothing astonishes me in programming. Let me try to remove the component from the page to see if I can still reproduce.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [9월 13, 2017, 3:08오후 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972/3 "2017-09-13T15:08:29Z")
Probably related to the component, no idea why atm, I will investigate and push a fix, thx.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [9월 13, 2017, 4:03오후 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972/4 "2017-09-13T16:03:05Z")
I have the fix for categories, I’m looking at topics, and I have some chicken and egg problem, but will find a solution.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [9월 13, 2017, 4:45오후 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972/5 "2017-09-13T16:45:15Z")
Should be fixed by:
[https://github.com/discourse/discourse/commit/7a4ddc2bb1bc2e353c67ce3846229b551d0603de](https://github.com/discourse/discourse/commit/7a4ddc2bb1bc2e353c67ce3846229b551d0603de)
Will track it once deployed.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [9월 13, 2017, 4:49오후 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972/6 "2017-09-13T16:49:58Z")
Wow this is a very bad regression. You’ll need to track this closely and monitor customer support for sites affected ☹
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 18, 2018, 2:28오전 UTC](https://meta.discourse.org/t/editing-category-settings-causes-category-to-be-muted-for-the-current-user/69972/7 "2018-05-18T02:28:07Z")