Working with Mass Contact
Ninja Overlord - August 10, 2008 - 13:18
| Project: | Contact Forms |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Can this be made to work with another module, should it be installed? The module to which I refer to is Mass Contact.
I already posted an issue in that module's issue queue, and now I am posting here to see which is easier to do.
#1
Have you tried it?
#2
I have not yet, I'm firstly wondering if it would be a friendly addition if I went ahead and worked on it and made a patch available. If it would not be, then I'll work within the Mass Contact module, for the patch would be friendly with that maintainer for sure.
#3
The changes to the mass contact form module needed to add the features of my module are not huge. I once created a patch for the core contact module and it required significantly less code than my module. Also to modify my module to work with Mass Contact would require a lot of duplicate code because they use different tables to The core Contact module. So, to me, it would make more sense (especially as the maintainer is open to it) to create a patch for the Mass Contact module.
My Contact Forms module was previously named Contact List module and the code was different in that I took advantage of Drupals behaviour of when you enter a path that doesn't exist like "contact/Bill_Smith" Drupal will drop back to "Contact". So what I did was checked if there was arg(1) and if there was, I checked if a category existed then altered the form. In Contact Forms I generate unique paths in hook_menu for each category so I could redirect "contact" to another "directory" page where people could list the categories as links and add descriptions.
I hope that helps
Regards
Geoff
#4