justb3a

Simple Contact Form

Recommended Posts

I have a small request: form data should be stored regardless whether a mail has been sent or not. Just in case, someone forgets to install sendmail on their DigitalOcean server :D (or, on a more serious note, a component in the notification chain is failing)

Share this post


Link to post
Share on other sites

Who would forget this ??  :P  ^_^

v0.2.1 - Regardless whether a mail has been sent or not, if saveMessages is enabled, the data will be stored. Besides a corresponding log entry will be saved.

  • Like 2

Share this post


Link to post
Share on other sites

Great module, thanks for sharing. I was interesting in adding the new Google Recaptcha in addition to the honeypot. Has anyone had any luck doing so and if so any suggestions on the best approach to add it?

Thanks

Share this post


Link to post
Share on other sites

Hi all,

the module version 0.2.1 claims compatibility with PW 2.5, 2.6, 2.7 -  but not 3.0.

I tried to use it in PW 3.0.10 devns, and it works like expected as long as I leave the setting saveMessages unticked.

Checking this option throws the following message:

Fatal error: Call to a member function find() on a non-object in  ...../site/assets/cache/FileCompiler/site/modules/SimpleContactForm/SimpleContactForm.module on line 747

Line 747 of that file is

        $spamMailsMsgs = $receivedMessages->find('scf_spamMail!=');

Most likely it's some other problem and not the PW version causing this error.

But for compatibility, would it help to replace the  <?php  by  <?php namespace ProcessWire; in all the php files of the module, or is there more to do to get it compatible?
 

Share this post


Link to post
Share on other sites

Most likely it's some other problem and not the PW version causing this error.

But for compatibility, would it help to replace the  <?php  by  <?php namespace ProcessWire; in all the php files of the module, or is there more to do to get it compatible?

Replacing the php tag with the one containing the namespace isn't the solution. Modules without namespace declarations should also function in PW3.x. At the moment I'm working on a new version supporting PW3.x. I guess I'll finish that this week (the next release will provide further improvements as well).  :)

  • Like 1

Share this post


Link to post
Share on other sites

If you want to use this module with PW3.x (and only PW3.x), please pull branch feature/devns. It needs a bit more testing before I'll release it. 

  • first backup your installation
  • after upgrading the module, go to module settings, have a look at the settings – you may have to adapt something

Whats new:

  • messages will be saved as pages instead of repeater items
  • you have to define a parent page, all messages created will live under this parent
  • the page name starts with the current timestamp, you could add additional fields which should be appended
  • field selection: you can existing fields or fill in field names, after the module are saved, for each name a field will be created
  • manage settings like field type, required, additional error checks for each field
  • after the module settings are saved, all existing repeater items will be converted to pages
  • no more template creation, ProcessWire API renders the form (you can adapt the markup)
  • you may have to translate error and success messages

Have a look at the latest readme to get more information. I would love to get some feedback  ;)

  • Like 5

Share this post


Link to post
Share on other sites

Hi, and thank you for this module!

I've been trying get the feature/devns branch to work with PW 3.0.14 but ran into a problem.

I try to render the form as below:

82         <?php echo $modules->get('SimpleContactForm')->render(); ?>

and the form shows up but with the following message:

Notice: Trying to get property of non-object in /site/templates/_main.php on line 82

If I fill in the form and press send I get a "Your contact request has been send successfully!" message, and when I check the Simplecontactform-log it has a success entry. It seems like it's working so why do I get the error message on line 82? 

Thanks in advance!

Share this post


Link to post
Share on other sites

Hi @Piqsel, thanks for the feedback.

I just installed a fresh PW 3.0.14 installation, downloaded SimpleContactForm branch feature/devns, filled in module settings. Then I added 

echo $modules->get('SimpleContactForm')->render(); to home.php.
But I can't reproduce the message you received. Everything works as expected. Do you include the module call inside _main.php? Because the error notice refers to line 82 of /site/templates/_main.php and not to /site/modules/SimpleContactForm/xxx. Furthermore the module call doesn't include a property request. Apart from this you said the module seems to work, so maybe this error notice isn't related? Could you please try to restrict the issue by debugging the parts one after the other? [var_dump($modules); var_dump($modules->get('SimpleContactForm'));] You have to find out which part produces the error message.

Share this post


Link to post
Share on other sites

Hi @justb3a,

thanks for the module. I am currently trying to use SimpleContactForm (PW 2.7.2 // SCF 0.2.1) with two templates on one page (for contacting the owner and for signing up to the newsletter (e-mail and printed)). I was trying to use: 

$options = array (
  'submitName' => 'newname'

but this caused the whole page to throw an error. Would be great if you would have a hint for me to get submitName to work.

Is there a way to prevent the form to load the homepage when an error occurs. When using ajax I would like the form to set some classes on the erroneous fields – did I miss something?

Thanks for your feedback,

Depone

Share this post


Link to post
Share on other sites

Hi,

here is a working example of one of my latest projects on how to use more than one contact form on a single page (PW 2.x):

$optionsContact = array(
  'submitName' => 'submit-contact',
  'templateName' => 'estate-contact-request'
);
    
echo $modules->get('SimpleContactForm')->render($optionsContact);

$optionsRecommend = array(
'allFields'=> $allFields,
'requiredFields' => $allFields,
'submitName' => 'submit-recommend',
'templateName' => 'estate-recommend',
'emailSubject' => 'xxx',
'emailMessage' => $emailMessage,
'successMessage'=> $successMessage
);

echo $modules->get('SimpleContactForm')->render($optionsRecommend);

You can override every option from the module settings,. If you skip an option, the one from module settings will be used. So you don't have to pass any option to the first render call. Then you need to adapt the JavaScript to trigger the related form. If you pass another template you have to create it manually (by copying the generated one and then adapted it to the special needs, make sure to change the submitName).

If an error occurs, please let me know, what the error message is and when it appears (rendering the form, submitting the form, using ajax...).

Is there a way to prevent the form to load the homepage when an error occurs. When using ajax I would like the form to set some classes on the erroneous fields – did I miss something?

I noticed already that this wasn't the best idea and changed this behaviour in the devns branch (PW 3.0.x compatibility). Unfortunately there is no way to achieve the same in the "old" version working with PW below 3.x.

Share this post


Link to post
Share on other sites

Hi @justb3a,

thank you very much for your fast reply. The submitName is now working. I forgot to explicitly set a templateName on both instances, because I assumed it would fallback to the default if nothing is declared. If I set templateName and submitName on both it works.

Thanks for the description of the submit-behavior. I am currently highlighting the required fields if the user moves forward without filling them out, what seems as a legit workaround.

With one form I am running into – [FAILURE] Number of fields does not match. – even though the same hidden fields are available as on the other form. The form itself has one more field than the other one, but I set them with the allFields-key. Do you have a hint for me what I might have overlooked?

Thanks,

Depone

Edit 2016-04-14: fixed – error was caused by a field-name mismatch. 

  • Like 1

Share this post


Link to post
Share on other sites

This modal is ace but super confusing for optional use.

trying to get a second form (not on the same page) with different options and but it doesnt seem to render. e.g.

$options = array(
      'allFields' => 'email',
    );

    echo $modules->get('SimpleContactForm')->render($options);

for example this simply gives me the same form from the module settings.

doing the above with submitName, and templateName crashes and means in need to make a new template... (but why?) so i made a new template but now im getting my site twice (modal), so i exclude the _init and _main, but then the from doesnt show, should it be added to the new template now??

sorry if im missing something

Share this post


Link to post
Share on other sites

Hi @benbyf, I had the same situ until I spotted that I had not followed the instructions properly, maybe you did what I did—I copied the file `simple_contact_form.php` to a new template called `simple_membership_form.php` but then forgot to create a new corrosponding template in the PW admin. So I did that. That nearly fixed it but I guessed perhaps the plain template I had created was in some way not like the one that ships so I deleted the template I'd made in the PW Admin and instead used the Admin to make a copy of the template that ships and then changed it's name and told it to use the file `simple_membership_form.php` and it worked AOK.

Good luck! :)

I had to stop using the form for a second form as the second form needed radio options and I couldn't work out how to do that :( I might come back to ask if it turns out I can't do w/o the form :)

Share this post


Link to post
Share on other sites

I assume you 're using PW 2.7.x and the latest stable version of the module (master branch / ProcessWire module directory).

If the second form contains different fields than the first one, you need to pass a lot more params as only the 'allFields' key.

(at least requiredFields, emailFields, templateName).

As I said before the module for PW3 changed a lot and also got an improved Readme.  

If you still run into trouble, please provide an example which I can reproduce and document  ;)

(Module settings for the first form and the difference to the second one).

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @justb3a if that kind offer to document was re my possible use case, most appreciated :)

Right now I have sidestepped the requirement but if I find I need it and can't work it out I will reply here in case you have a chance to doc then :)

PS: I am using latest production 2.7 PW and latest 2.7 ver of your module (I can't move to PW 3 as I am using @kongondo's fabulous blog module which I think is not fully ready for PW 3 (sorry if I am out of date on that assumption).

Share this post


Link to post
Share on other sites

on submit the form sends me to the hompage, anyone happen to know why this might be happening?

Share this post


Link to post
Share on other sites

Hi benbyf,

Check the error log. You are likely not passing validation and getting spammed out. Check this forum on how to address it. I can't find the post right now, but will link to it when I do.

Share this post


Link to post
Share on other sites

added the Inputs and system count to the module so that it read to the logs and I got this: 2016-04-22 18:18:20    [FAILURE] Number of fields does not match. Input:7 System:9.

seems that some fields arent being submitted. do I need to specify the spam fields or thing in the submission...?

Share this post


Link to post
Share on other sites

Do all your fields match up on your form to what the module has generated? Check your template field names against what is in the module settings. Make sure you save the module if you have updated or changed any fields.

Also check the antiSpamCountAdditonalInputs in the module settings and make sure those fields exist in your template.

  • Like 1

Share this post


Link to post
Share on other sites

thats fixed it. although it does say in the module settings that these get added automatically, which in this case is obviously not true.

Share this post


Link to post
Share on other sites

Hi @justb3a,

to assist the receiver in answering to the sender, I would like to add a Reply-To-Header to the form. 

To achieve this I have added the following code to SimpleContactForm.module: 

// Set variable for E-Mail-Address to reply to
    foreach ($this->emailFields as $emailField) {
      $replyToEmail = $this->sanitizer->email($this->input->post->{$emailField});
    }
// Add Reply-To header
      $wireMail->header('Reply-To', $replyToEmail);

Would this be a feature you’d like to add to the Module? 

If yes I could fork the Repo on Github and create a Pull Request …

Share this post


Link to post
Share on other sites

hi @depone,

I assume you're referring to the latest master version which is only compatible with PW 2.x. I don't want to add any features to this version anymore. Sorry for that. But I decided to add this feature to the feature/devns branch which supports PW 3.x. There is a new module setting where you're able to set a reply-to email address. If you want to use a value from the entries of the form, you have to pass this as an option to the render function:

$options = array('emailReplyTo' => $input->scf_email);
echo $modules->get('SimpleContactForm')->render($options);
  • Like 1

Share this post


Link to post
Share on other sites

Hi all,

the module version 0.2.1 claims compatibility with PW 2.5, 2.6, 2.7 -  but not 3.0.

I tried to use it in PW 3.0.10 devns, and it works like expected as long as I leave the setting saveMessages unticked.

Checking this option throws the following message:

Line 747 of that file is

        $spamMailsMsgs = $receivedMessages->find('scf_spamMail!=');

Most likely it's some other problem and not the PW version causing this error.

But for compatibility, would it help to replace the  <?php  by  <?php namespace ProcessWire; in all the php files of the module, or is there more to do to get it compatible?

Same issue in ProcessWire 2.7.2 for me. Uhm?

--- Edit:

Fixed it: https://github.com/justonestep/processwire-simplecontactform/pull/4

Edited by Tramvai

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

      Features
      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.
       
      https://github.com/Toutouwai/AddTemplateEnhancements
    • By AAD Web Team
      Hi,
      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?
      Thanks!
      Margaret

    • 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.
      Update
      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.