justb3a

Simple Contact Form

224 posts in this topic

Never! change anything in the module code!

Just go to module settings (Admin > modules > SimpleContactForm > Edit) and add there the fields. Click submit, reload the form, you will see the new fields appended.

Please have a look at the documentation!

post-2759-0-15114000-1440412681_thumb.pn

Share this post


Link to post
Share on other sites

I'm having some troubles with the form. 

I've setup everything on my localhost and every thing seems to be working fine. Then i've copied everything to my server and for some reason the form stopped working. 

When I fill in all the field i get an error: 'Please verify the data you have entered.' even though everything looks fine. The weird part is that is doesn't say anything in the Logfile. 

Do you have any idea what the problem could be?

Share this post


Link to post
Share on other sites

Thankyou for building out this form. I was trying to setup the plugin, but everytime I remove a field name I get the following error: 

Error: Call to a member function save() on null (line 1098 of /home/marmil113/marshhospital.com/site/modules/simplecontactform/SimpleContactForm.module)

Any idea what I can do?

Share this post


Link to post
Share on other sites

@carlos: I guess there is something broken with your database because the fieldgroup failed to save after removing a field. Is this a production installation? If not, I would recommend to deinstall this module and check the clear data option (please do a backup before). After that have a look at your database and clear all stuff generated by this module if there’s something left. If the deinstallation with the clean option fails, you have to do this manually.

I tested it again and everything is working as expected. 

Share this post


Link to post
Share on other sites

I've been playing around with simple contact form and it works great!

I'm pretty new to all this, i'm trying to send the form using ajax ( thats so the page doesn't refresh right? ), iv'e included jquery.simplecontactform.js using 

   <script src="<?php echo $config->urls->templates?>scripts/jquery.simplecontactform.js"></script>

on my main page.

but what do i do with 

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

$.simplecontactform($('.js-simplecontactform'));
}

iv'e tried adding it to my main page using <script> and also tried <?php> neither works.

Also is there a way to style the send confirmation text?

heres some examples of what i've done so far.

http://ianjburgess.com/screenshot/Screen%20Shot%202015-10-14%20at%202.40.10%20PM.png

http://ianjburgess.com/screenshot/Screen%20Shot%202015-10-14%20at%202.40.59%20PM.png

Share this post


Link to post
Share on other sites

@Mido: Not the best but simplest solution:

  •  include jQuery
  •  include SimpleContactForm script
  •  include a general js file (main.js for example) which contains the function call you mentioned above

To style the confirmation text, modify the template, add a class and add CSS for that class.

Share this post


Link to post
Share on other sites

Hey

I really like this module and got it working quite well. There's only a few issues which I've encountered. Some mails are being sent directly and other need a wait time of maybe 30 minutes to be send to the email I've set in the settings. I've excluded my IP for the spam option yet it takes a long time for some messages to get through. Any idea what triggers this?

In the /scf-messages/ I can still see all the messages right away after they have been accepted by the system.  Could it still have something to do with the spam filter?

edit: Tried another IP too, still waiting for the mail...

edit 2: Last received mail took 2h to arrive

edit 3: Now they seem to come straight away... weird...

Share this post


Link to post
Share on other sites

hi,

I'm quite sure that this behaviour is not related to this module. The spam filter only checks some stuff and if everything is fine it hands the mail over to the mail agent and saves the message. Have a look at your mail log, maybe there is a queue. If the message was saved successfully, the spam checks are passed without any problem.

Share this post


Link to post
Share on other sites

Thanks @justb3a for your module, I am finally getting to use it :)

TL;DR

Is there something I need to configure in SCF to ensure it uses the WireMailSMTP module to send mail rather than in-built/default methods in PW? Thanks for any comments.

Background

I would like to sent mail via Mandrill and so as I have in the past with the PW Forms module I have installed WiremailSMPT; I noticed you said SCF now supports WireMail. I assumed that this meant when email was sent from the SCF if WireMailSMTP was installed it would automatically go via that module (and it's settings (Mandrill in my case)), but so far I am finding emails are arriving AOK but not via the WireMailSMTP module (as Mandrill is not listed in the route).

Share this post


Link to post
Share on other sites

I began editing simple_contact_form.php and found I was getting [FAILURE] CSRF Token validation failed. I back-tracked and found that, apparently, reindenting the code of the original form file with a Sublime Text plugin caused the errors..? I tried to diff the original versus the reindented one but as far as I could see nothing was 'wrong', just differently indented.

No time now to do stuff like try an alt diff tool in case the first missed something, but I thought I'd share in case this helps anyone else.

@justb3a if a copy of the indented-and-broken code would be helpful just let me know and I'll publish it on Dropbox or similar.

Share this post


Link to post
Share on other sites

@alan: Did you check that CSRF token validation works? If you load the form (frontend) there should be a hidden input containing a generated name and value:

<input type="hidden" id="_post_token" name="TOKEN1234567891X1234567891" value="A1B2c3d4efgHIj5klLmno6pQrstUVwxy" />

As said above, the name and value are generated, make sure it's not hardcoded. Also have a look at your log file (simplecontactform-log), all errors are displayed there.

I've never used WireMailSMTP – if you've figured out how to use it, please let me know!  ;)

1 person likes this

Share this post


Link to post
Share on other sites

@all Right now all is good and I am just trying to work out how to have SCF use WireMailSMTP rather than native PW transport.

It uses it out of the box, mean: you haven't to do anything in regard of SCF. SCF uses wiremail(), - and if you have installed and setup wiremailSMTP, it is used instead of the basic wiremail, which uses the PHP mail function.

1 person likes this

Share this post


Link to post
Share on other sites

@justb3a Thanks, yes the token is there and since I undid the reindenting of code it works AOK. Also thanks I have used the log to see what was wrong (very helpful, I also spotted that my test emails had hit the IP address limit per day so I upped it for testing :)

@horst Thanks, yes I assumed that it was used. But I am pretty sure it's not being used...

History: I installed and used SCF to send email (via PW built in wiremail I assume). Then I installed WireMailSMTP and set it to use my Mandrill credentials.

But email is arriving without showing Mandrill as the sender (view email headers also shows no mention of Mandrill.com) and based on all my other uses of WiremailSMTP+Mandrill I assume (where Mandrill is listed) I assume this mean Mandrill and therefore WireMailSMTP are being bypassed (I guess?).

Env: • WireMailSMTP passes it's connectivity test. • I have debug turned on.

If there's anything I can do to help test what may be happening I'd be happy to test and report.

Thanks in advance for any suggestions.

1 person likes this

Share this post


Link to post
Share on other sites

I use it on one site with wiremailSMTP and it works. But I haven't used it together with Mandrill.

I think you use a recent or latest version of SCF? (earlier version hasn't supported wiremail())

You may check in the headers of your emails for the User-Agent, e.g. ProcessWire/WireMail or ProcessWire/WireMailSMTP or ...

1 person likes this

Share this post


Link to post
Share on other sites

@horst Thanks for the suggestions, I will check and report back in case it's of any help to others.

1 person likes this

Share this post


Link to post
Share on other sites

@horst I checked and

  • SCF is 0.1.2 which is the latest at the moment = ✔
  • header says "...X-Mailer: ProcessWire/WireMail..." = ✖

so my setup (WireMailSMTP ver 0.1.13 on a PW 2.7.0 site and SCF) seems to be working AOK but emails are bypassing WireMailSMTP :'(

@justb3a and/or @horst : if there is anything I could do here to help fix this for me (and I assume others) then I would be happy to try stuff and report back/thanks for any suggestions you may have :)

1 person likes this

Share this post


Link to post
Share on other sites

Fixed the problem where WireMailSMTP is being bypassed in favour of WireMail...

@justb3a I would usually leave module code 100% alone, but comparing how mail is called in another site I noticed it was different, so I edited `SimpleContactForm.module` around line 478 like this: 

// Below original module code bypasses WireMailSMTP
// $wireMail = new WireMail();

// Below does not bypass WireMailSMTP
$wireMail = wireMail();

and email is then sent via WireMailSMTP. If I edit it back to the original then it bypasses WireMailSMTP and I can switch back and forth depending on how I leave the code around line 478.

If this is this something you would like me to log on git etc then please let me know as I would love to have an official (unedited) copy of your excellent module that used WireMailSMTP.

Sorry if I explained that all badly and thanks again for this module, cheers, -Alan

3 people like this

Share this post


Link to post
Share on other sites

@alan: WOW! What a great find.  ^-^  You are right. I have checked this and yes, on the site I thought it would working together, it also bypasses SMTP as you described it.

@justb3a: please can you fix this with one of the next releases?

1 person likes this

Share this post


Link to post
Share on other sites

Thanks for the fix @justb3a and glad this helped your site also @horst ^_^

1 person likes this

Share this post


Link to post
Share on other sites

new version 0.2.0 brings in some new features:


  • supports multiple instances
  • allows usage of full ProcessWire API in options
  • allows to render more than one contact form on a page
  • allows to send more than one email
  • makes validation hookable
  • read on
4 people like this

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 Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      A module for ProcessWire CMS/CMF. Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.

      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Advanced: define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
    • By joshuag
      Introducing our newest [commercial] module:
      Recurme
      Processwire Recurring Dates Field & Custom Calendar Module.
      http://www.99lime.com/modules/recurme/
      One Field to Recur them ALL…
      A Recurring Dates InputField for your Processwire templates. The InputField you’ve been waiting for.
      Complex RRule date repeating in a simple and fast user interface.
      Use the super simple, & powerful API to output them into your templates.
      example:
      <? // easy to get recurring events $events = $recurme->find(); // events for this day $events = $recurme->day(); // events for this week $events = $recurme->week(); // events for this month $events = $recurme->month(); ?> <? // Loop through your events foreach($events as $event){ echo $event->title; echo $event->start_date; echo $event->rrule; echo $event->original->url; ... } ?> Unlimited Custom Calendars.
      Imagine you could create any calendar you wanted on your website. Use recurring events with the Recurme field, or use your own Processwire pages and date fields to render calendars… it’s up to you. Fully customizable. Make as many calendars as you like. Get events from anywhere. Recurme does all the hard date work for you.
      Unlimited Custom Admin Calendars too.
      Hope you like it  ,
       Joshua & Eduardo from 99Lime.
       




    • By valan
      At our site we use both email and phone authorizations at frontend. To make life easier, I've developed HelperPhone pack that handles phone numbers. This pack includes following modules for ProcessWire CMS/CMF:
      FieldtypePhoneNumber: module that stores phone numbers InputfieldPhoneNumber: module that renders inputfield for phone numbers HelperPhone: module that loads PhoneNumber and PhoneNumberConst classes, and 'libphonenumber' namespace All these modules require included PW WireData-derived class PhoneNumber and PhoneNumberConst.
      PhoneNumber class is a thin wrapper over giggsey/libphonenumber-for-php, itself is port of Google's libphonenumber. PhoneNumberConst class stores constants, used by PhoneNumber class Usage: PhoneNumber class
      $phone = '8 (916) 318-07-29 ext 1234'; // input string could be in any phone-recognizable format $phoneNumber = new PhoneNumber($phone, 'RU'); // or wire('modules')->get('HelperPhone')->makePhoneNumber($phone, 'RU'); echo ($phoneNumber->isValidNumber() ? 'Yes':'No'); // Yes echo ($phoneNumber->isValidNumberForRegion($regionCode) ? 'Yes':'No'); // Yes echo $phoneNumber->getNumberTypeTitle(); // Mobile echo $phoneNumber->getCountryCode(); // 7 echo $phoneNumber->getRegionCode(); // RU echo $phoneNumber->getNationalNumber(); // 9163180729 echo $phoneNumber->getExtension(); // 1234 echo $phoneNumber->formatForCallingFrom('US') // 011 7 916 318-07-28 echo $phoneNumber->formatForCallingFrom('GE') // 00 7 916 318-07-28
      For more methods and properties please refer to PhoneNumber and PhoneNumberConst source files. Need more? Check giggsey/libphonenumber-for-php and use it by accessing $phoneNumber->phoneNumber property - it is instance of \libphonenumber\PhoneNumber or null (if empty).
      Usage: field
      Note: on field creation, make sure that you've configured field settings
      Default region: assumed region if input phone number string is not in international format (starts with '+', etc)
      Enabled/disabled phone extentions: if disabled, phone extension will be removed on field save.
      Phone field settings in example below: default region code 'RU', phone extensions are enabled
      echo $page->phone; // +79163180729 // Note1: $page->phone stores instance of PhoneNumber and renders to string in E164 format. // Note2: E164 format does not include extension. echo $page->getFormatted('phone'); // +7 916 318-07-29 ext. 1234 echo $page->getUnformatted('phone'); // +79163180729 echo $page->phone->format(PhoneNumberConst::RFC3966); // tel:+7-916-318-07-29;ext=1234 echo $page->phone->getNationalNumber(); // 9163180729 Usage: PW selectors
      FieldtypePhoneNumber is instance of FieldtypeText. It stores phone numbers and extensions as string in E164 format with #extention (if provided by user and enabled in settings) E.g. in db it looks like this: '+79163180729#1234'. This makes it easy to query fields as any text field.
      echo $pages->find([     'template' => 'my_temlate',     'phone^=' => '+79163180729', ]); // will echo page ids where phone starts with '+79163180729' Finally
      I've decided to put it here first and later to Modules directory (based on your feedbacks).
      GitHub: https://github.com/valieand/HelperPhone
      Enjoy
    • By justb3a
      Little admin helper module: Using this module you can view all template cache settings at once. E.g. cache status, cache time (configurable). Furthermore it adds the functionality to clear the entire template cache or just the template cache for a given template. Note that this may cause a temporary delay for one or more requests while pages are re-cached.

       
      GitHub: https://github.com/justb3a/processwire-templatecacheoverview
    • By Steven Veerbeek
      Hi,
      I am trying to create a module for a webshop in which I can predefine a number of thumbnail sizes for my product images. I was thinking of storing each of these image sizes as a child page with 'width' and 'height' fields under the module page , so I can use a PageTable input field in my module to easily manage them.
      I know how to create a Pagetable field and add it to templates so I can use it in regular pages, but because I am planning on implementing some other functionalities that (I think) can't be achieved with a regular page, I need the PageTable field to work within a module.
      So far I have come up with this piece of code by trial and error:
      $page = $this->page; $field_sizes = $this->modules->get("InputfieldPageTable"); $field_sizes->title = "image_sizes"; $field_sizes->label = "Image sizes"; $field_sizes->set('parent_id', $page->id); $template = wire("templates")->get("image_size"); $field_sizes->set('template_id', $template->id); $field_sizes->set('columns', "title\nimage_width\nimage_height"); $wrapper->add($field_sizes); It works in that it does display an empty PageTable in my module. I can also add pages and they will be added as child pages under my module page, but when I do, the way the PageTable is displayed gets all messed up. Instead of showing the newly created page as a row in the PageTable, all the fields on the module page (including the PageTable field itself) are repeated within the PageTable field.
      I hope my explanation makes sense. I am fairly new to Processwire (and module development in particular) so perhaps I am just trying to use PageTable in a way it was not intended to be. Maybe you guys could give me some directions on how to achieve what I am looking for?
      Thanks!