Active
Project:
Advanced Contact
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Dec 2009 at 22:30 UTC
Updated:
25 May 2010 at 13:52 UTC
I have a problem user on my site who is contacting my members to spam them but is otherwise a useful member. That's got me thinking of some enhancements to the contact module. When I went looking to see if these exist, I found this module. Would you be interested in these or is that totally out of scope? Depending on how hard I find this to write, I'm thinking late January / February.
Possibly more... That's what came to mind from dealing with this.
If anyone knows where those features already exist, please let me know. I have no desire to re-invent the wheel. :)
Michelle
Comments
Comment #1
JaredAM commentedIt would seem like you could do a lot of what you want with the flag module.
Also, Mail logger captures all outgoing mail. Very handy module.
Comment #2
michelleNot sure how flag would help with this but Mail Logger definitely would. Thanks for the link!
Michelle
Comment #3
neclimdulWell you could probably do something with flagging a user as naughty and then something...
The listed points I'm most interested in implementing personally would be.
4) Pretty straight forward limiting contact by role.
5) We could probably provide some sort of API for limiting ideally. Then an implementation for User Relationships.
Comment #4
joelstein commentedI recently released the Contact Save module, which stores contact form submissions in the database and gives admins the ability to respond to the messages through the website. Plus, there is a great module called Contact Forms which separates each category into it's own contact form.
Why don't we all three join forces? We are all doing one or two little modifications to beef up the way the core contact.module works. Looking at the three names (Advanced Contact, Contact Forms, and Contact Save), I think Advanced Contact has the best name, and it's the oldest.
I'd be happy to merge the three modules together (they're each pretty small), and become a maintainer of this module to help ease the transition. What do you think?
Comment #5
neclimdulI'd be happy to work through that. Why don't we work up some patches and see what it would look like. I'm also not sure how contact form would be merged. Its mostly the same thing as what this module is doing with a different implementation from what I understand.
Comment #6
joelstein commentedOkay, this might be a little overwhelming, but I just compiled a list of modules which in greater or lesser ways tap into the core contact module. I guess the question is, which of these should we try to tackle? Plus, some of them aren't really compatible with one another. Anyway, here's the (alphabetized) list, and we can brainstorm on the next steps:
Advanced Contact
Anonymous Contact
Author Contact
Contact attach
Contact form blocks
contact form fields
Contact Form on Node
Contact Forms
Contact Hide Email
Contact Link
Contact profile
Contact Redirect
Contact Role
Contact Save
Contact Tracker
Custom Contact
Flood exemption
Google Analytics Contact Form
Graceful Email Obfuscation Filter
Mass Contact
Newsletter Checkbox
OG Contact
Simplenews Contact Checkbox
tContact
Comment #7
generalelektrix commentedI don't think it's possible to merge tContact functionalities into Contact Forms, but Contact Forms MUST be made compatible with its functionnalities. The latest version is not, because it will not consider the language of the request for a contact form. I had to hack into the module code to add it. It's just a matter of checking for the form language in the SQL query using the $language global object.
I agree a merge of Advanced Contact and Contact Forms seems important. I never used the other modules, so I can't really be of any help concerning these, but I encourage you guys to join forces.
Comment #8
generalelektrix commentedOops. Sorry, double posted my previous message because of a guru meditation error....