Simple Contact Form

Recommended Posts

Never! change anything in the module code!

Just go to module settings (Admin > modules > SimpleContactForm > Edit) and add there the fields. Click submit, reload the form, you will see the new fields appended.

Please have a look at the documentation!


Share this post

Link to post
Share on other sites

I'm having some troubles with the form. 

I've setup everything on my localhost and every thing seems to be working fine. Then i've copied everything to my server and for some reason the form stopped working. 

When I fill in all the field i get an error: 'Please verify the data you have entered.' even though everything looks fine. The weird part is that is doesn't say anything in the Logfile. 

Do you have any idea what the problem could be?

Share this post

Link to post
Share on other sites

Thankyou for building out this form. I was trying to setup the plugin, but everytime I remove a field name I get the following error: 

Error: Call to a member function save() on null (line 1098 of /home/marmil113/marshhospital.com/site/modules/simplecontactform/SimpleContactForm.module)

Any idea what I can do?

Share this post

Link to post
Share on other sites

@carlos: I guess there is something broken with your database because the fieldgroup failed to save after removing a field. Is this a production installation? If not, I would recommend to deinstall this module and check the clear data option (please do a backup before). After that have a look at your database and clear all stuff generated by this module if there’s something left. If the deinstallation with the clean option fails, you have to do this manually.

I tested it again and everything is working as expected. 

Share this post

Link to post
Share on other sites

I've been playing around with simple contact form and it works great!

I'm pretty new to all this, i'm trying to send the form using ajax ( thats so the page doesn't refresh right? ), iv'e included jquery.simplecontactform.js using 

   <script src="<?php echo $config->urls->templates?>scripts/jquery.simplecontactform.js"></script>

on my main page.

but what do i do with 

if ($('.js-simplecontactform').length) {


iv'e tried adding it to my main page using <script> and also tried <?php> neither works.

Also is there a way to style the send confirmation text?

heres some examples of what i've done so far.



Share this post

Link to post
Share on other sites

@Mido: Not the best but simplest solution:

  •  include jQuery
  •  include SimpleContactForm script
  •  include a general js file (main.js for example) which contains the function call you mentioned above

To style the confirmation text, modify the template, add a class and add CSS for that class.

Share this post

Link to post
Share on other sites


I really like this module and got it working quite well. There's only a few issues which I've encountered. Some mails are being sent directly and other need a wait time of maybe 30 minutes to be send to the email I've set in the settings. I've excluded my IP for the spam option yet it takes a long time for some messages to get through. Any idea what triggers this?

In the /scf-messages/ I can still see all the messages right away after they have been accepted by the system.  Could it still have something to do with the spam filter?

edit: Tried another IP too, still waiting for the mail...

edit 2: Last received mail took 2h to arrive

edit 3: Now they seem to come straight away... weird...

Share this post

Link to post
Share on other sites


I'm quite sure that this behaviour is not related to this module. The spam filter only checks some stuff and if everything is fine it hands the mail over to the mail agent and saves the message. Have a look at your mail log, maybe there is a queue. If the message was saved successfully, the spam checks are passed without any problem.

Share this post

Link to post
Share on other sites

Thanks @justb3a for your module, I am finally getting to use it :)


Is there something I need to configure in SCF to ensure it uses the WireMailSMTP module to send mail rather than in-built/default methods in PW? Thanks for any comments.


I would like to sent mail via Mandrill and so as I have in the past with the PW Forms module I have installed WiremailSMPT; I noticed you said SCF now supports WireMail. I assumed that this meant when email was sent from the SCF if WireMailSMTP was installed it would automatically go via that module (and it's settings (Mandrill in my case)), but so far I am finding emails are arriving AOK but not via the WireMailSMTP module (as Mandrill is not listed in the route).

Share this post

Link to post
Share on other sites

I began editing simple_contact_form.php and found I was getting [FAILURE] CSRF Token validation failed. I back-tracked and found that, apparently, reindenting the code of the original form file with a Sublime Text plugin caused the errors..? I tried to diff the original versus the reindented one but as far as I could see nothing was 'wrong', just differently indented.

No time now to do stuff like try an alt diff tool in case the first missed something, but I thought I'd share in case this helps anyone else.

@justb3a if a copy of the indented-and-broken code would be helpful just let me know and I'll publish it on Dropbox or similar.

Share this post

Link to post
Share on other sites

@alan: Did you check that CSRF token validation works? If you load the form (frontend) there should be a hidden input containing a generated name and value:

<input type="hidden" id="_post_token" name="TOKEN1234567891X1234567891" value="A1B2c3d4efgHIj5klLmno6pQrstUVwxy" />

As said above, the name and value are generated, make sure it's not hardcoded. Also have a look at your log file (simplecontactform-log), all errors are displayed there.

I've never used WireMailSMTP – if you've figured out how to use it, please let me know!  ;)

  • Like 1

Share this post

Link to post
Share on other sites

@all Right now all is good and I am just trying to work out how to have SCF use WireMailSMTP rather than native PW transport.

It uses it out of the box, mean: you haven't to do anything in regard of SCF. SCF uses wiremail(), - and if you have installed and setup wiremailSMTP, it is used instead of the basic wiremail, which uses the PHP mail function.

  • Like 1

Share this post

Link to post
Share on other sites

@justb3a Thanks, yes the token is there and since I undid the reindenting of code it works AOK. Also thanks I have used the log to see what was wrong (very helpful, I also spotted that my test emails had hit the IP address limit per day so I upped it for testing :)

@horst Thanks, yes I assumed that it was used. But I am pretty sure it's not being used...

History: I installed and used SCF to send email (via PW built in wiremail I assume). Then I installed WireMailSMTP and set it to use my Mandrill credentials.

But email is arriving without showing Mandrill as the sender (view email headers also shows no mention of Mandrill.com) and based on all my other uses of WiremailSMTP+Mandrill I assume (where Mandrill is listed) I assume this mean Mandrill and therefore WireMailSMTP are being bypassed (I guess?).

Env: • WireMailSMTP passes it's connectivity test. • I have debug turned on.

If there's anything I can do to help test what may be happening I'd be happy to test and report.

Thanks in advance for any suggestions.

  • Like 1

Share this post

Link to post
Share on other sites

I use it on one site with wiremailSMTP and it works. But I haven't used it together with Mandrill.

I think you use a recent or latest version of SCF? (earlier version hasn't supported wiremail())

You may check in the headers of your emails for the User-Agent, e.g. ProcessWire/WireMail or ProcessWire/WireMailSMTP or ...

  • Like 1

Share this post

Link to post
Share on other sites

@horst Thanks for the suggestions, I will check and report back in case it's of any help to others.

  • Like 1

Share this post

Link to post
Share on other sites

@horst I checked and

  • SCF is 0.1.2 which is the latest at the moment = ✔
  • header says "...X-Mailer: ProcessWire/WireMail..." = ✖

so my setup (WireMailSMTP ver 0.1.13 on a PW 2.7.0 site and SCF) seems to be working AOK but emails are bypassing WireMailSMTP :'(

@justb3a and/or @horst : if there is anything I could do here to help fix this for me (and I assume others) then I would be happy to try stuff and report back/thanks for any suggestions you may have :)

  • Like 1

Share this post

Link to post
Share on other sites

Fixed the problem where WireMailSMTP is being bypassed in favour of WireMail...

@justb3a I would usually leave module code 100% alone, but comparing how mail is called in another site I noticed it was different, so I edited `SimpleContactForm.module` around line 478 like this: 

// Below original module code bypasses WireMailSMTP
// $wireMail = new WireMail();

// Below does not bypass WireMailSMTP
$wireMail = wireMail();

and email is then sent via WireMailSMTP. If I edit it back to the original then it bypasses WireMailSMTP and I can switch back and forth depending on how I leave the code around line 478.

If this is this something you would like me to log on git etc then please let me know as I would love to have an official (unedited) copy of your excellent module that used WireMailSMTP.

Sorry if I explained that all badly and thanks again for this module, cheers, -Alan

  • Like 3

Share this post

Link to post
Share on other sites

@alan: WOW! What a great find.  ^-^  You are right. I have checked this and yes, on the site I thought it would working together, it also bypasses SMTP as you described it.

@justb3a: please can you fix this with one of the next releases?

  • Like 1

Share this post

Link to post
Share on other sites

new version 0.2.0 brings in some new features:

  • supports multiple instances
  • allows usage of full ProcessWire API in options
  • allows to render more than one contact form on a page
  • allows to send more than one email
  • makes validation hookable
  • read on
  • Like 4

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By horst
      Wire Mail SMTP

      An extension to the new WireMail base class that uses SMTP-transport

      This module integrates EmailMessage, SMTP and SASL php-libraries from Manuel Lemos into ProcessWire. I use this continously evolved libraries for about 10 years now and there was never a reason or occasion not to do so. I use it nearly every day in my office for automated composing and sending personalized messages with attachments, requests for Disposition Notifications, etc. Also I have used it for sending personalized Bulkmails many times.

      The WireMailSmtp module extends the new email-related WireMail base class introduced in ProcessWire 2.4.1 (while this writing, the dev-branch only).
      Here are Ryans announcement.

      Current Version 0.2.6
      get it from the Modules Directory Install and Configure

      Download the module into your site/modules/ directory and install it.

      In the config page you fill in settings for the SMTP server and optionaly the (default) sender, like email address, name and signature.
      You can test the smtp settings directly there. If it says "SUCCESS! SMTP settings appear to work correctly." you are ready to start using it in templates, modules or bootstrap scripts.

      Usage Examples
      The simplest way to use it:
      $numSent = wireMail($to, $from, $subject, $textBody); $numSent = wireMail($to, '', $subject, $textBody); // or with a default sender emailaddress on config page This will send a plain text message to each recipient.
      You may also use the object oriented style:
      $mail = wireMail(); // calling an empty wireMail() returns a wireMail object $mail->to($toEmail, $toName); $mail->from = $yourEmailaddress; // if you don't have set a default sender in config // or if you want to override that $mail->subject($subject); $mail->body($textBody); $numSent = $mail->send(); Or chained, like everywhere in ProcessWire:
      $mail = wireMail(); $numSent = $mail->to($toEmail)->subject($subject)->body($textBody)->send(); Additionaly to the basics there are more options available with WireMailSmtp. The main difference compared to the WireMail BaseClass is the sendSingle option. With it you can set only one To-Recipient but additional CC-Recipients.
      $mail = wireMail(); $mail->sendSingle(true)->to($toEmail, $toName)->cc(array('person1@example.com', 'person2@example.com', 'person3@example.com')); $numSent = $mail->subject($subject)->body($textBody)->send(); The same as function call with options array:
      $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); There are methods to your disposal to check if you have the right WireMail-Class and if the SMTP-settings are working:
      $mail = wireMail(); if($mail->className != 'WireMailSmtp') { // Uups, wrong WireMail-Class: do something to inform the user and quit echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; return; } if(!$mail->testConnection()) { // Connection not working: echo "<p>Couldn't connect to the SMTP server. Please check the {$mail->className} modules config settings!</p>"; return; } Following are a ...

      List of all options and features

      testConnection () - returns true on success, false on failures

      sendSingle ( true | false ) - default is false

      sendBulk ( true | false ) - default is false, Set this to true if you have lots of recipients (50+)

      to ($recipients) - one emailaddress or array with multiple emailaddresses

      cc ($recipients) - only available with mode sendSingle, one emailaddress or array with multiple emailaddresses

      bcc ($recipients) - one emailaddress or array with multiple emailaddresses

      from = 'person@example.com' - emailaddress, can be set in module config (called Sender Emailaddress) but it can be overwritten here

      fromName = 'Name Surname' - optional, can be set in module config (called Sender Name) but it can be overwritten here

      priority (3) - 1 = Highest | 2 = High | 3 = Normal | 4 = Low | 5 = Lowest

      dispositionNotification () or notification () - request a Disposition Notification

      subject ($subject) - subject of the message

      body ($textBody) - use this one alone to create and send plainText emailmessages

      bodyHTML ($htmlBody) - use this to create a Multipart Alternative Emailmessage (containing a HTML-Part and a Plaintext-Part as fallback)

      addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
      (only available if a signature is defined in the config screen)

      attachment ($filename, $alternativeBasename = "") - add attachment file, optionally alternative basename

      send () - send the message(s) and return number of successful sent messages

      getResult () - returns a dump (array) with all recipients (to, cc, bcc) and settings you have selected with the message, the message subject and body, and lists of successfull addresses and failed addresses,

      logActivity ($logmessage) - you may log success if you want

      logError ($logmessage) - you may log warnings, too. - Errors are logged automaticaly
      useSentLog (true | false) - intended for usage with e.g. third party newsletter modules - tells the send() method to make usage of the sentLog-methods - the following three sentLog methods are hookable, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here

      sentLogReset ()  - starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter

      sentLogGet ()  - is called automaticly within the send() method - returns an array containing all previously used emailaddresses

      sentLogAdd ($emailaddress)  - is called automaticly within the send() method
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
    • By ukyo
      Call ProcessWire API Functions Inside STRING
      Github Repo
      Current status : BETA
      Each called method must return string value !
      I added all functions, but not tested all. I focused page(), page()->render and field properties (label, description and notes). I also tested some basic pages() api calls.
      Your API calls must start with { and must end with }. For use multiple arguments inside functions, separate arguments with ~ char.
      NOTE If you pass directly arguments to api {page(title)}, this call will check for requestedApiCall()->get(arguments).
      processString(string, page, language); Get page title <?php $str = "You are here : {page:title}"; echo processString($str); ?> Get page children render result <?php $str = "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.<hr>{page:render:children}"; echo processString($str); ?> Get homepage title <?php $str = "You can visit our <a hre='{pages(1):url}'>{pages:get(1):title}</a>"; echo processString($str); ?> Get title field label, description or notes <?php $str = "Our title field properties are : label: {label(title)} - description: {description(title)} - notes: {notes(title)}"; echo processString($str); ?> Multiple examples <?php $str = " <ul class='uk-list uk-list-striped'> <li><b>01: GET FIELD LABEL</b> <code>&#123;label(title)&#125;</code> <b>RESULT :</b> <code>{label(title)}</code></li> <li><b>02: GET FIELD LABEL WITH PREFIX</b> <code>&#123;label(title~=> )&#125;</code> <b>RESULT :</b> <code>{label(title~=> )}</code></li> <li><b>03: GET FIELD LABEL WITH SUFFIX</b> <code>&#123;label(title~~ <=)&#125;</code> <b>RESULT :</b> <code>{label(title~~ <=)}</code></li> <li><b>04: GET FIELD DESCRIPTION</b> <code>&#123;description(title)&#125;</code> <b>RESULT :</b> <code>{description(title)}</code><br> <li><b>05: GET FIELD DESCRIPTION WITH PREFIX</b> <code>&#123;description(title~=> )&#125;</code> <b>RESULT :</b> <code>{description(title~=> )}</code></li> <li><b>06: GET FIELD DESCRIPTION WITH SUFFIX</b> <code>&#123;description(title~~ <=)&#125;</code> <b>RESULT :</b> <code>{description(title~~ <=)}</code></li> <li><b>07: GET FIELD NOTES</b> <code>&#123;notes(title)&#125;</code> <b>RESULT :</b> <code>{notes(title)}</code><br> <li><b>08: GET FIELD NOTES WITH PREFIX</b> <code>&#123;notes(title~=> )&#125;</code> <b>RESULT :</b> <code>{notes(title~=> )}</code></li> <li><b>09: GET FIELD NOTES WITH SUFFIX</b> <code>&#123;notes(title~~ <=)&#125;</code> <b>RESULT :</b> <code>{notes(title~~ <=)}</code></li> <li><b>10: GET PAGE TITLE</b> <code>&#123;page(title)&#125;</code> <b>RESULT :</b> <code>{page(title)}</code></li> <li><b>11: GET PAGE TITLE</b> <code>&#123;page:title&#125;</code> <b>RESULT :</b> <code>{page:title}</code></li> <li><b>12: GET PAGE RENDER TITLE</b> <code>&#123;page:render:title&#125;</code> <b>RESULT :</b> <code>{page:render:title}</code></li> <li><b>12: GET HOMEPAGE TITLE</b> <code>&#123;pages:get(template=home):title&#125;</code> <b>RESULT :</b> <code>{pages:get(template=home):title}</code></li> <li><b>13: GET HOMEPAGE TEMPLATE ID</b> <code>&#123;pages:get(template=home):template:id&#125;</code> <b>RESULT :</b> <code>{pages:get(template=home):template:id}</code></li> </ul> "; echo processString($str); ?>
    • By Robin S
      This module corrects a few things that I find awkward about the "Add New Template" workflow in the PW admin. I opened a wishlist topic a while back because it would good to resolve some of these things in the core, but this module is a stopgap for now.
      Originally I was going to share these as a few standalone hooks, but decided to bundle them together in a configurable module instead. This module should be considered alpha until it has gone through some more testing.
      Add Template Enhancements
      Adds some efficiency enhancements when adding or cloning templates via admin.

      Derive template label from name: if you like to give each of your templates a label then this feature can save some time. When one or more new templates are added in admin a label is derived automatically from the name. There are options for underscore/hyphen replacement and capitalisation of the label. Edit template after add: when adding only a single template, the template is automatically opened for editing after it is added. Copy field contexts when cloning: this copies the field contexts (a.k.a. overrides such as column width, label and description) from the source template to the new template when using the "Duplicate/clone this template?" feature on the Advanced tab. Copy field contexts when duplicating fields: this copies the field contexts if you select the "Duplicate fields used by another template" option when adding a new template. Usage
      Install the Add Template Enhancements module.
      Configure the module settings according to what suits you.
    • By AAD Web Team
      I've put in a support request (as a followup on an existing one) for this but it's nearly 10pm Ryan's time, so I thought I'd ask on here just in case someone can help...
      Yesterday we purchased ProDrafts, but I couldn't get the key to validate. Every time I hit submit on the module settings screen the key would be removed from the field I entered it in, and then it would complain about the missing value. I put in a support request and Ryan responded last night. It turned out it was because we're behind a proxy/firewall. He gave me a fix to get around that issue - some code to go into admin.php. I put that code in and saved admin.php, but now I can't even get into our admin anymore!
      (Just to clarify, I took the code back out and saved admin.php but that made no difference. It's definitely not the new code causing the error.)
      The errors relate to a lack of permission on the ProDrafts module (see attached screenshot). We do have a key, but evidently the code Ryan gave me to add the key in via admin.php isn't taking effect before the error is thrown...?
      I tried removing the ProDrafts directory from the modules directory, but that hasn't helped.
      Is there a hook I can put in somewhere to tell it not to load ProDrafts at all, or not check the permissions? Or is there some way to manually uninstall it from the file system?

    • By DaveP
      I just made a textformatter module that allows you to insert dummy content (lorem ipsum style) in text fields via shortcodes.
      Usage is simple - just type for example [dc3] into a textarea with this textformatter applied (plain textarea or CKEditor) and it will be replaced at runtime by 3 paragraphs of dummy content. It can also be used to populate text fields (for headings etc) using e.g. [dc4w]. This will produce 4 words (rather than paragraphs) at runtime.
      The actual content comes from an included 'dummytext.txt' file containing 50 paragraphs of 'Lorem ipsum' from lipsum.com. The 50 paragraphs is arbitrary - it could be 10 or 100 or anything in between, and the contents of that file can be changed for your own filler text if you wish.
      The slightly clever bit is that for any given page, the same content will be returned for the same tag, but the more paragraphs available in 'dummytext.txt', the less likely it is that two pages will get the same content (very roughly speaking - it's actually based on the page ID) so content selection is determinate rather than random, even though only the tags are saved to the db.
      Tags now work like this -
      [dc3] - Show 3 paragraphs ([dc:3], [dc3p] & [dc:3p] all do the same). [dc3-6] - Show 3 to 6 paragraphs randomly per page load ([dc:3-6], [dc3-6p] & [dc:3-6p] all do the same). [dc3w] - Show 3 words ([dc:3w] does the same). [dc3-6w] - Show 3 to 6 words randomly per page load ([dc:3-6w] does the same). <End update on tags.>
      If you think it might be useful, you can download it from GitHub and give it a try.