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