Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When a user subscribed to a new node, category etc. the system automatically picks the frequency of the notification as set in the "Send Interval" in "Preferences", i.e. if that is set to "daily" for this user all new subscriptions are automatically set to daily. If the user chooses another "Send Interval" in "Preferences", all new subscriptions use this one while the old ones stay as they were. This is as I would expect the behaviour.
However, users on our site cannot change the "Send Interval" of an individual subscription afterwards. That means a subscription for, for example, a node that is set to "daily" cannot be changed to any other value by the user - even Drupal's User1 cannot do that. The only way to change it is to set the "Send interval" in "Preferences" to the interval you want it the individual subscription to be, then delete the individual subscription and finally to subscribe anew - then you get the interval set in "Preferences".
I think it should be possible for a user the change the interval after setting up the subscription - otherwise there is not point in giving them a dropdown menu to do so. I did suspect that this is maybe a configuration issue on our site but as it also applies to the User1 I don't think this can be something about permission not being set up correctly.
Comments
Comment #1
salvisI pretty much agree with what you say about "expected behavior."
Hmm, I'm confused. On what URL do you see a "dropdown menu" that cannot be changed?
Comment #2
Anonymous (not verified) commentedOn all pages where the user can set the interval:
/user/NUMBEROFUSER/subscriptions/type
/user/NUMBEROFUSER/subscriptions/taxa
/user/NUMBEROFUSER/subscriptions/group
/user/NUMBEROFUSER/subscriptions/node
Whatever interval has been set there initially cannot be changed, i.e. I subscribe to a group and want my messages "daily" that is fine but if I later want to change it to "hourly" the system does not accept it, even for USER1.
Comment #3
salvisWhat do you mean with "the system does not accept it"? I can change it to whatever value I want, and the new value stays put. I just tried this with user/3/subscriptions/type, a non-privileged user. Forgive me for asking this, but you do click on the [Save] button, don't you?
Due to the algorithm that I described in another thread of yours, any changes here will not take effect immediately. Any notifications that have already been queued have their eligibility timestamp stored with them and won't be mailed until that time has passed, but newly queued notifications should use the changed interval.
Comment #4
Anonymous (not verified) commentedThe problem that we experience is directly related to hitting the save button: users can change the interval to whatever setting they want but as soon as they hit the save button all settings revert to what they have been before clicking save. So: login, go to subscriptions, pick a subscription, changes the interval from Y to X, the page displays X, then click save - settings reverts to Y.
The only way of changing it is deleting the individual subscription and setting up a new one; however, this again cannot be changed.
I hope this clarifies the problem.
Comment #5
salvisPlease update to the current -dev version. Not that there's a fix in there, but it behaves just fine for me, and we have to narrow this down somehow...
Comment #6
Anonymous (not verified) commentedUpdating to -dev did the trick!
Comment #7
salvisOk, glad it works. I don't see which of the changes could have helped with your issue, though. Maybe you had somehow "customized" your copy of 5.x-2.3?
Anyway, no use in digging deeper.