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

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

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

@justb3a, it's working now with the update to 1.0.5, huge thanks for your time and patience!

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

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 joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.1.1 Debugging: fixed error during uninstall 0.1.0 Added new detection of async scripts for W3C Validation 0.0.6 CSS-Debugging for hiding unused buttons, added ProCache support for the JavaScript tag 0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • By bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
×
×
  • Create New...