Default Settings for Notify Are Enabled & No Way to Change for All Users
josephgut - March 4, 2009 - 21:51
| Project: | Notify |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Description
We recently installed the Notify module and started to receive many complaints from members saying that they didn't want to receive so many emails. It seems that the default setting is to have the master switch and e-mail for new content "On" straight out of the box. The biggest issue is that there doesn't appear to be a way within the functionality of the module to turn Disable notifications for all users or for a default setting for new users. Of course this can be done via MySQL, but seems there should be a way within the module. Perhaps I'm missing something?
#1
I don't think this is exactly what you're looking for, but it might help:
admin/user/user/notify
#2
#3
I have the same issue. In the register poage by default the
Receive email notifications of news posted to this site. Notifications are sent every 9 hours.
is ENABLED - which is misleading the subscribers to get notifications.
I would like have this disabled by default and let user tick it if they want.
Anyway to do this?
Also surprisingly while i have under permissions - access notify and administer notify - only enabled for the "ADMIN user" - the option to receive notification is enables and available to any user.
What do i need to do so that the option to recevie notification is only available to admin or any other specific users.
#4
Add this line to notify.module :
if (!user_access('access notify')) return;right after:
function _notify_user_reg_fields() {which is at about line 136.
#5
Here's a patch for both setting a default & checking anon access on the reg form. Also committed to dev version.
#6
Was this committed only to the -dev version for D5, not D6 which this issue is about?
The time stamps on the main module page indicate no such update for the 6.x-dev version.
#7
ehh. It was committed to CVS head, which is now the Drupal 6 version, but apparently drupal.org doesn't know that. The CVS tree for this project was a mess when I inherited it, and then I made it worse, and then I made it better... but I still can't get a dev package generated for HEAD. I've posted a support ticket to the d.o wizards. Meanwhile, you can get CVS HEAD for the latest dev code.