justb3a

Simple Contact Form

224 posts in this topic

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.

2 people like this

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

1 person likes this

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  ;)

5 people like this

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. 

1 person likes this

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

1 person likes this

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.

1 person likes this

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);
1 person likes this

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 bernhard
      Hi,
      just stumbled over a little module that i built for my last project. it helped me to test performance of my rockdatatables module to generate 3000 random json datasets and i want to share it with you. maybe it saves some time for someone.
      https://gitlab.com/baumrock/RockDummyData/
      easy example:
      $rdd = $modules->get('RockDummyData'); for($i=0; $i<15; $i++) { // this has to be inside the for-loop to always get a new dummy $dummy = $rdd->getDummy(); echo date("d.m.Y H:i:s", $dummy->timestamp) . "<br>"; } more advanced:
      $json = new stdClass(); $json->data = array(); $rdd = $modules->get('RockDummyData'); for($i=0; $i<3000; $i++) { // this has to be inside the for-loop to always get a new dummy $dummy = $rdd->getDummy(); $obj = new stdClass(); $obj->name = $dummy->forename . ' ' . $dummy->surname; $obj->position = $dummy->job; $obj->office = $dummy->city; $obj->color = $dummy->color; $obj->start_date = new stdClass(); $obj->start_date->display = date('d.m.Y',$dummy->timestamp); $obj->start_date->sort = $dummy->timestamp; $obj->salary = rand(0,10000); $json->data[] = $obj; } echo json_encode($json); you have to store your random datasets on your own into the /data folder. there are several services for creating all kinds of random data on the web - if you know one service that allows sharing those datasets let me know and i can include common needed data into the module
    • By AndySh
      Hello!
      I need your assistance please. I purchased the module FormBuilder. Unfortunately, the module discontinued delivering customer submissions to e-mail box specified in the module settings. Direct mailing to the e-mail box works OK. The module settings stays the same and are correct, like "Send e-mail to administrator(s) is checked. The last version of FormBuilder 3.0 has been installed. Please advise how to resolve the issue becase I cannot get orders from customers anymore (((
    • By kixe
      As described in this post (https://processwire.com/talk/topic/8551-custom-urls-for-pages/?p=82742) the option 'Name Format Children' under the tab 'Family' in template settings doesn't work properly and also not as expected. I had a look inside the code and made some changes which are working properly, which offers much more options, more consistency and less code too.

      The result is the following. You have 3 Options for generating name and title, which could be combined in endless variations.
      Name is always derived from title, same like creating pages manually.
      type date: if function detects # character anywhere in the string, conversion will be: deletion of # and string will be used as format parameter for PHP date() function type field: if string is a fieldname of the parent page the value of this field will be used type string: if string doesn't fit to the 2 preceeding it will be taken as it is All parts (separated by comma) will be composed in the order of setting. You can use unlimited numbers of parts

      I made a pull request on github: https://github.com/ryancramerdesign/ProcessWire/pull/831

      Example screenshots

      Setting ...


      will result in


       
    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
       
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend