Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
The notifications bug is known and we're working on a fix. (It has to be made in one repo, propagated to another via npm, and then of course deployed. I think we're waiting for the npm step at th...
Answer
#2: Post edited
by
Monica Cellio
·
2023-01-31T04:03:04Z (almost 2 years ago)
- The notifications bug is [known](https://meta.codidact.com/posts/287466) and we're working on a fix. (It has to be made in one repo, propagated to another via `npm`, and then of course deployed. I think we're waiting for the `npm` step at the moment.) The bug happens if you click directly on the number or text, but if you click in the whitespace around them, it works. It wasn't always broken; some other recent change indirectly caused the problem.
You can see all of your notifications on [this page](https://meta.codidact.com/users/me/notifications). We're in the process of adding that as a tab on the profile page for improved visibility, and also moving the link in the notifications drop-down to the top near "mark all as read".
- The notifications bug is [known](https://meta.codidact.com/posts/287466) and we're working on a fix. (It has to be made in one repo, propagated to another via `npm`, and then of course deployed. I think we're waiting for the `npm` step at the moment.) The bug happens if you click directly on the number or text, but if you click in the whitespace around them, it works. It wasn't always broken; some other recent change indirectly caused the problem.
- You can see all of your notifications on [this page](https://meta.codidact.com/users/me/notifications). <s>We're in the process of adding that as a tab on the profile page for improved visibility, and also moving the link in the notifications drop-down to the top near "mark all as read".</s>
- **Update 2023-01-30:** that last part is now done. There's a new tab on your profile page for your notifications. This is a global list, not per-community; you'll see the same items on all communities. We (by which I mean Moshi who did the actual work) also moved the "see all notifications" link on the inbox drop-down to the top, where it's more likely to be seen.
#1: Initial revision
by
Monica Cellio
·
2023-01-03T15:35:10Z (almost 2 years ago)
The notifications bug is [known](https://meta.codidact.com/posts/287466) and we're working on a fix. (It has to be made in one repo, propagated to another via `npm`, and then of course deployed. I think we're waiting for the `npm` step at the moment.) The bug happens if you click directly on the number or text, but if you click in the whitespace around them, it works. It wasn't always broken; some other recent change indirectly caused the problem. You can see all of your notifications on [this page](https://meta.codidact.com/users/me/notifications). We're in the process of adding that as a tab on the profile page for improved visibility, and also moving the link in the notifications drop-down to the top near "mark all as read".