fefrei
(Felix Freiberger)
June 2, 2016, 4:01pm
1
This issue is back from the dead:
Summary:
Attempted to set notification type for “moderators” group, and was unable to change it from normal
Steps to reproduce:
Open messages view
Switch to group message page
Click notification type switcher, and select any type other than normal
Expected Results:
Notification type switches
Actual Results:
Error appears in Chrome dev tools
Attachments:
Error in Chrome:
Uncaught TypeError: Cannot read property 'setNotification' of undefined
t.default.r.extend.clicked @ _applicatio…
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 Like
fefrei
(Felix Freiberger)
June 17, 2016, 4:51pm
2
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 ?
techAPJ
(Arpit Jalan)
June 17, 2016, 7:15pm
4
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?
fefrei
(Felix Freiberger)
June 17, 2016, 7:20pm
5
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:
login required
SSO is enabled
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 Like
fefrei
(Felix Freiberger)
June 22, 2016, 11:31am
6
Could you maybe try that again with a new group? I think that’s the most interesting difference between your experiment and my experience…
techAPJ
(Arpit Jalan)
June 22, 2016, 12:30pm
7
Just tried locally, still not able to repro this issue
2 Likes
fefrei
(Felix Freiberger)
June 22, 2016, 3:23pm
8
Strange. I tried to reproduce it again, and failed – so it seems to be sporadic.
1 Like
fefrei
(Felix Freiberger)
September 5, 2016, 3:53pm
9
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 Likes
fefrei
(Felix Freiberger)
March 14, 2017, 4:12pm
10
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.
sam
(Sam Saffron)
March 14, 2017, 5:30pm
11
fefrei:
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?
fefrei
(Felix Freiberger)
April 20, 2017, 7:14am
14
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 Likes
sam
(Sam Saffron)
July 21, 2022, 7:00am
15
Is this still the case now? I am going to assume not and close, but flag to reopen if it still happens.
1 Like