Jump to content
justb3a

Simple Contact Form

Recommended Posts

Since I haven't received answers, I add the code directly in the module (I know is bad but I need to finish)
Line 264:

$inputfield->attr('class','form-control');

It would be great if this option was in the configuration as well as the current option for the Send button

Share this post


Link to post
Share on other sites
On 28/06/2017 at 9:53 PM, Pixrael said:

Since I haven't received answers, I add the code directly in the module (I know is bad but I need to finish)
Line 264:


$inputfield->attr('class','form-control');

It would be great if this option was in the configuration as well as the current option for the Send button

Hi, I spent the last days without a computer (holidays!!) so I didn't read my emails :)
But the forum offers a lot of good advice and you're not the first one who asking this. So please have a look at the following posts / answers:

Share this post


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

I like the second solution, I will implement it later. Thank you!

It works, but applies the classes to all inputfields, including the form and buttons. Is there any way to ask the type of input (Ex. InputfieldText) before applying the classes? I check the API Reference for inputfield but nothing..

Share this post


Link to post
Share on other sites

I just tried to install it a few times on the current release version, but I get this same error every time:

Error: Uncaught Error: [] operator not supported for strings in /Users/me/git/site.net/site/modules/SimpleContactForm/SimpleContactForm.module:131
Stack trace:
#0 /Users/me/git/site.net/wire/core/Modules.php(602): ProcessWire\SimpleContactForm->init()
#1 /Users/me/git/site.net/wire/core/Modules.php(477): ProcessWire\Modules->initModule(Object(ProcessWire\SimpleContactForm))
#2 /Users/me/git/site.net/wire/core/ProcessWire.php(495): ProcessWire\Modules->triggerInit()
#3 /Users/me/git/site.net/wire/core/Wire.php(380): ProcessWire\ProcessWire->___init()
#4 /Users/me/git/site.net/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___init', Array)
#5 /Users/me/git/site.net/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessWire), 'init', Array)
#6 /Users/me/git/site.net/wire/core/ProcessWire.php(587) (line 131 of /Users/me/git/site.net/site/modules/SimpleContactForm/SimpleContactForm.module) 

This error message was shown because: you are logged in as a Superuser. Error has been logged.

 

Share this post


Link to post
Share on other sites
3 hours ago, Claus said:

I’m on 7.1.5

So you either have to downgrade to PHP 7.0.x or wait for @justb3a to update the module. You can "hack it" too, either by actually changing the module's code or you can try the "multiple copies of the same module" technique:

https://processwire.com/blog/posts/processwire-core-updates-2.5.14/

I never did the latter, BTW.

  • Like 1

Share this post


Link to post
Share on other sites

I downgraded to 7.0.5 and that works without issues. Thanks for the help!

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

I feel very stupid. I read all the thread and all the documentation. But I'm unable to hide scf-website by css. How I can add class='hidden' to this specific field?

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

						$options = array(
						 'btnClass' => 'button is-primary',
						 'successMessage'  => 'Message Sent!',
						 'errorMessage'  => 'Sorry - error, your message was not sent!',
						 
						  'markup' => array(
							'list' => "<div class='field' {attrs}>{out}</div>",
							'item_label' => "<label class='label' for='{for}'>{out}</label>",
							'item' => "<div class='control'>{out}</div>",
							'item_error' => "<article class='message is-warning'><div class='message-body'>{out}</div></article>",
						  ),
			
						);

						echo $scf->render($options);

Thanks

Melanie

Share this post


Link to post
Share on other sites

@mel47 How do you mean?

If you add the following to your CSS file this should work

#wrap_Inputfield_scf-website, 
#wrap_scf-date {
	display: none;
}

That should work

Share this post


Link to post
Share on other sites

It's not that easy to access only this field, you could add a class for every "InputfieldText" for example.

But why not extending your CSS as @alexmercenary suggested? If you do not want to use an ID as CSS selector you could use classes as well.

This is the default markup:

<div class="form__item form__item--scf-website" id="wrap_Inputfield_scf-website">...</div>
<div class="form__item form__item--scf-date field--required" id="wrap_scf-date">...</div>

As you can see, every field gets wrapped using the class form__item--{fieldname}. Just extend your CSS:

.hidden, 
.form__item--scf-website {
    display: none;
    visibility: hidden;
}

:)

Share this post


Link to post
Share on other sites

Ok thanks! Have played too much with markup and classes options (incorrectly). Everything is fine now.

Mel

Share this post


Link to post
Share on other sites
On 7/19/2017 at 7:16 AM, Claus said:

I just tried to install it a few times on the current release version, but I get this same error every time:

[...]

As a follow-up to this, where exacty is allFields first declared before init() is called? Not sure what's going on there, because that's supposed to be an array, but it looks like PHP is calling it a string...?

Share this post


Link to post
Share on other sites

@Mike Rockett It's declared in `SimpleContactFormConfig.php:19`. It was declared as string (oops, my fault :P) but should be of type array. I've fixed it.

  • Like 2

Share this post


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

@Mike Rockett It's declared in `SimpleContactFormConfig.php:19`. It was declared as string (oops, my fault :P) but should be of type array. I've fixed it.

Ah right, didn't actually think it was a config property (wasn't looking properly). 

Share this post


Link to post
Share on other sites

I just realised that a user can omit filling out any of the form fields, then press 'Send', and an email will be sent. Am I doing something wrong, or how can I stop this from happening?

Share this post


Link to post
Share on other sites
5 hours ago, Claus said:

how can I stop this from happening

The module uses ProcessWire's own form API; you just need to set the required fields to be required in the admin.

  • Like 2

Share this post


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

The module uses ProcessWire's own form API; you just need to set the required fields to be required in the admin.

Bingo! Thanks.

  • Like 1

Share this post


Link to post
Share on other sites

Uff, after a few weeks i have a problem with the checkboxes in the form.
They 're not required, but the user can't send the form when not checked.

Anyone with same problems?

Iam using two different forms on my website (different pages) which haven't the same fields,
i set the fields for the particular form with:

$options = array(
  'allFields' => 'sfc_tel,scf_fax,scf_email,scf_subject,scf_message,scf_haendlerwerden',
  ..
);

scf_haendlerwerden is a checkbox, not-required. 
Is that where the error comes from, selecting the fields via $options["allFields"] ?

ProcessWire 3.0.75

Share this post


Link to post
Share on other sites
On 21/09/2017 at 9:14 PM, maxf5 said:

Any ideas? How do you set up checkboxes?

Hei, I found some time to reproduce your issue. The logfile (BE > Logs > Simplecontactform-log) contains the reason what's going wrong:

> [FAILURE] Number of fields does not match.

This means that the number of submitted fields does not match the number of fields which are present in the form. Looking further it turned out that $this->input->post does not contain the checkbox field (if it wasn't checked). 

It's a standard browser behaviour that the value of a checkbox is only sent if the checkbox was checked. This means I have to exclude this fieldtype when comparing number of fields / counting fields. coming soon...

 

Edit: Just published a new release / version 1.0.5. Please update.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Hi justb3a, the module is amazing! I think I found a small glitch: if one tries to enter more than one field name in "Create and add fields" (comma separated), ProcessWire throws an error:

 ProcessWire: ProcessModule: Field name 'scf__contact_lastname' may not have double underscores because this usage is reserved by the core

Field names I tried with are like this: contact_title, contact_firstname, contact_lastname...
If this field names are entered in one by one, all is well.

PW version 3.0.76

Share this post


Link to post
Share on other sites

@titanium The problem wasn't that you entered multiple fieldnames at once. The comma-separated may not include spaces. So entering `contact_title,contact_firstname,contact_lastname...` does work. I added a hotfix which removes the spaces before parsing the string.

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...