When a contact message would be a node this module will become much more flexible. For example it becomes possible to use views.module to list all contact messages.
When a contact message would be a node this module will become much more flexible. For example it becomes possible to use views.module to list all contact messages.
Comments
Comment #1
casey commentedComment #2
dropcube commentedMaybe a good idea, but it is not going to happen in 6.x. Moving to 7.x queue.
Comment #3
pp commentedI think it isn't contact.module task.
Because you shall can do following:
1. Create a new content type name like "contact"
2. Create a new action "Send email"
3. Setting the create contact trigger.
The 3. isn't working yet. Just you set the create content(all content types) trigger ;)
pp
Comment #4
dave reidThis isn't really active right now, so setting as postponed.
Comment #5
dave reidComment #6
dave reidBumping to D8. Definitely want to do this.
Comment #7
dave reidMarked #412688: Integrate the contact form with fields as a duplicate of this since we'd have fields available if we convert contact mails to nodes.
Comment #8
gpk commentedYou can always use webform module if you need this functionality sooner rather than later.
Comment #9
jody lynnI think pp is on the right track. Instead of converting into nodes, the first step should be to add a trigger (integration with trigger module).
Comment #10
sunI didn't know of this issue — the "convert everything into a node" paradigm is obviously obsolete, as we have an entity system now :)
However, I'm actively working to convert contact messages into entities in:
#1825044: Turn contact form submissions into full-blown Contact Message entities, without storage