# Notification Bug due to Babble plugin

**URL:** https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706
**Category:** Support
**Created:** [April 30, 2021, 2:16pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706 "2021-04-30T14:16:05Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![hawks](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hawks/32/198521_2.png) [@hawks](https://meta.discourse.org/u/hawks)
#### Post date: [April 30, 2021, 2:16pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/1 "2021-04-30T14:16:05Z")

</div>

Hi guys,

I seem to be having a strange bug where I and all my staff are getting system notifications or notifications of messages that we are not included in. This could be system messages to users or private messages from one user to another! not sure why we are getting these additional notification but this seems to be and issue after the latest update (I hadn’t updated since about 2 weeks prior).

Another instance of when this is an issue is I have enabled notifications for all users when an announcement goes out under the announcement category. Just now an announcement went out and I seemed to get a notification for every single user this notification was sent too!! (The list is way longer than the screenshot below).

 ![image](https://global.discourse-cdn.com/meta/original/3X/5/e/5e462d8731bcb2949f28d79fa7374f9bbf9fb857.png)

Is this a known bug, or even a bug at all? is this maybe something I have done wrong in my settings?

A few more screenshots of examples below of notifications me and my team are receiving but are not related to us

 ![image](https://global.discourse-cdn.com/meta/original/3X/8/2/8262975f28daed34e0ea478f63f8ef6eb5b9073d.png)

![image](https://global.discourse-cdn.com/meta/original/3X/7/6/76c8097a6801ff50655a364877a49b598ea2f816.png)

If there is any more information or logs you may require for this just let me know.

---

<div class="post-metadata">

### Author: ![pawelorzech](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pawelorzech/32/251878_2.png) [@pawelorzech](https://meta.discourse.org/u/pawelorzech)
#### Post date: [April 30, 2021, 2:18pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/2 "2021-04-30T14:18:44Z")

</div>

Same issue here. Everyone is getting the same notifications!

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [April 30, 2021, 2:19pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/3 "2021-04-30T14:19:12Z")

</div>

Do you use the babble plugin?

> [@Everyone receives all notifications (even PMs) due to Babble plugin](https://meta.discourse.org/t/everyone-receives-all-notifications-even-pms/188496):
>
> Hello all! Last night after upgrading to 2.7.0beta7 ([7568c7a101](https://github.com/discourse/discourse/commits/7568c7a101f8b371f7cbd6018450bf3e2cd72b59)) from test-passed, we have encountered an situation where everyone registered on our forum will receive all notifications on every like/reply/comment. The notifications can’t be dismissed from /u/username/notifications/. This also includes PMs between users (which is a bit problematic, as you can imagine). Luckily they can’t read PMs that aren’t theirs, but they still can see who messaged who with what title. Any ideas?

---

<div class="post-metadata">

### Author: ![pawelorzech](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pawelorzech/32/251878_2.png) [@pawelorzech](https://meta.discourse.org/u/pawelorzech)
#### Post date: [April 30, 2021, 2:20pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/4 "2021-04-30T14:20:21Z")

</div>

I do but it’s turned off

---

<div class="post-metadata">

### Author: ![hawks](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hawks/32/198521_2.png) [@hawks](https://meta.discourse.org/u/hawks)
#### Post date: [April 30, 2021, 2:21pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/5 "2021-04-30T14:21:54Z")

</div>

Same, I use it but it is turned off. I can remove it from the config file and rebuild the forum when the traffic dies down to see if that helps?

---

<div class="post-metadata">

### Author: ![pawelorzech](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pawelorzech/32/251878_2.png) [@pawelorzech](https://meta.discourse.org/u/pawelorzech)
#### Post date: [April 30, 2021, 2:47pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/6 "2021-04-30T14:47:55Z")

</div>

Deleted Babble and it seems fine now

---

<div class="post-metadata">

### Author: ![hawks](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hawks/32/198521_2.png) [@hawks](https://meta.discourse.org/u/hawks)
#### Post date: [April 30, 2021, 3:19pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/7 "2021-04-30T15:19:40Z")

</div>

I just did the same and it fixed it for me!!

---

<div class="post-metadata">

### Author: ![REALITY](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/reality/32/199798_2.png) [@REALITY](https://meta.discourse.org/u/REALITY)
#### Post date: [April 30, 2021, 3:32pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/8 "2021-04-30T15:32:55Z")

</div>

Yup same here…though now we don’t have Babble 🤣 🤔

---

<div class="post-metadata">

### Author: ![Mark\_Schmucker](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mark_schmucker/32/124810_2.png) [@Mark\_Schmucker](https://meta.discourse.org/u/Mark_Schmucker)
#### Post date: [May 1, 2021, 12:15pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/9 "2021-05-01T12:15:10Z")

</div>

> [@REALITY](#):
>
> though now we don’t have Babble 🤣 🤔

And your groups page (/g) is broken. If you decide not to re-install babble, you will need to clean up the groups with:

> **[Pavilion](https://pavilion.tech/)**
>
> Pavilion is the leading Discourse consultancy.

---

<div class="post-metadata">

### Author: ![REALITY](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/reality/32/199798_2.png) [@REALITY](https://meta.discourse.org/u/REALITY)
#### Post date: [May 1, 2021, 12:20pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/10 "2021-05-01T12:20:33Z")

</div>

Our Group page is working fine, though thank you for the link i’ll bookmark it if any problems arise.

---

<div class="post-metadata">

### Author: ![slambert](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/slambert/32/110945_2.png) [@slambert](https://meta.discourse.org/u/slambert)
#### Post date: [May 2, 2021, 4:36pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/11 "2021-05-02T16:36:50Z")

</div>

Reported this on the Pavilion site as a bug report for Babble:

> **[Pavilion](https://pavilion.tech/)**
>
> Pavilion is the leading Discourse consultancy.

---

<div class="post-metadata">

### Author: ![REALITY](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/reality/32/199798_2.png) [@REALITY](https://meta.discourse.org/u/REALITY)
#### Post date: [May 21, 2021, 3:15pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/12 "2021-05-21T15:15:11Z")

</div>

Our full Babble shout-box conversation has turned up as a topic on our main page, it seems only Admin can access it though.

It is formatted as any other topic on the forum would be.

Is this normal?

---

<div class="post-metadata">

### 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: [June 20, 2021, 3:15pm UTC](https://meta.discourse.org/t/notification-bug-due-to-babble-plugin/188706/13 "2021-06-20T15:15:12Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
