Jump to content
justb3a

Simple Contact Form

Recommended Posts

Hello justb3a,

at the moment I try to build my first website with processwire and so I need a simple contactform.

I found your module and it works fine. But I have a problem to fit the module to my bootstrap form.

Can you explain me (i'm a beginner) how i can realize this. This would be wonderful.

Thanks and many greetings from Berlin

Share this post


Link to post
Share on other sites

hello gebeer,

thank you for your response.

I tried to change it, but in the moment it is not so easy for me. To many new things I have to learn.

Maybe you can help me.

I tried to put the class: col-sm-8 to an input field. How can I do this? Changing the "item_content" in the class-array didn't work. 

 

   Webbrowser:  <input id="Inputfield_scf_email" class=" required" name="scf_email" type="text" size="60">

Maybe you have an example for a correct array?

 

Many Greetings

Lena

Share this post


Link to post
Share on other sites

Hi,

it seems that `item_content` only apply to inputfields of type InputfieldWrapper and InputfieldPage. 

If you use something like `_init.php` you can add a hook there:

$this->addHookBefore('Inputfield::render', function(HookEvent $event) {
  if ($this->page->template->name === 'contact') { // adapt template name to compare with
    $inputfield = $event->object;
    $inputfield->addClass('col-sm-8');
    $event->return = $inputfield;
  }
});

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi all!

This module works great and I don't have any errors. I was just wondering if there is any option to send an e-mail with the data filled in the form in a template. So you receive at the end an e-mail with a logo and maybe more adjustments. Or should I add the logo in the module file to the message and maybe style it there too?

-EDIT-

My contractor haves an alias of a gmail account. So the e-mail adres looks like name@companyname.com but it is from google. Now I want to send the emails to that email address, but he receives nothing. Also not in the spambox. Is it possible that this doesn't work because the emailadress is an alias or is it something else? 

To present more information, the website I am currently working on was a few years ago moved from a hosting service to another hosting company. Now I noticed that the email in the current hosting application has the wrong records, but the e-mailadresses are still working and don't experience any problems, except for not receiving the contact form e-mail.

Does anyone know how this is possible, is it because the records are wrong (but emailaddressess still work fine) or is it a bug in the module?

Thanks in advance,

~Harmen

Edited by Harmen
Additional errors

Share this post


Link to post
Share on other sites
12 hours ago, ank said:

Hello

is there a way to make some fields required ?

Sure, you only have to check the required checkbox in the field settings.

required.png

  • Like 1

Share this post


Link to post
Share on other sites

justb3a, thanks for such a lovely script! :-)

This works perfectly with SimpleContactForm 1.0.0 on Processwire 3.0.42

<?php $scf = $modules->get('SimpleContactForm'); 
    $options = array(
	'btnClass' => 'button fit big',
	'btnText' => 'SEND MESSAGE!',
	'successMessage'  => 'Message Sent!',
	'errorMessage'  => 'Sorry - message send error!'
);
echo $scf->render($options); ?>

But if you just use this (without specifiying the successmessage) e.g.

<?php $scf = $modules->get('SimpleContactForm'); 
$options = array(
	'btnClass' => 'button fit big',
	'btnText' => 'SEND MESSAGE!'
);
echo $scf->render($options); ?>

The form processes (send) correctly, but the form output on the web page after sending is shown as:

<p class='form--success--message'>SEND MESSAGE!</p>

Showing the 'btnText', rather than the correct 'default success message'.

Have I missed someting obvious?

I've posted just incase anyone else is having the same issues.

  • Like 1

Share this post


Link to post
Share on other sites

For some sites the "spam message" might not be approprate :lol:

So I changed line 215 in SimpleContactForm.module to

            $this->_("Sorry, but your message didn't pass our %s test. Please try another %s."),

and change lines 155 (& the following) & 172 (& the following) in \lib\SpamProtection.php to

      $this->_('spam'),

and

      $this->_('time'),

 

So the message will read " Sorry, but your message didn't pass our spam test. Please try another time. "

Thanks again @justb3a

Share this post


Link to post
Share on other sites

@dab It's not that good idea to change something inside a third-party module (or, even worse, in the core). If you update the module, all your changes get lost.
I would suggest translating the values  – which will be inserted – with 'spam' and 'time'. You could also translate "Sorry, but your message didn't pass our %s test. Please try another %s." with "Sorry, but your message didn't pass our spam test. Please try another time.". Therefore I made them translatable. ^_^

  • Like 1

Share this post


Link to post
Share on other sites

Hello, Im having some problems with simple contact form styling. I tried everything but just don't get it. I went throu THIS pages but can't figure it out what should I actually do to make it the way I want. I tried and played with this but no success. Im not a coder but understand some ...

My HTML looks like this:
 


	<form action="#" method="post">
		<div class="input-field">
			<input type="text" name="name" class="form-control" placeholder="Your Name...">
		</div>
		<div class="input-field">
			<input type="email" name="email" class="form-control" placeholder="Your Email...">
		</div>
		<div class="input-field">
			<input type="text" name="Phone" class="form-control" placeholder="Phone Number...">
		</div>
		<div class="input-field">
			<textarea name="message" class="form-control" placeholder="Messages..."></textarea>
		</div>
		<button type="submit" id="submit" class="btn btn-blue btn-effect">Send</button>
	</form>

Any help is appreciated.

Thank you

R

Share this post


Link to post
Share on other sites

hi roych,

you should be as clear as possible in your questions. you don't explain what the problem is. you could add screenshots how it is and how it should be. styling is usually done via CSS. answers depend a lot on your setup...

  • Like 1

Share this post


Link to post
Share on other sites

Sorry for not being clear enough. I would like to style my form created in  SimpleContactForm module. But I can't figure it out how from those instructions. Where and how should I change classes in my code.

expl.

My code for showing a form now, looks like this. 

<?php echo $modules->get('SimpleContactForm')->render(); ?>

this is giving me some basic style from PW. How do I change those styles so it would look like the form posted in first post?

I tried and played with this

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

$options = array(
  'markup' => array(
    'list' => "<div {attrs}>{out}</div>",
    'item' => "<p {attrs}>{out}</p>"
  ),
  'classes' => array(
    'form' => 'form form__whatever',
    'list' => 'list-item'
  )
);

echo $scf->render($options);

but can't figure it out how this should work. There is no changes no mather what I do ...  And where is the Style for submit button etc.?

I hope I was more clear this time.

Thank you

R

Edited by kongondo
Your question is about module that has its own support forum. I have moved your thread to that support forum.

Share this post


Link to post
Share on other sites

Hi,

I've migrated a Processwire site that was running on PW 2.6.1 with SCF 0.1.1 to a new installation of PW 3.0.42 and after I install SCF 1.0.0 I'm getting the following error which breaks the admin:

 

Error: [] operator not supported for strings (line 131 of ...\site\modules\Processwire-SimpleContactForm\SimpleContactForm.module)

Line 131 of that file is ->     foreach (self::$additionalFields as $f) $allFieldsExtended[] = $f;

 

When I remove the [] from that line (which I don't suspect for a second is an actual fix, but at least makes the admin functional again) the module shows as installed and all of my previously created fields appear in red on the settings screen under "Select form fields". Is there something I need to do to those old fields? There's mention of upgrade notes on the first page of the thread here but none of the links work.

Share this post


Link to post
Share on other sites

I haven't used this module, so not sure about those red fields, but I think the likely correct fix for the operator not supported issue is to to define $allfields in the additional fields at around line 65.

protected $allFields = array();

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, Adrian. That got rid of the error message.

Unfortunately, it seems that a lot of functionality's been lost and with the gaping documentation gaps this isn't going to work for me.

Share this post


Link to post
Share on other sites

Why its not working?

Email is displayed as not valid, but it is. Turn yellow -> not sending...

How to turn off website and date? I hide it per css buts dirty…

using 1.0

tom

 

Share this post


Link to post
Share on other sites

I can't figure the [FAILURE] Number of fields does not match issue at all.

I have 5 fields:-

  • scf_firstname
  • scf_surname
  • scf_email
  • scf_company
  • scf_enquiry

PW ver. 3.0.33

SCF ver. 1.0.0

Any help greatly appreciated.

Share this post


Link to post
Share on other sites

@Roych

Try this:

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

$options = array(
  'btnClass' => 'btn btn-blue btn-effect',
  'btnText' => 'Send',
  'classes' => array(
    'item' => 'input-field'
  )
);

$content .= $scf->render($options);

You need to set the placeholder in the field settings, go to Admin > Setup > Fields > Edit Field: xxx > Tab Input > Placeholder Text.
It's recommended to hide the label using css (label { display: none; }). People which have to use screen readers will reward you ^_^

Unfortunately it's not that easy to add the class form-control to every input field. There is no way to set it globally.
I would suggest using css to achieve what you want:

.input-field input,
.input-field textarea,
.input-field select {
  // your styling goes here
}

Otherwise you have to hook into every render function for every fieldtype you use and pass the class inside the getAttributesString function

 

Share this post


Link to post
Share on other sites

@alexmercenary I found a little bug: The module uses a imaginary field named 'date'. Normally there is no 'date' field (naive assumption, I know) and everything works as expected. But if you create a field named 'date' for something else, the condition matches and the form has one more field than desired. The same counted for a field named 'ip'. I just released a new version 1.0.1. Please try if it's working now.

@Tom Walcher

On 24/02/2017 at 7:01 PM, Tom Walcher said:

Email is displayed as not valid, but it is. Turn yellow -> not sending...

How to turn off website and date? I hide it per css buts dirty…

The form just validates every field how it is configured in the field settings. If you want to have email validation, set the field type to email. If you want a field to be required, just check the corresponding checkbox in the field settings. Same counts for html5 validation.

Hiding the website and date field via CSS is not dirty. The website field is already of type hidden, so you just have to hide the corresponding label. The website field is intentional not hidden. It's a trap for spambot. Have a look at the documentation.

 

  • Like 1

Share this post


Link to post
Share on other sites
On 23/02/2017 at 3:40 AM, adrian said:

I haven't used this module, so not sure about those red fields, but I think the likely correct fix for the operator not supported issue is to to define $allfields in the additional fields at around line 65.


protected $allFields = array();

 

I would not recommend doing this. 'allfields' is already declared in the moduleConfig file. If you set it in the module file again, this value will be overwritten and if you render the form all fields are gone. ^_^

@Arcturus

On 23/02/2017 at 6:01 PM, Arcturus said:

Unfortunately, it seems that a lot of functionality's been lost and with the gaping documentation gaps this isn't going to work for me.

Feel free to optimise the documentation! Fixes and suggestions are very welcome!
A lot has been changed since version 0.1.1. I think, this is the page you were looking for, but this is no longer relevant. Because the module now renders the form by itself and no template adaptions are needed any longer. Did you try to render the form (frontend)? If not, please do so. There are some migration functions in the module. If you still want to use this module, please post the input of the column data from table modules where column 'class' equals SimpleContactForm. Furthermore some additional informations would be really good (save messages enabled? fields which should be added, ..).

  • Like 1

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      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 Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...