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

casey’s picture

Version: x.y.z » 6.x-dev
dropcube’s picture

Version: 6.x-dev » 7.x-dev

Maybe a good idea, but it is not going to happen in 6.x. Moving to 7.x queue.

pp’s picture

I 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

dave reid’s picture

Status: Active » Postponed

This isn't really active right now, so setting as postponed.

dave reid’s picture

Title: rewrite using node system » Convert contact emails into nodes
dave reid’s picture

Version: 7.x-dev » 8.x-dev

Bumping to D8. Definitely want to do this.

dave reid’s picture

Marked #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.

gpk’s picture

You can always use webform module if you need this functionality sooner rather than later.

jody lynn’s picture

I 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).

sun’s picture

Status: Postponed » Closed (duplicate)

I 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