In the discussion about tag notifications not working on v2.7.11 for regular users, tomitomas reported that they are not receiving notifications for watched tags, despite the subscription being active. This issue seems to be limited to non-admin profiles, as tomitomas mentioned that admin profiles do not have this issue.
tomitomas also found that their preference settings page is empty and that updating the fields does not save the changes. pfaffman suggested trying safe mode, but tomitomas reported that the issue persists in safe mode.
nathank shared a similar experience with tag notifications not working and found that they are not being applied or appearing in the users’ notifications. nathank also mentioned that this issue is still a problem and pointed to a related thread.
The issue was eventually discussed in a related thread, and according to tomitomas, version 2.8.0 may fix the issue, which will need to be confirmed.
I didn’ t find any post about it, sorry if I missed it and if it’s already handled.
Sorry, as a new user, I have to split my message into several one to send all details
on v2.7.11, (as a regular user - ie non admin) it seems that we are not able to receive notifications about a tag watched (same for the other options too)
If i look at on a tag page : I made a suscription “watched” → the small bell is set on that tag page ==> so I should be notified of all new posts and topics when that tag is used, but I don’t have any notification when a new topic is created
yep, that’s what I did.
but if I ask the question, it’s because that wasn’t clear for me
any user can use
says that anybody can use it, but doesn’t say if it’s applied only for the current user
I think it is, otherwise it might be a security issue. but i prefer to ask confirmation
I’ve noticed something similar, where tag notifications are not working at all. I only discovered it when wondering why nobody was replying to a post and then digging around in the email logs.
They are not appearing in the users’ Notifications–>Tags at all, and are not being applied. This is also the case with safe-mode on.
When interrogating the database, they seem to be correct.
I’ve had to do an ugly workaround with @mentions instead.
Can you reproduce this here on Meta? If not it means it’s already fixed in our default release channel, so you can update to that or wait until it’s dispatched to the slower release channel you are using.