justb3a

Simple Contact Form

Recommended Posts

Just a simple contact form including spam protection.
Optional support for Twig (TemplateTwigReplace) as template engine.
 
---
 
Please have a look at the readme on github!
If you upgrade from version 0.0.9 and below, there are some extra steps to be taken.

The Guides

Edited by justb3a
Added the "module" tag and removed it from title.
  • Like 27

Share this post


Link to post
Share on other sites

This is great. I thought about doing a contact form module myself as i would have needed it in nearly every single project we've done recently.

Btw: I like that all of your modules support TemplateTwigReplace! :)

Share this post


Link to post
Share on other sites

Looks great, have to try it out soon. Thanks for your contribution.

Share this post


Link to post
Share on other sites

Amazing!

I've been mostly doing this functionality in my templates as far as I haven't needed any save functionality but I will be defiantly be checking this out when i do.

Share this post


Link to post
Share on other sites

Little update: I added one more spam protection:

  • antiSpamCountAdditionalInputs - Number of additional inputs. Spam bots often send more than the number of available fields.

Thanks for your feedback  :)

Share this post


Link to post
Share on other sites

Very nice.. just tryed it out and works perfectly.

I had a little trouble with ajax but sorted out in the end.

My fault for copy and pasting from the instructions but this code below needs to be changed:

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

to

if ($('.js-simple_contact_form').length) {
   $.simplecontactform($('.js-simple_contact_form'));
}

just a matter of class name if using the default class of the form in simple_contact_form.php

  • Like 2

Share this post


Link to post
Share on other sites

@dazzyweb thanks for pointing that out! I wanted to answer your message but you solved it too fast  :)

Share this post


Link to post
Share on other sites

Hello, 

I was glad to find this module, cause that was just what I looked for.. but I upload the module and when I Install it, I have an error : Method Modules::getInstall does not exist or is not callable in this context

But If I go back in the module page, It seems well installed (I have access to the settings), but when I call the form in my template, an error appears : Error Exception: Method Modules::getInstall does not exist or is not callable in this context (in /home/www/d7a3bc5db5bed31cde906ac7976f3d83/web/wire/core/Wire.php line 231)

Any ideas ? Maybe I skipped a step...

I'm not a Master in PW, but I globally understand how it works..

Thanks in advance.

Share this post


Link to post
Share on other sites

Hi @nyo08,

which version of ProcessWire are you using?

I found a similar error and changed my code as explained.

Please clone the module (github) and checkout  hotfix/2.4-dependency and try again. And please let me know if everything works as expected.

I tested it (ProcessWire 2.5.3) without any problems.

git clone git@github.com:justonestep/processwire-simplecontactform.git SimpleContactForm
cd SimpleContactForm
git checkout  hotfix/2.4-dependency

Share this post


Link to post
Share on other sites

Hi @nyo08,

which version of ProcessWire are you using?

I found a similar error and changed my code as explained.

Please clone the module (github) and checkout  hotfix/2.4-dependency and try again. And please let me know if everything works as expected.

I tested it (ProcessWire 2.5.3) without any problems.

git clone git@github.com:justonestep/processwire-simplecontactform.git SimpleContactForm
cd SimpleContactForm
git checkout  hotfix/2.4-dependency

Indeed I update my PW (I had the 2.2.4 version... looks like I miss some update ahah) and that's perfecly work

O0

Share this post


Link to post
Share on other sites

This module seems to be great.

Is there any option to set the Labeltext for the Inputfields?

Share this post


Link to post
Share on other sites

It would be great if the wireMail function could be used for sending emails instead of the php mail function.

This way people would be able to use it together with their favourite mail extensions. For example with SMTP support: wiremail-swiftmailer or wiremailsmtp

  • Like 5

Share this post


Link to post
Share on other sites

@makari: This module creates a simple template, you can / should change the html structure as well as the label texts. If you need multi language support you have to change the text like this echo __("the label text here!"). Now you can translate the labels via Processwire Backend.

@horst: Thats a good point but first I have to finish another project. I will keep it in mind – as some other things (I did not forget your message  ;) ).

  • Like 2

Share this post


Link to post
Share on other sites

Hey there,

I've installed this module. It has created a new template simple_contact_form.php

I've created a page and used simple_contact_form.php as its template

So I see the contact form on the new page, but it doesn't seem to work (I've used my @gmail.com as emailTo)

is there anything else I should do to make it work?

Share this post


Link to post
Share on other sites
but it doesn't seem to work (I've used my @gmail.com as emailTo)

Gmail doesn't allow you to send an email from yourself to yourself, unlike other email platforms.  The message gets sent but you don't receive the copy, since if's from yourself.

Share this post


Link to post
Share on other sites

I didn't try to send an e-mail to myself?

I have sent @gmail e-mail in the module settings and was testing it on the site using another e-mail, but nothing much happens there..

Share this post


Link to post
Share on other sites

Ok, then I would then look at the php mail function on your server.  I believe this module doesn't make use of enhanced PW capabilities for email sending.

It would be great if the wireMail function could be used for sending emails instead of the php mail function.
 
This way people would be able to use it together with their favourite mail extensions. For example with SMTP support: wiremail-swiftmailer or wiremailsmtp

Share this post


Link to post
Share on other sites

The module uses now the WireMail function instead of php mail.

Besides I added the tag "scf" for fields and templates created by this module (just available on a new installation).

  • Like 5

Share this post


Link to post
Share on other sites

Hi,

Just experienced a couple of bugs with this module which happen when the save messages setting is off.

SimpleContactForm.module

First bug:

if (!$this->pages->findOne('name=' . $this->pageName) instanceof Pages) {

I believe this should be without the "!" at the start as it is currently the wrong way around. Removing it fixed it for me.

Next bug:

} elseif (!in_array($currentIp, $excludeIps)) {

This line should also check if the saveMessages setting is on, i.e.:

} elseif (!in_array($currentIp, $excludeIps) && $this->saveMessages) {

I haven't tested any of these with other settings and I'm not sure they are correct - just needs some looking into.

  • Like 1

Share this post


Link to post
Share on other sites

@pwired:

@makari: This module creates a simple template, you can / should change the html structure as well as the label texts. If you need multi language support you have to change the text like this echo __("the label text here!"). Now you can translate the labels via Processwire Backend.

@BrettMW: Indeed, I only tested this at the beginning with save message settings deactivated. Thanks for your feedback, I will test and implement this as soon as possible. 

Share this post


Link to post
Share on other sites

New version 0.0.9 includes fixes for deactivated save message setting.

On line :343 I removed the exclamation mark (!) and I corrected the instance to compare with. This has to be Page instead of Pages because findOne returns a single page (because of this double bug the messages has been stored). I included a second check here just to make sure that save messages is on. I also included this additional check on line :396. 

  • Like 3

Share this post


Link to post
Share on other sites

New version 0.1.0 adds some more spam protection possibilities and logging.

  • CSRF validation
  • mark messages as spam (by mail or/and ip address)
  • logging for received messages and spam
  • sort option for repeater items in backend to get the latest to the beginning of the list

For more information have a look at the readme.

NOTICE: If you upgrade an existing installation from 0.0.9 and below to the current version, there are some steps to be taken.

  • 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 blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/