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

good call, got this: Number of fields does not match

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 Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • 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://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      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/
    • By blynx
      Hej,
      A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated
      (Also pull requests are appreciated 😉 - have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

      Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe
      .zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip
      You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:
      <?php $pwpswp = $modules->get('Pwpswp'); echo $pwpswp->renderGallery($page->nicePictures); Options are provided like so:
      <?php $galleryOptions = [ 'imageResizerOptions' => [ 'size' => '500x500' 'quality' => 70, 'upscaling' => false, 'cropping' => false ], 'loresResizerOptions' => [ 'size' => '500x500' 'quality' => 20, 'upscaling' => false, 'cropping' => false ], 'pswpOptions' => (object) [ 'shareEl' => false, 'indexIndicatorSep' => ' von ', 'closeOnScroll' => false ] ]; echo $pswp->renderGallery($page->images, $galleryOptions); More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe
      What do you think? Any ideas, bugs, critique, requests?
      cheers
      Steffen