justb3a

Simple Contact Form

Recommended Posts

Hello justb3a,

at the moment I try to build my first website with processwire and so I need a simple contactform.

I found your module and it works fine. But I have a problem to fit the module to my bootstrap form.

Can you explain me (i'm a beginner) how i can realize this. This would be wonderful.

Thanks and many greetings from Berlin

Share this post


Link to post
Share on other sites

hello gebeer,

thank you for your response.

I tried to change it, but in the moment it is not so easy for me. To many new things I have to learn.

Maybe you can help me.

I tried to put the class: col-sm-8 to an input field. How can I do this? Changing the "item_content" in the class-array didn't work. 

 

   Webbrowser:  <input id="Inputfield_scf_email" class=" required" name="scf_email" type="text" size="60">

Maybe you have an example for a correct array?

 

Many Greetings

Lena

Share this post


Link to post
Share on other sites

Hi,

it seems that `item_content` only apply to inputfields of type InputfieldWrapper and InputfieldPage. 

If you use something like `_init.php` you can add a hook there:

$this->addHookBefore('Inputfield::render', function(HookEvent $event) {
  if ($this->page->template->name === 'contact') { // adapt template name to compare with
    $inputfield = $event->object;
    $inputfield->addClass('col-sm-8');
    $event->return = $inputfield;
  }
});

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi all!

This module works great and I don't have any errors. I was just wondering if there is any option to send an e-mail with the data filled in the form in a template. So you receive at the end an e-mail with a logo and maybe more adjustments. Or should I add the logo in the module file to the message and maybe style it there too?

-EDIT-

My contractor haves an alias of a gmail account. So the e-mail adres looks like name@companyname.com but it is from google. Now I want to send the emails to that email address, but he receives nothing. Also not in the spambox. Is it possible that this doesn't work because the emailadress is an alias or is it something else? 

To present more information, the website I am currently working on was a few years ago moved from a hosting service to another hosting company. Now I noticed that the email in the current hosting application has the wrong records, but the e-mailadresses are still working and don't experience any problems, except for not receiving the contact form e-mail.

Does anyone know how this is possible, is it because the records are wrong (but emailaddressess still work fine) or is it a bug in the module?

Thanks in advance,

~Harmen

Edited by Harmen
Additional errors

Share this post


Link to post
Share on other sites
12 hours ago, ank said:

Hello

is there a way to make some fields required ?

Sure, you only have to check the required checkbox in the field settings.

required.png

  • Like 1

Share this post


Link to post
Share on other sites

justb3a, thanks for such a lovely script! :-)

This works perfectly with SimpleContactForm 1.0.0 on Processwire 3.0.42

<?php $scf = $modules->get('SimpleContactForm'); 
    $options = array(
	'btnClass' => 'button fit big',
	'btnText' => 'SEND MESSAGE!',
	'successMessage'  => 'Message Sent!',
	'errorMessage'  => 'Sorry - message send error!'
);
echo $scf->render($options); ?>

But if you just use this (without specifiying the successmessage) e.g.

<?php $scf = $modules->get('SimpleContactForm'); 
$options = array(
	'btnClass' => 'button fit big',
	'btnText' => 'SEND MESSAGE!'
);
echo $scf->render($options); ?>

The form processes (send) correctly, but the form output on the web page after sending is shown as:

<p class='form--success--message'>SEND MESSAGE!</p>

Showing the 'btnText', rather than the correct 'default success message'.

Have I missed someting obvious?

I've posted just incase anyone else is having the same issues.

  • Like 1

Share this post


Link to post
Share on other sites

For some sites the "spam message" might not be approprate :lol:

So I changed line 215 in SimpleContactForm.module to

            $this->_("Sorry, but your message didn't pass our %s test. Please try another %s."),

and change lines 155 (& the following) & 172 (& the following) in \lib\SpamProtection.php to

      $this->_('spam'),

and

      $this->_('time'),

 

So the message will read " Sorry, but your message didn't pass our spam test. Please try another time. "

Thanks again @justb3a

Share this post


Link to post
Share on other sites

@dab It's not that good idea to change something inside a third-party module (or, even worse, in the core). If you update the module, all your changes get lost.
I would suggest translating the values  – which will be inserted – with 'spam' and 'time'. You could also translate "Sorry, but your message didn't pass our %s test. Please try another %s." with "Sorry, but your message didn't pass our spam test. Please try another time.". Therefore I made them translatable. ^_^

  • Like 1

Share this post


Link to post
Share on other sites

Hello, Im having some problems with simple contact form styling. I tried everything but just don't get it. I went throu THIS pages but can't figure it out what should I actually do to make it the way I want. I tried and played with this but no success. Im not a coder but understand some ...

My HTML looks like this:
 


	<form action="#" method="post">
		<div class="input-field">
			<input type="text" name="name" class="form-control" placeholder="Your Name...">
		</div>
		<div class="input-field">
			<input type="email" name="email" class="form-control" placeholder="Your Email...">
		</div>
		<div class="input-field">
			<input type="text" name="Phone" class="form-control" placeholder="Phone Number...">
		</div>
		<div class="input-field">
			<textarea name="message" class="form-control" placeholder="Messages..."></textarea>
		</div>
		<button type="submit" id="submit" class="btn btn-blue btn-effect">Send</button>
	</form>

Any help is appreciated.

Thank you

R

Share this post


Link to post
Share on other sites

hi roych,

you should be as clear as possible in your questions. you don't explain what the problem is. you could add screenshots how it is and how it should be. styling is usually done via CSS. answers depend a lot on your setup...

  • Like 1

Share this post


Link to post
Share on other sites

Sorry for not being clear enough. I would like to style my form created in  SimpleContactForm module. But I can't figure it out how from those instructions. Where and how should I change classes in my code.

expl.

My code for showing a form now, looks like this. 

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

this is giving me some basic style from PW. How do I change those styles so it would look like the form posted in first post?

I tried and played with this

$scf = $modules->get('SimpleContactForm');

$options = array(
  'markup' => array(
    'list' => "<div {attrs}>{out}</div>",
    'item' => "<p {attrs}>{out}</p>"
  ),
  'classes' => array(
    'form' => 'form form__whatever',
    'list' => 'list-item'
  )
);

echo $scf->render($options);

but can't figure it out how this should work. There is no changes no mather what I do ...  And where is the Style for submit button etc.?

I hope I was more clear this time.

Thank you

R

Edited by kongondo
Your question is about module that has its own support forum. I have moved your thread to that support forum.

Share this post


Link to post
Share on other sites

Hi,

I've migrated a Processwire site that was running on PW 2.6.1 with SCF 0.1.1 to a new installation of PW 3.0.42 and after I install SCF 1.0.0 I'm getting the following error which breaks the admin:

 

Error: [] operator not supported for strings (line 131 of ...\site\modules\Processwire-SimpleContactForm\SimpleContactForm.module)

Line 131 of that file is ->     foreach (self::$additionalFields as $f) $allFieldsExtended[] = $f;

 

When I remove the [] from that line (which I don't suspect for a second is an actual fix, but at least makes the admin functional again) the module shows as installed and all of my previously created fields appear in red on the settings screen under "Select form fields". Is there something I need to do to those old fields? There's mention of upgrade notes on the first page of the thread here but none of the links work.

Share this post


Link to post
Share on other sites

I haven't used this module, so not sure about those red fields, but I think the likely correct fix for the operator not supported issue is to to define $allfields in the additional fields at around line 65.

protected $allFields = array();

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, Adrian. That got rid of the error message.

Unfortunately, it seems that a lot of functionality's been lost and with the gaping documentation gaps this isn't going to work for me.

Share this post


Link to post
Share on other sites

Why its not working?

Email is displayed as not valid, but it is. Turn yellow -> not sending...

How to turn off website and date? I hide it per css buts dirty…

using 1.0

tom

 

Share this post


Link to post
Share on other sites

I can't figure the [FAILURE] Number of fields does not match issue at all.

I have 5 fields:-

  • scf_firstname
  • scf_surname
  • scf_email
  • scf_company
  • scf_enquiry

PW ver. 3.0.33

SCF ver. 1.0.0

Any help greatly appreciated.

Share this post


Link to post
Share on other sites

@Roych

Try this:

$scf = $modules->get('SimpleContactForm');

$options = array(
  'btnClass' => 'btn btn-blue btn-effect',
  'btnText' => 'Send',
  'classes' => array(
    'item' => 'input-field'
  )
);

$content .= $scf->render($options);

You need to set the placeholder in the field settings, go to Admin > Setup > Fields > Edit Field: xxx > Tab Input > Placeholder Text.
It's recommended to hide the label using css (label { display: none; }). People which have to use screen readers will reward you ^_^

Unfortunately it's not that easy to add the class form-control to every input field. There is no way to set it globally.
I would suggest using css to achieve what you want:

.input-field input,
.input-field textarea,
.input-field select {
  // your styling goes here
}

Otherwise you have to hook into every render function for every fieldtype you use and pass the class inside the getAttributesString function

 

Share this post


Link to post
Share on other sites

@alexmercenary I found a little bug: The module uses a imaginary field named 'date'. Normally there is no 'date' field (naive assumption, I know) and everything works as expected. But if you create a field named 'date' for something else, the condition matches and the form has one more field than desired. The same counted for a field named 'ip'. I just released a new version 1.0.1. Please try if it's working now.

@Tom Walcher

On 24/02/2017 at 7:01 PM, Tom Walcher said:

Email is displayed as not valid, but it is. Turn yellow -> not sending...

How to turn off website and date? I hide it per css buts dirty…

The form just validates every field how it is configured in the field settings. If you want to have email validation, set the field type to email. If you want a field to be required, just check the corresponding checkbox in the field settings. Same counts for html5 validation.

Hiding the website and date field via CSS is not dirty. The website field is already of type hidden, so you just have to hide the corresponding label. The website field is intentional not hidden. It's a trap for spambot. Have a look at the documentation.

 

  • Like 1

Share this post


Link to post
Share on other sites
On 23/02/2017 at 3:40 AM, adrian said:

I haven't used this module, so not sure about those red fields, but I think the likely correct fix for the operator not supported issue is to to define $allfields in the additional fields at around line 65.


protected $allFields = array();

 

I would not recommend doing this. 'allfields' is already declared in the moduleConfig file. If you set it in the module file again, this value will be overwritten and if you render the form all fields are gone. ^_^

@Arcturus

On 23/02/2017 at 6:01 PM, Arcturus said:

Unfortunately, it seems that a lot of functionality's been lost and with the gaping documentation gaps this isn't going to work for me.

Feel free to optimise the documentation! Fixes and suggestions are very welcome!
A lot has been changed since version 0.1.1. I think, this is the page you were looking for, but this is no longer relevant. Because the module now renders the form by itself and no template adaptions are needed any longer. Did you try to render the form (frontend)? If not, please do so. There are some migration functions in the module. If you still want to use this module, please post the input of the column data from table modules where column 'class' equals SimpleContactForm. Furthermore some additional informations would be really good (save messages enabled? fields which should be added, ..).

  • Like 1

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.