Behavior of 'Default Notification Settings' page

  • Affected Version
    WoltLab Suite 5.5

    The 'Apply changes for existing users also' option only applies the last changes.

    That is, that page should be used to configure the predefined notification settings for your website, and the selected options should apply ALL options (just changed now or not) to all users.

    Otherwise, to ensure that all users have the default predefined options, you must change each option twice (at least) for the changes to take effect. It is counterintuitive.

    Summary: If I click on 'Apply changes for existing users also' option, I expect that the settings set on that page (just now or before) will be applied to all users.

  • Aethior August 18, 2023 at 9:37 PM

    Changed the title of the thread from “Behavior of 'Default Notification Settings'” to “Behavior of 'Default Notification Settings' page”.
  • Otherwise, to ensure that all users have the default predefined options, you must change each option twice (at least) for the changes to take effect. It is counterintuitive.

    Well, no. This is intended to allow the administrator to force set a particular setting for all users without overwriting every single setting.

  • I can see that point, but it still seems counterintuitive to me.

    Let me explain my last use case (not a common use case):

    I have created several test users (alpha and beta) and I wanted to test the notification settings. I have used the Default Notification Settings page to set all notifications as active. I have applied the changes to all users.

    However, when I checked my account notification settings there were no changes and I did not understand what was happening. My question was: How is it possible that I have set all notifications on as default and the changes have not been applied? Until you explained that point I was unable to see it.

    I suppose it may be an exceptional use case.

    Edited once, last by Aethior (August 18, 2023 at 10:52 PM).

  • You are correct, that specific use case is not handled very well by that form, but if you really want to do it, it takes just a tad more effort. The primary motivation behind the current behavior is to offer an implicit “guard rail” that prevents you from completely wiping any users settings by accident.

    We consider any interference with the users’ preference to be bad in general but at the same time understand that it might be sometimes necessary to adjust a single setting. Apart from testing and early setup work its hard to imagine a situation where modifying all settings of every user is necessary at all. I mean, yes, the behavior is heavily opinionated, but has proven itself over the years (it is around for well over a decade already).

  • Alexander Ebert August 20, 2023 at 11:19 PM

    Added the Label Works as designed

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!