Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
It would expand the usefulness of the Contact Form
- would have a editable page title
- could have a META Desc
- could add fields as required
- could add image to jazz up
- could generate a Contact log via Views
We can leave these separately, but the best and easiest way that integrating contact.module with the field API would be converting them to nodes. We can leave these separate for now if someone wants to provide a patch for this issue, but I'm definately going to bump this to D8.
Wait. What? Why on earth would contact module have anything to do with nodes?
AFAIK this is allowing the contact form itself to have additional fields placed onto it; nothing to do with nodes. I'm actually not sure if this is a D7 or D8 thing; could really go either way. Though it feels more D8-ish, given our ~week-long timeframe.
Yeah I don't know enough about the Fields API yet to attempt to try and do this in a week with everything else going on. Anyone else is more than welcome to drive this for D7, but I can't right now.
I think there would be some use to site-wide contact form submissions being nodes. You could have all your admins be able to keep a log of them on the site. And what if e-mail sending suddenly doesn't work. No one receives that e-mail and it's lost. If it were a node we'd have a record of it.
Little more controversial making personal contact mails nodes. Plus, it's hard for me to see how we could add fields to contact forms and generate e-mails like we currently do. This definitely needs more discussion and research, hence postponed. :/
Eh. That's definitely a separate request, and something I don't think I'd like to see in core. We'd need to have core shipping with a node access module of some kind, and the performance issues associated with that.
Comments
Comment #1
yched commentedHm, hadn't tought about this. Interesting and doable, I guess...
Comment #2
green monkey commentedIt would expand the usefulness of the Contact Form
- would have a editable page title
- could have a META Desc
- could add fields as required
- could add image to jazz up
- could generate a Contact log via Views
Comment #3
dave reidThis should be a little easier with fields in core. Maybe a better solution is to implement #85814: Convert contact emails into nodes?
Comment #4
naught101 commentedsubscribing
Comment #5
dave reidMuch better solution is to convert contacts into nodes. Marking this as a duplicate of #85814: Convert contact emails into nodes.
Comment #6
naught101 commentedDave: that bug isn't really related. It's about contact form submissions, while this is about the actual contact form itself.
Although it seems that some of jwells's suggestions would go better under that bug
Comment #7
dave reidWe can leave these separately, but the best and easiest way that integrating contact.module with the field API would be converting them to nodes. We can leave these separate for now if someone wants to provide a patch for this issue, but I'm definately going to bump this to D8.
Comment #8
webchickWait. What? Why on earth would contact module have anything to do with nodes?
AFAIK this is allowing the contact form itself to have additional fields placed onto it; nothing to do with nodes. I'm actually not sure if this is a D7 or D8 thing; could really go either way. Though it feels more D8-ish, given our ~week-long timeframe.
Comment #9
dave reidYeah I don't know enough about the Fields API yet to attempt to try and do this in a week with everything else going on. Anyone else is more than welcome to drive this for D7, but I can't right now.
I think there would be some use to site-wide contact form submissions being nodes. You could have all your admins be able to keep a log of them on the site. And what if e-mail sending suddenly doesn't work. No one receives that e-mail and it's lost. If it were a node we'd have a record of it.
Little more controversial making personal contact mails nodes. Plus, it's hard for me to see how we could add fields to contact forms and generate e-mails like we currently do. This definitely needs more discussion and research, hence postponed. :/
Comment #10
webchickEh. That's definitely a separate request, and something I don't think I'd like to see in core. We'd need to have core shipping with a node access module of some kind, and the performance issues associated with that.
Comment #11
naught101 commentedThis shouldn't actually be postponed, since it isn't waiting on #85814: Convert contact emails into nodes
Comment #12
Teddd commentedsubscribing
Comment #13
sunI didn't know of this issue — I've essentially done exactly this in:
#1825044: Turn contact form submissions into full-blown Contact Message entities, without storage
So even though this issue is older, I'm marking it as duplicate.