#6310 - Top-level notifications where categories are supported should define a default, not all

  • By
  • Added
  • 18 views
Identifier #6310
Issue type Feature request or suggestion
Title Top-level notifications where categories are supported should define a default, not all
Status Open
Handling member Deleted
Addon core_notifications
Description Currently, in your notification settings, if you enable (or disable) a notification for a type that has categories, then the setting applies to every category.

Instead, for types with categories, make it so that the top-level ticks define the *default* (e.g., what is selected when you monitor or auto-monitor a category in that type) rather than applying retroactively and immediately to every category in that type.

Also, have a link enabling the member to retroactively apply their top-level selection either to all categories or to the categories they are currently monitoring.
Additional information This resolves two issues:
  • Usually, types with categories have the potential to send out a lot of notifications (e.g., forum posts). This can easily create spam issues if someone were to enable notifications on every category.
  • This resolves an issue where auto-monitoring always chooses the "most used" settings defined by a member; maybe the member wants to define a default for a particular type.

Example:
My auto-monitoring only enables e-mail notifications for comments. But I also want web notifications for content that I monitor or get auto-monitored. If I tick the top-level box, then I get web notifications for comments on literally every piece of content. I don't want that either. The only way to do this is to go through the hundreds of categories and manually apply them.
Funded? No
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated