Jump to content
justb3a

Simple Contact Form

Recommended Posts

a need 2 different forms, how can i exclude a field in one form ?

i want to render a second form without the field "message", while i need this field in the first form.

Share this post


Link to post
Share on other sites

Hello, I was wondering if it's possible to redirect to a specific URL after successfull submit, or if there's a workaround to get this done.

Regards!

 

Share this post


Link to post
Share on other sites

@Victor So far, there was no way to redirect to a specific URL. But I've considered to implement this feature from time to time. So: there is a new version including an option to specify a redirect page :)

  • Like 2

Share this post


Link to post
Share on other sites

Hello again,

I've got a new problem. I'm trying to save the message sent as a page so I have "saveMessages" enabled. But when I go to the page I've only got 3 fields on it: Title, creation date and IP address fields. So I guessed that I shoul manually add the others fields in my form to this "simple_contact_form_messages" template, but even after this I'm not able to get the fields from my form populated on the page as a saved mesasge. Am I doing something wrong? Am I missing something?

I will appreciate any help! Thanks.

 

Hello, I just wanted to let you know that it's working now. Not sure what happened. Thanks anyway. Regards.

Edited by Victor
It's working now

Share this post


Link to post
Share on other sites

@Victor 

On 22/03/2017 at 3:18 AM, Victor said:

Hello, I just wanted to let you know that it's working now. Not sure what happened. Thanks anyway. Regards.

^-^

Share this post


Link to post
Share on other sites

Hello,

is it possible to "echo" the values of the fields that just were submited on succes ?

Thanks.

Share this post


Link to post
Share on other sites
17 minutes ago, ank said:

Hello,

is it possible to "echo" the values of the fields that just were submited on succes ?

Thanks.

Hello @ank 

I think with $input->post('field_name') where you want the fields to show up.

I hope it helps. 

Share this post


Link to post
Share on other sites

I'm seriously struggling with a form

is it possible to redirect to a page after send, and still use the submitted fields.

what i want by example on the redirect page is:
IF answers on question1 = "yes" then echo "You answer was YES";
and this for several fields

Regards

Share this post


Link to post
Share on other sites

@ank

you may try echo $input->post['field_optionselect']->title . Or you can do a var_dump($input->post['field_optionselect']) in your template. That will tell you in which format the data is there and how you can access subfields like 'title'.

For using field data  on the redirect page, youcould take the values of the fields and attach them as URL query strings to the redirect URL.

Dummy code

// in the template with your form process the fields from your form
$valueField1 = $sanitizer->text($input->post['field1']);
// send them to the redirect page as url querie strings
$session->redirect("yourredirecturl" . "?field1=$valueField1");
// in the template of your redirect page, you can now get the value
$valueField1 = $input->get['field1'];
// and then do with it what you want

 

  • Like 1

Share this post


Link to post
Share on other sites

Hey guys Im new to ProcessWire and I read that ProcessWire community is very active and very helpful! So I'll say thanks in advance! 

Now to the question part. :D 

I am little bit confused of how to properly use this "easy contact form". So I installed the module and no problem with that, added fields and settings through PW admin and use $modules->get('SimpleContactForm')->render() to show the contact form on the page and no problem there as well. The form appears! 

  1. The problem starts with the posts in this thread here... I read that people talk about a "easy_contact_form.php" template file that should be generated in site/template directory. Should it be generated manually or is it generated automatically? I didn't get that part because it is not generated in my case!
  2. Now how do I modify this form? (I mean css and html part...) I read about changing the markup and style properties in options but how does it exactly work? Is there a php file generated after you add the options that you can open later and modify the code? (I hope it doesn't sound stupid because Im not used to working with CMS's)
  3. Plus if I would like to add my own spam filer (for example recaptcha), then where do I do the changes in code? For exapmle the new invisible recaptcha is added to the submit button, so where can I get to the code where the submit button is generated? Or what is the proper way to do it?

I got this project from a client where I have a big system built on ProcessWire and it has been very tough for me to make sense about everything that has been done by previous developer (no documentation left at all). I have been reading and searching alot to help me get started from somewhere but I tell you guys that so far PW does not seem very beginner friendly. There are not alot of step by step tutorials and if I search for examples on some problems then all I find is code snipets without any explanation where to use this code... Here as well all of the post give some code and talk about fixing code parts, but where exactly is the code used seems to be a common knowledge to everyone. It would be great if there would be at least one exaple page with all the files and code necessary for a beginner to scroll through and make some logical sense about how stuff works. But all in all its great to see that there is this community here that work to improve this open source CMS platform. :)

Anyway hopefully nobody gets mad at what I wrote! Not ment to offend anyone! ;)

So yeah I would appreciate if someone can point me in the right direction, at least what to read or where to find good tutorials etc. 

Cheers!

Share this post


Link to post
Share on other sites

@Slav

  1. No template file needed. This is obsolete.
  2. Please read the following part of the documentation: How to overwrite classes and markup
  3. You need to hook into the module and add your filter there. Have a look at the following documentation part: Add custom validation

Hope this will be helpful, otherwise please let me know how to improve the documentation parts. Sorry, I have no time at the moment to answer more detailed ???.

Share this post


Link to post
Share on other sites

@justb3a

Thank you for the quick reply! I will read the doc you provided. Ill try the hook part next. It looks that Im getting the hang of modifying the Markups and Classes. Takes time and trial/error to make it perfect, but form is taking the shape I was looking for.

About how to improve the doc... hmmm... Maybe add some extra descriptions about how Markup and Classes array creates content (or at least add a link to the documentation where it is already explained) that would definitely help complete beginners like me. :) You get the hang of it while testing but if you are novice like me then maybe some reading material would be useful. For example describe each part of the array, like the meaning or implementaion of {attrs} and {out}. I now understand how they work and a lot of people would say that its basic knowledge but sometimes it saves alot of time if the documentation is as detailed as possible... IMO at least :) It could save your time as well because I see alot of repeated questions in this post. So if there is enough information in Module documentation then you dont have to "waste" your time on repeated answers. ;)

Im going to be working with this Module for few days so If I see parts that are confusing I will try to think of a way to make it less confusing. :P

Anyway great job with this Module! You made alot of peoples life easier!

Cheers!

Share this post


Link to post
Share on other sites

Hi again!

Is there any way to translate submitButton Text?

I mean like, according to what language is selected... In FormBuilder there is a place where you can assign submitButton text to different languages that are used on website...

Cheers

Share this post


Link to post
Share on other sites

@justb3a

I did read the readme file... and I understood how to change the buttonText, but what I did not know was the ProcessWire way of translating (as I said before I'm completely new to PW). Now I know! Thanks! ;)

Share this post


Link to post
Share on other sites

Simple Contact Form and Template Cache?

Hey all,

thanks again for this wonderful module. How can i manage my forms with template cache turned on? You will get an internal server error.
Respectively what has to be written in the post variables?

best regards

Share this post


Link to post
Share on other sites

@maxf5 Please have a look at this post. Furthermore turning caching on could be complicated because the value of the hidden date field gets cached and this value is used for spam protection...

  • Like 2

Share this post


Link to post
Share on other sites

@justb3a Hi, could you or anyone please help me out? I have two issues to solve:

#1 I have a Select Options Filedtype in the form called scf_enquirytype. By using %scf_enquirytype% in the Email Message settings, I get the ID of the filed not the Title. Is there any way to get the Title instead?

#2 After successfully posting the form, the page is reloaded but my form – consequently the success message too – is at the bottom of the page, and the reloaded page starts at the top, so the message cannot be seen without scrolling manually to it. Is there any way to solve this? Eg. by jumping to an anchor placed before the success message? Maybe with the AJAX option I could solve it, but I do not really need the AJAX option this time.

Thanks in advance,

Share this post


Link to post
Share on other sites

Hi

#1 Do not use the email message textarea in module settings, write your own using php and access the title as you 're used to.

0)

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

 

#2 Just pass an action parameter as option: 

$modules->get('SimpleContactForm')->render($array('action' => './#anchor'));

 

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




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      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 nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...