justb3a

Simple Contact Form

224 posts in this topic

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

1 person likes this

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.

1 person likes this

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

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.

1 person likes this

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.

1 person likes this

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

1 person likes this

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

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!