I did think that as well initially, but the user_mention email didn’t stack up. I was wondering if these older posts were imported ones from a migration to Discourse? You shouldn’t get a mention notification a second time for the same post, but if a record of it wasn’t created during a migration somehow then perhaps it would think it was the first time on the category move?
Was it from a topic you had moved? Confirming this will help us troubleshoot it.
There’s a chance it is the setting disable_category_edit_notifications, try disabling that and check if email is going out when you move a topic.
You can changed it at /admin/site_settings/category/all_results?filter=disable_category_edit_notifications
I believe this is the behavior, I just moved some topics around on a personal site and got email for all the messages I was mentioned in. It very rare, and the I like folks to be notified when this is done, so I’ll live with it. But that might be a bit much for a larger community.
I mean, that’s what’s odd. Is that it isn’t power users receiving notifications. It’s … anyone who was mentioned in a post that was moved from that category to another, so we have reports of people getting 30-40 notifications.
I’ve had this happen too. It really puts you off housekeeping!!! I thought I’d been sufficiently clever by turning off the category notifications - but no! Mentions caught me out and resulted in several angry emails directed to me. Not fun.
Turning off emails altogether will save some of these, but means that the work needs to be done out of hours. And this isn’t possible on busy international forums, nor does it suppress notifications.
In future I plan to do things from the console to make sure that unwanted notifications don’t trigger.
But it sure would be nice to have a fool-proof “housekeeping” mode for staff that allows use of the GUI but completely suppresses notfications.
We saw the same thing happening with a mention in a post from 2016 that was moved to a different category, on a recently imported forum.
I cannot find any recent changes (everything related to these notifications seems at least 11 months old code) but I think it’s too coincidental to see this happening just after this was reported here.
This is absolutely totally unwanted behavior. Especially right after a migration, this should not be peoples first interaction with a Discourse forum.
Why would one want a notification to be sent out if a topic is moved to a different category anyway?
@JammyDodger@maiki is this indeed prevented by disable_category_edit_notifications ? If not, is there a way to backfill the notifications so this won’t happen again?
I don’t think doing these things from the console would prevent notifications from triggering. If you want to circumvent notifications, you would need to do it in the database (and that could have other kinds of unwanted side effects).
Isn’t think the way you schedule topics to post? Move them from a private category to a public one?
At least that is one way we use our forum software. We collaborate on posts in the staff category and then when we’re finished with them, publish them out to a public category. It would make us sad if notices didn’t go out for those.
I think there should be a way to prevent it from happening in cases where it isn’t the desired behavior.
In our case our categories function as distinct email list serves. We’ve had scenarios in the past where it was a desired behavior to have the moved topic generate notifications to go out to the new “list”. Did we want that to happen EVERY time, may be not. As I said, an option would be preferred.