Closed (fixed)
Project:
Team Notifications
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Feb 2009 at 20:10 UTC
Updated:
9 Jul 2009 at 13:30 UTC
Hey Team (Notifications),
I was using this module with the fancy checkboxes and all but something happened and they disappeared. Now I have the autocompleting field where I have to type in each username that I want to notify, which is very painful to do. There also appears to be a portion of a check box below the autocompleting field.
Has anyone else had this happen? Does anyone know how to fix it?
The content is a custom type with CCK fields in Drupal 6. I have attached a screenshot below.
Thanks in advance for any help,
randyesq
| Comment | File | Size | Author |
|---|---|---|---|
| team_notify_nochecks.jpg | 9.14 KB | randyesq |
Comments
Comment #1
randyesq commentedI believe I found the answer to my own question, and hopefully this will bring some light to others when they experience this problem.
In notifications_team.module around line 172 the code reads:
I now see why the nifty checkboxes are disappearing; the module is designed to do so. This brings two issue to mind:
1) The module documentation should state that when there are more than 20 users, the checkboxes are converted into an autocomplete field, and
2) I was under the impression that one of the Team Notifications main selling points (for me) was the simplicity involved with visual selection of team members. It would be nice in the future to have a Team Notifications setting page where this number could be set by those with the appropriate privileges.
Comment #2
David Goode commentedHaha yeah, sorry about that. We are working on a documentation page for this and sendto where that should be addressed. Such a patch would be pretty straightforward though if anyone wants to try their hand at it, and I'd be happy to commit it.
David
Comment #3
David Goode commentedNow there is a settings field under the notifications content form, I'll mark this fixed.
Thanks,
David