Jump to content
justb3a

Simple Contact Form

Recommended Posts

Thank you very much for the quick reply!

#1 Ok, I'll do that.

#2 'action' => './#anchor' does work indeed, I should have thought of this.

BTW, I've just noticed a typo in the success message: "Your contact request has been send successfully!" => sent

Thanks for the great module! Maybe it should be renamed to Highly Customizable Contact Form ;):)

Share this post


Link to post
Share on other sites
36 minutes ago, justb3a said:

$emailMessage = file_get_contens('path/to/message.php'); // or include partial etc.
$modules->get('SimpleContactForm')->render($array('emailMessage' => $emailMessage));

I tried this, but I must be missing something here as the content of message.php is not interpreted by PHP but it is sent as a string literal, so I cannot get it to work :( What am I doing wrong?

Share this post


Link to post
Share on other sites

Using twig the following does work:

{% set emailMessage %}{% include 'mails/recommend.twig' %}{% endset %}
{% set options = {
  'action': './#recommend',
  'emailMessage': emailMessage
} %}
{{modules.get('SimpleContactForm').render(options)}}
{# recommend.twig #}
...
{{ estate.title }}
{{ page.httpUrl }}
{% if input.scf_salutation == 1 %}xx{% elseif input.scf_salutation == 2 %}xx{% else %}xx{% endif %}
...

I thought using php should work the same.

Share this post


Link to post
Share on other sites

I do not use twig, just plain php. In my message.php file if I have this for example:

<?php namespace ProcessWire;
echo "You have received a new contact form message";

That is what is sent, not just:
You have received a new contact form message

Actually this is what I expect, since file_get_contents simply reads the file, so I have the string, that's okay, but how is it going to be interpreted?

Edited by szabesz
typo

Share this post


Link to post
Share on other sites

1)

$emailMessage = $page->title . ' test';
$content .= $modules->get('SimpleContactForm')->render(array('emailMessage' => $emailMessage));

2)

include('./mess.php');
$content .= $modules->get('SimpleContactForm')->render(array('emailMessage' => $emailMessage));

// mess.php
<?php namespace ProcessWire;

$emailMessage = $page->title . ' test2 ' . $input->post->fieldname;

Share this post


Link to post
Share on other sites

or 3)

ob_start();
include('./mess.php');
$emailMessage = ob_get_clean();
$content .= $modules->get('SimpleContactForm')->render(array('emailMessage' => $emailMessage));

// mess.php
<?php namespace ProcessWire;
echo $page->title . ' test3 ' . $input->post->headline;

 

Share this post


Link to post
Share on other sites

Thank you! I'm testing them, and 1) obviously works, let's see the other two. I'll be back :)

Share this post


Link to post
Share on other sites

I tested 1), 2) and 3).  They work all. :)

If you want to use file_get_contents, you need to pass an URL returning the content. Otherwise the code won't be interpreted.

Stackoverflow:

Quote

I suppose you want to get the content generated by PHP, if so use:

$Vdata = file_get_contents('http://YOUR_HOST/YOUR/FILE.php');

Otherwise if you want to get the source code of the PHP file, it's the same as a .txt file:

$Vdata = file_get_contents('path/to/YOUR/FILE.php');

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, szabesz said:

BTW, I've just noticed a typo in the success message: "Your contact request has been send successfully!" => sent

I fixed the typo, thanks for the hint.

The translation string has been changed, some may need to translate it again!
 

1 hour ago, szabesz said:

Thanks for the great module! Maybe it should be renamed to Highly Customizable Contact Form ;):)

It started pretty simple (for private use only). Then I did the "mistake" to put it on Github :lol:. But if you don't need something special, I think/hope it's still pretty easy.

  • Like 1

Share this post


Link to post
Share on other sites
29 minutes ago, justb3a said:

I tested 1), 2) and 3).  They work all. :)

Yes they do, however 3) with output buffering resulted in:

scf_enquirytype: 1
scf_name: Szabesz
Date: 2017-05-14 09:18:47

and I did not get my message. However, simple include works for me as expected. Here it is for reference if anyone is interested in getting the title of a selected Select Options Fieldtype:

<?php namespace ProcessWire;

// as per https://processwire.com/api/modules/select-options-fieldtype/#manipulating-options-on-a-page-from-the-api
// scf_enquirytype is a Select Options Fieldtype
$field = $fields->get('scf_enquirytype');
$all_options = $field->type->getOptions($field);

// $enquirytype stores the ID of the option selected
$enquirytype = $input->post->scf_enquirytype * 1;

$emailMessage = $enquirytype . "\n\n";
// WireArray is 0 indexed, while Select Options Fieldtype starts at 1, we account for this:
$emailMessage .= $all_options->eq($enquirytype - 1)->title . "\n";

BTW, thanks for the file_get_contents explanation, I've never used it instead on include, today I've learnt a few things again :)

  • Like 1

Share this post


Link to post
Share on other sites

I installed this module but it stays dead by all means.

First I installed it via the Modules interface in Processwire. Only two fields 'scf_name' and 'scf_email_adress' showed up in my Fields list. On the form also 'scf_website' appeared. Filling out a form gave an error message, probably because there was no message content. That went away when I entered a default text in the module interface. But no way to add the supposed fields. So I deleted the module via Processwire and removed the folder from my server.

Then I grabbed the zip file from Github and uploaded it to my server. This time no fields were created at all. I added an existing one in the module interface. It shows up alright, but no others except the dreaded 'scf_website' shows up – although it doesn't show up in my Fields list.

I'm using Processwire 3.0.62. Contact form is here amvk.be/contact/

Share this post


Link to post
Share on other sites

@BFD Calendar Could you please explain what you did exactly? It doesn't matter whether the module is installed via ProcessWire Module Interface or via Github (unless you checkout develop branch). As the documentation says, the scf_website field is used as honey pot check to prevent spam. In module settings you could add any existing field or create new ones by entering the names (comma-separated). Per default no fields are added, because I do not know which fields you need ;) Furthermore: please have a look at the log file. If the form cannot be submitted, the reason will be found there.

  • Like 1

Share this post


Link to post
Share on other sites

@justb3a Ok, this makes things easier, guess I read some old documentation. I suppose you sent a form from city: whereever, that arrived.

But anyway, the scf_website field is still there.... and the other ones I added show up, but now the contact form doesn't pass the test. [FAILURE] Number of fields does not match.

And then I still haven't figured out how to format the fields on the form....

Share this post


Link to post
Share on other sites
1 minute ago, BFD Calendar said:

But anyway, the scf_website field is still there....

The scf_website field must be there! Again: this field is used for spam protection. Please read the belonging documentation as described above, all necessary informations are there:

Quote

Spam Protection: Hide honeypot field using CSS

Spam bots fill in automatically all form fields. By adding an invisible field you're able to trick the bots. The key to the honeypot technique is that the form only can be sent when the honeypot field remains empty otherwise it will be treated as spam.

The honeypot technique doesn't interfere with the user experience. It demands nothing extra of them like a captcha does. In fact, user won't even notice you're using it.

All that's required is a visually hidden form field. This form adds such a field named scf-website by default but you have to make sure to add a display: none; CSS rule on it.

If the fields does not match, you could have a look at your database. Table modules where class equals SimpleContactForm. Column data contains json, I guess the allFields value doesn't match anymore. Otherwise just reinstall the module and start with clean settings.

To format the fields, you can pass options to adapt HTML structure as well as class names. Unfortunately not everything can be achieved using this. For really special needs you have to hook into the field render function. To get an overview of what's possible, have a look at the documentation: How to overwrite classes and markup.

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, justb3a said:

To format the fields, you can pass options to adapt HTML structure as well as class names. Unfortunately not everything can be achieved using this. For really special needs you have to hook into the field render function.

In my case I used UIkit 3 with LESS, so I could just style easily like this:

#contact-form input:extend(.uk-input) {}
#contact-form .field--error--message:extend(.uk-alert-danger) {}
#contact-form #wrap_Inputfield_submit:extend(.uk-width-1-1\@s) {}

#contact-form .FieldtypeTextarea:extend(.uk-textarea) {}
#contact-form #wrap_Inputfield_scf_message:extend(.uk-width-1-1\@s) {}

more info on Extend

Share this post


Link to post
Share on other sites

I uninstalled and deleted the module from the server, then reinstalled from the Modules interface and added fields etc. The contact.php template contains

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

	$options = array(
	'emailAdd' => true,
	'emailAddMessage' => $input->scf_message,
	'emailAddMessage' => $input->scf_name,
	'emailAddMessage' => $input->scf_hometown,
	'emailAddReplyTo' => $input->scf_emailaddress,
	'emailAddTo' => $input->scf_email,
	'markup' => array(
    'list' => "<div {attrs}>{out}</div>",
    'item' => "<p {attrs}>{out}</p>"
    ),
	'classes' => array(
    'form' => 'form amvk_contact',
    'list' => 'list-item'
	)
	);

	echo $scf->render($options);

Now the form sends me two messages. The first one has the correct sender and subject (from the module interface) and correct reply address from the scf_emailaddress field in the form. The only content in the message is the scf_hometown information. The second message is all blank.

I do understand the honeypot technique. I just wonder why the field isn't invisible by default. "make sure to add a display: none; CSS rule on it" is probably simple when you know where to add that rule. I'm afraid I don't....

Share this post


Link to post
Share on other sites
43 minutes ago, BFD Calendar said:

 


	$options = array(
	'emailAdd' => true,
	'emailAddMessage' => $input->scf_message,
	'emailAddMessage' => $input->scf_name,
	'emailAddMessage' => $input->scf_hometown,
	'emailAddReplyTo' => $input->scf_emailaddress,
	'emailAddTo' => $input->scf_email,
	'markup' => array(
    'list' => "<div {attrs}>{out}</div>",
    'item' => "<p {attrs}>{out}</p>"
    ),
	'classes' => array(
    'form' => 'form amvk_contact',
    'list' => 'list-item'
	)
	);

 

This is not how arrays work. Each key can ony exist once. EmailAddMessage is overwritten three times.

Quote

I do understand the honeypot technique. I just wonder why the field isn't invisible by default. "make sure to add a display: none; CSS rule on it" is probably simple when you know where to add that rule. I'm afraid I don't....

The field isn't visible by default, because I don't want to add inline styles. Just trigger the field in your .css file and add display:none; there.

Share this post


Link to post
Share on other sites

@justb3a Speaking of invisible fields, validator.w3.org/nu reports:

Error: The for attribute of the label element must refer to a non-hidden form control.
date'>↩↩ <label class='form__item--label' for='scf-date'>Date</

But I need to hide this field too. What is your recommended solution?

Share this post


Link to post
Share on other sites
2 minutes ago, szabesz said:

@justb3a Speaking of invisible fields, validator.w3.org/nu reports:

Error: The for attribute of the label element must refer to a non-hidden form control.
date'>↩↩ <label class='form__item--label' for='scf-date'>Date</

But I need to hide this field too. What is your recommended solution?

Couple of questions...

Why use a label for a hidden field?

Is the date field to track when the user submits the form? If so, it is not necessary. You can set the date when you process the form.

Share this post


Link to post
Share on other sites
7 minutes ago, rick said:

But it won't affect the functionality, only the w3 validation.

Sure, the module works fine, and it supports spam protection based on the time the client uses to fill it in and to submit it, which is quite useful I think. It is just this label that should be somehow eliminated if possible. Since it is a ProcessWire form API field, I do not know how to achieve it.

Share this post


Link to post
Share on other sites

I removed the date field label some days ago (@see Github issue). I didn't know that ProcessWire provides a way to skip the label. It's added to the develop branch, so it'll published with the next release! :)

  • Like 1

Share this post


Link to post
Share on other sites
3 minutes ago, justb3a said:

I removed the date field label some days ago

Oh, I was banging on open doors :) Again, thanks for the great module! 

Share this post


Link to post
Share on other sites

Is there any way to assign a css class directly to the input element? I'm trying to build the form with the bootstrap classes

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      InputfieldSlideToggle
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Status
      Still very alpha, use with caution!
      Features / Field Settings
      Size
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.
      Screenshots

      Some examples with checkbox label


      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  









    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

       
      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

       
      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

       
      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      InputfieldDatetime.zip
       
      Kind Regards
      Orkun
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




×
×
  • Create New...