Unable to set notification type for group message inbox, again

סיכום מבוסס בינה מלאכותית

The issue of being unable to set notification types for group message inboxes has resurfaced in Discourse 1.6.0.beta7, with users encountering the error Uncaught TypeError: Cannot read property 'setNotification' of undefined fefrei. Although reloading sometimes temporarily resolves it, the problem persists sporadically, especially for new groups with SSO enabled and login required fefrei. Attempts to reproduce the bug by techAPJ and others on Meta and Try failed, even with new groups techAPJ. fefrei later reproduced it on a fresh Discourse instance by creating a group, enabling incoming mail, and attempting to set notification levels from the inbox notification. Interestingly, the bug appears only when the notification level is still at default and vanishes after the first successful update fefrei. Additionally, fefrei reported another issue: inability to persistently update tracking states for other users, though changes to one’s own state work. sam requested a separate topic for the latter issue, and later sam closed this topic assuming the bug was resolved, inviting reopening if it recurs.

This issue is back from the dead:

Now it’s happening in Discourse 1.6.0.beta7. The reproduction steps are still the same, the error message is still Uncaught TypeError: Cannot read property 'setNotification' of undefined.


Somehow, after reloading the page, I ended up tracking the inbox, and could switch to watching…

לייק 1

This is still an issue; but this time, I could not get the state to switch to tracking.

Here’s a screenshot of the inspector:

Can we repro this @techapj?

Unable to repro this issue here on meta (for team & moderators group) or on try (admins group).

Just curious, did reloading the page solved the issue?

Every time I tried to switch the notification mode, a new copy of the error was thrown on the console. Reloading didn’t fix it on the first try.

After trying a few different notification state and navigating to the archive and back, after reloading, I was tracking the inbox.

It’s interesting that you cannot reproduce it, while I could reproduce it multiple times. The only details that are interesting about my case:

  1. login required
  2. SSO is enabled
  3. I was always testing it for a fresh group, after sending it a test email to make the inbox show up.

Is there something I can do to help you debug this?

לייק 1

Could you maybe try that again with a new group? I think that’s the most interesting difference between your experiment and my experience…

Just tried locally, still not able to repro this issue :confused:

2 לייקים

Strange. I tried to reproduce it again, and failed – so it seems to be sporadic.

לייק 1

I just set up a fresh Discourse instance, and hit this again. Here’s what I did last:

  • create a new group
  • set up incoming mail for the group
  • send a test mail to the group
  • open the notification that there is a message in my inbox
  • try to set the notification level from there

4 לייקים

I can no longer repro this.

However, I can no longer update the tracking state for someone else (by visiting their messages page). The change appears to work, and there are no errors in the console, but the change reverts when the page reloads. Instead, I changed my own tracking state for this group.

Can you do a separate topic on this issue?

I’ve just run into this again:

So it looks like the bug is back, or was never really gone.

An observation I made: This only occurs if the level is still at the default. It never happens once you successfully updated a group’s notification level once.

Is there anything I can do to help you debug this?

2 לייקים

Is this still the case now? I am going to assume not and close, but flag to reopen if it still happens.

לייק 1