Jump to content
justb3a

Simple Contact Form

Recommended Posts

Never! change anything in the module code!

Just go to module settings (Admin > modules > SimpleContactForm > Edit) and add there the fields. Click submit, reload the form, you will see the new fields appended.

Please have a look at the documentation!

post-2759-0-15114000-1440412681_thumb.pn

Share this post


Link to post
Share on other sites

I'm having some troubles with the form. 

I've setup everything on my localhost and every thing seems to be working fine. Then i've copied everything to my server and for some reason the form stopped working. 

When I fill in all the field i get an error: 'Please verify the data you have entered.' even though everything looks fine. The weird part is that is doesn't say anything in the Logfile. 

Do you have any idea what the problem could be?

Share this post


Link to post
Share on other sites

@ttttim: Do you use the latest version? Since the latest version every action should be logged.

Share this post


Link to post
Share on other sites

Thankyou for building out this form. I was trying to setup the plugin, but everytime I remove a field name I get the following error: 

Error: Call to a member function save() on null (line 1098 of /home/marmil113/marshhospital.com/site/modules/simplecontactform/SimpleContactForm.module)

Any idea what I can do?

Share this post


Link to post
Share on other sites

@carlos: I guess there is something broken with your database because the fieldgroup failed to save after removing a field. Is this a production installation? If not, I would recommend to deinstall this module and check the clear data option (please do a backup before). After that have a look at your database and clear all stuff generated by this module if there’s something left. If the deinstallation with the clean option fails, you have to do this manually.

I tested it again and everything is working as expected. 

Share this post


Link to post
Share on other sites

I've been playing around with simple contact form and it works great!

I'm pretty new to all this, i'm trying to send the form using ajax ( thats so the page doesn't refresh right? ), iv'e included jquery.simplecontactform.js using 

   <script src="<?php echo $config->urls->templates?>scripts/jquery.simplecontactform.js"></script>

on my main page.

but what do i do with 

if ($('.js-simplecontactform').length) {

$.simplecontactform($('.js-simplecontactform'));
}

iv'e tried adding it to my main page using <script> and also tried <?php> neither works.

Also is there a way to style the send confirmation text?

heres some examples of what i've done so far.

http://ianjburgess.com/screenshot/Screen%20Shot%202015-10-14%20at%202.40.10%20PM.png

http://ianjburgess.com/screenshot/Screen%20Shot%202015-10-14%20at%202.40.59%20PM.png

Share this post


Link to post
Share on other sites

@Mido: Not the best but simplest solution:

  •  include jQuery
  •  include SimpleContactForm script
  •  include a general js file (main.js for example) which contains the function call you mentioned above

To style the confirmation text, modify the template, add a class and add CSS for that class.

Share this post


Link to post
Share on other sites

Hey

I really like this module and got it working quite well. There's only a few issues which I've encountered. Some mails are being sent directly and other need a wait time of maybe 30 minutes to be send to the email I've set in the settings. I've excluded my IP for the spam option yet it takes a long time for some messages to get through. Any idea what triggers this?

In the /scf-messages/ I can still see all the messages right away after they have been accepted by the system.  Could it still have something to do with the spam filter?

edit: Tried another IP too, still waiting for the mail...

edit 2: Last received mail took 2h to arrive

edit 3: Now they seem to come straight away... weird...

Share this post


Link to post
Share on other sites

hi,

I'm quite sure that this behaviour is not related to this module. The spam filter only checks some stuff and if everything is fine it hands the mail over to the mail agent and saves the message. Have a look at your mail log, maybe there is a queue. If the message was saved successfully, the spam checks are passed without any problem.

Share this post


Link to post
Share on other sites

Thanks @justb3a for your module, I am finally getting to use it :)

TL;DR

Is there something I need to configure in SCF to ensure it uses the WireMailSMTP module to send mail rather than in-built/default methods in PW? Thanks for any comments.

Background

I would like to sent mail via Mandrill and so as I have in the past with the PW Forms module I have installed WiremailSMPT; I noticed you said SCF now supports WireMail. I assumed that this meant when email was sent from the SCF if WireMailSMTP was installed it would automatically go via that module (and it's settings (Mandrill in my case)), but so far I am finding emails are arriving AOK but not via the WireMailSMTP module (as Mandrill is not listed in the route).

Share this post


Link to post
Share on other sites

I began editing simple_contact_form.php and found I was getting [FAILURE] CSRF Token validation failed. I back-tracked and found that, apparently, reindenting the code of the original form file with a Sublime Text plugin caused the errors..? I tried to diff the original versus the reindented one but as far as I could see nothing was 'wrong', just differently indented.

No time now to do stuff like try an alt diff tool in case the first missed something, but I thought I'd share in case this helps anyone else.

@justb3a if a copy of the indented-and-broken code would be helpful just let me know and I'll publish it on Dropbox or similar.

Share this post


Link to post
Share on other sites

@alan: Did you check that CSRF token validation works? If you load the form (frontend) there should be a hidden input containing a generated name and value:

<input type="hidden" id="_post_token" name="TOKEN1234567891X1234567891" value="A1B2c3d4efgHIj5klLmno6pQrstUVwxy" />

As said above, the name and value are generated, make sure it's not hardcoded. Also have a look at your log file (simplecontactform-log), all errors are displayed there.

I've never used WireMailSMTP – if you've figured out how to use it, please let me know!  ;)

  • Like 1

Share this post


Link to post
Share on other sites

@all Right now all is good and I am just trying to work out how to have SCF use WireMailSMTP rather than native PW transport.

It uses it out of the box, mean: you haven't to do anything in regard of SCF. SCF uses wiremail(), - and if you have installed and setup wiremailSMTP, it is used instead of the basic wiremail, which uses the PHP mail function.

  • Like 1

Share this post


Link to post
Share on other sites

@justb3a Thanks, yes the token is there and since I undid the reindenting of code it works AOK. Also thanks I have used the log to see what was wrong (very helpful, I also spotted that my test emails had hit the IP address limit per day so I upped it for testing :)

@horst Thanks, yes I assumed that it was used. But I am pretty sure it's not being used...

History: I installed and used SCF to send email (via PW built in wiremail I assume). Then I installed WireMailSMTP and set it to use my Mandrill credentials.

But email is arriving without showing Mandrill as the sender (view email headers also shows no mention of Mandrill.com) and based on all my other uses of WiremailSMTP+Mandrill I assume (where Mandrill is listed) I assume this mean Mandrill and therefore WireMailSMTP are being bypassed (I guess?).

Env: • WireMailSMTP passes it's connectivity test. • I have debug turned on.

If there's anything I can do to help test what may be happening I'd be happy to test and report.

Thanks in advance for any suggestions.

  • Like 1

Share this post


Link to post
Share on other sites

I use it on one site with wiremailSMTP and it works. But I haven't used it together with Mandrill.

I think you use a recent or latest version of SCF? (earlier version hasn't supported wiremail())

You may check in the headers of your emails for the User-Agent, e.g. ProcessWire/WireMail or ProcessWire/WireMailSMTP or ...

  • Like 1

Share this post


Link to post
Share on other sites

@horst Thanks for the suggestions, I will check and report back in case it's of any help to others.

  • Like 1

Share this post


Link to post
Share on other sites

@horst I checked and

  • SCF is 0.1.2 which is the latest at the moment = ✔
  • header says "...X-Mailer: ProcessWire/WireMail..." = ✖

so my setup (WireMailSMTP ver 0.1.13 on a PW 2.7.0 site and SCF) seems to be working AOK but emails are bypassing WireMailSMTP :'(

@justb3a and/or @horst : if there is anything I could do here to help fix this for me (and I assume others) then I would be happy to try stuff and report back/thanks for any suggestions you may have :)

  • Like 1

Share this post


Link to post
Share on other sites

Fixed the problem where WireMailSMTP is being bypassed in favour of WireMail...

@justb3a I would usually leave module code 100% alone, but comparing how mail is called in another site I noticed it was different, so I edited `SimpleContactForm.module` around line 478 like this: 

// Below original module code bypasses WireMailSMTP
// $wireMail = new WireMail();

// Below does not bypass WireMailSMTP
$wireMail = wireMail();

and email is then sent via WireMailSMTP. If I edit it back to the original then it bypasses WireMailSMTP and I can switch back and forth depending on how I leave the code around line 478.

If this is this something you would like me to log on git etc then please let me know as I would love to have an official (unedited) copy of your excellent module that used WireMailSMTP.

Sorry if I explained that all badly and thanks again for this module, cheers, -Alan

  • Like 3

Share this post


Link to post
Share on other sites

@alan: WOW! What a great find.  ^-^  You are right. I have checked this and yes, on the site I thought it would working together, it also bypasses SMTP as you described it.

@justb3a: please can you fix this with one of the next releases?

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the fix @justb3a and glad this helped your site also @horst ^_^

  • Like 1

Share this post


Link to post
Share on other sites

new version 0.2.0 brings in some new features:


  • supports multiple instances
  • allows usage of full ProcessWire API in options
  • allows to render more than one contact form on a page
  • allows to send more than one email
  • makes validation hookable
  • read on
  • Like 4

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 Robin S
      First a note about my other modules...
      I have three existing modules that are similar in that they allow restrictions to be placed on repeating inputfields: Limit Repeater, Limit PageTable, Limit Table
      Restrict Repeater Matrix takes a different approach to the module configuration from those other modules. The module settings for Restrict Repeater Matrix are applied in the field settings rather in a module config screen. I think this new approach is better, but it means that it isn't practical to create different settings for different roles via the admin interface. Instead the module has a hookable method, allowing roles to be targeted and other advanced usages to be achieved via a hook. The result is that the module is more flexible.
      I intend to transition my other modules to the same approach over the coming weeks, but because this will result in breaking changes I will be releasing the updated modules under new names ("Restrict Repeater", etc) to avoid users upgrading via the Upgrades module without full awareness of the changes. The old modules will be marked as deprecated.
      Restrict Repeater Matrix
      A module for ProcessWire CMS/CMF. Allows restrictions and limits to be placed on Repeater Matrix fields. Requires ProcessWire >= v3.0.0 and FieldtypeRepeaterMatrix >= v0.0.5.
      For any matrix type in a Repeater Matrix field you have the option to:
      Disable settings for items (cannot change matrix type) Prevent drag-sorting of items Prevent cloning of items Prevent toggling of the published state of items Prevent trashing of items Limit the number of items that may be added to the inputfield. When the limit is reached the "Add new" button for the matrix type will be removed and the matrix type will not be available for selection in the "Type" dropdown of other matrix items. Please note that restrictions and limits are applied with CSS/JS so should not be considered tamper-proof.
      Usage
      Install the Restrict Repeater Matrix module.
      For each matrix type created in the Repeater Matrix field settings, a "Restrictions" fieldset is added at the bottom of the matrix type settings:

      For newly added matrix types, the settings must be saved first in order for the Restrictions fieldset to appear. Set restrictions for each matrix type as needed. A limit of zero means that no items of that matrix type may be added to the inputfield.
      Setting restrictions via a hook
      Besides setting restrictions in the field settings, you can also apply or modify restrictions by hookingRestrictRepeaterMatrix::checkRestrictions. This allows for more focused restrictions, for example, applying restrictions depending on the template of the page being edited or depending on the role of the user.
      The checkRestrictions() method receives the following arguments:
      $field This Repeater Matrix field $inputfield This Repeater Matrix inputfield $matrix_types An array of matrix types for this field. Each key is the matrix type name and the value is the matrix type integer. $page The page that is open in ProcessPageEdit The method returns a multi-dimensional array of matrix types and restrictions for each of those types. An example of a returned array:

      Example hooks
      Prevent the matrix type "images_block" from being added to "my_matrix_field" in a page with the "basic-page" template:
      $wire->addHookAfter('RestrictRepeaterMatrix::checkRestrictions', function(HookEvent $event) { $field = $event->arguments('field'); $page = $event->arguments('page'); $type_restrictions = $event->return; if($field->name === 'my_matrix_field' && $page->template->name === 'basic-page') { $type_restrictions['images_block']['limit'] = 0; } $event->return = $type_restrictions; }); Prevent non-superusers from trashing any Repeater Matrix items in "my_matrix_field":
      $wire->addHookAfter('RestrictRepeaterMatrix::checkRestrictions', function(HookEvent $event) { $field = $event->arguments('field'); $type_restrictions = $event->return; if($field->name === 'my_matrix_field' && !$this->user->isSuperuser()) { foreach($type_restrictions as $key => $value) { $type_restrictions[$key]['notrash'] = true; } } $event->return = $type_restrictions; }); http://modules.processwire.com/modules/restrict-repeater-matrix/
      https://github.com/Toutouwai/RestrictRepeaterMatrix
    • By BitPoet
      Here's a little text formatter module that redirects all external links found in a textarea (e.g. for hit counting) to a given URL.
      TextformatterExternalRedirect
      GitHub repo
      As TextFormatters do, this module modifies the contents of the textarea (HTML) at rendering time. It prepends the given URL to the link address for external links (http and https), optionally makes sure that the link is opened in a new window and allows you to add css classes to such links.
      All options can be configured in the module's configuration settings.
      Usage:
      Download the zip archive and extract it to site/modules, the rename the top folder to TextformatterExternalRedirect Go to the backend and select "Modules" -> "Refresh", then click "Install" for "External Link Redirect" Click "Settings" and configure the module
      Go into the field configuration for the field(s) you want this formatter to apply to and add it from the dropdown
      Done, now any external links in the configured fields will have the configured settings applied Feel free to leave feedback and post and questions you have here.
       
    • By teppo
      Hey folks!
      Took a couple of late nights, but managed to turn this old gist of mine into a proper module. The name is SearchEngine, and currently it provides support for indexing page contents (into a hidden textarea field created automatically), and also includes a helper feature ("Finder") for querying said contents. No fancy features like stemming here yet, but something along those lines might be added later if it seems useful (and if I find a decent implementation to integrate).
      Though the API and selector engine make it really easy to create site search pages, I pretty much always end up duplicating the same features from site to site. Also – since it takes a bit of extra time – it's tempting to skip over some accessibility related things, and leave features like text highlighting out. Overall I think it makes sense to bundle all that into a module, which can then be reused over and over again 🙂
      Note: markup generation is not yet built into the module, which is why the examples below use PageArray::render() method to produce a simple list of results. This will be added later on, as a part of the same module or a separate Markup module. There's also no fancy JS API or anything like that (yet).
      This is an early release, so be kind – I got the find feature working last night (or perhaps this morning), and some final tweaks and updates were made just an hour ago 😅
      GitHub repository: https://github.com/teppokoivula/SearchEngine Modules directory: https://modules.processwire.com/modules/search-engine/ Demo: https://wireframe-framework.com/search/ Usage
      Install SearchEngine module. Note: the module will automatically create an index field install time, so be sure to define a custom field (via site config) before installation if you don't want it to be called "search_index". You can change the field name later as well, but you'll have to update the "index_field" option in site config or module settings (in Admin) after renaming it.
      Add the site search index field to templates you want to make searchable. Use selectors to query values in site search index. Note: you can use any operator for your selectors, you will likely find the '=' and '%=' operators most useful here. You can read more about selector operators from ProcessWire's documentation.
      Options
      By default the module will create a search index field called 'search_index' and store values from Page fields title, headline, summary, and body to said index field when a page is saved. You can modify this behaviour (field name and/or indexed page fields) either via the Module config screen in the PocessWire Admin, or by defining $config->SearchEngine array in your site config file or other applicable location:
      $config->SearchEngine = [ 'index_field' => 'search_index', 'indexed_fields' => [ 'title', 'headline', 'summary', 'body', ], 'prefixes' => [ 'link' => 'link:', ], 'find_args' => [ 'limit' => 25, 'sort' => 'sort', 'operator' => '%=', 'query_param' => null, 'selector_extra' => '', ], ]; You can access the search index field just like any other ProcessWire field with selectors:
      if ($q = $sanitizer->selectorValue($input->get->q)) { $results = $pages->find('search_index%=' . $query_string . ', limit=25'); echo $results->render(); echo $results->renderPager(); } Alternatively you can delegate the find operation to the SearchEngine module as well:
      $query = $modules->get('SearchEngine')->find($input->get->q); echo $query->resultsString; // alias for $query->results->render() echo $query->pager; // alias for $query->results->renderPager() Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 Note: later versions of the module may require Composer, or alternatively some additional features may require installing via Composer. This is still under consideration – so far there's nothing here that would really depend on it, but advanced features like stemming most likely would.
      Installing
      It's the usual thing: download or clone the SearchEngine directory into your /site/modules/ directory and install via Admin. Alternatively you can install SearchEngine with Composer by executing composer require teppokoivula/search-engine in your site directory.
    • By teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if someone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put I've been using MSN (...) for years, and it's been great – but there are some issues with it, particularly in the markup generation area, and it also does some things in a way that doesn't quite work for me – the xtemplates thing being one of these. In some ways less about features, and more about style, I guess 🙂
      Anyhow, in MarkupMenu I've tried to correct those little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and with PHP 7.1+ in mind, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) still on my todo list.
      One more small(ish) difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site had a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to leave that out 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM – one of those three or four letter abbreviations anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework" since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
×
×
  • Create New...