Jump to content
justb3a

Simple Contact Form

Recommended Posts

@justb3a: i increased the max_execution_time from 30 to 60 sec. the memory_limit is at 256M and still the same problem. :huh:

Share this post


Link to post
Share on other sites

@itsberni: 60 is not enough. Try the following values:

max_execution_time = 240
max_input_time = 240
memory_limit = 1024M 

Share this post


Link to post
Share on other sites

Hi Congomonster,

you have to change the fieldname. in your case scf_fullName in e.g. scf_Nachname. Be carefull. the prefix scf_ is important.

And you also have to change the values ( input - Tag ) in your form. But here you go without the prefix!

Don´t forget to adapt the fieldnames in your modulconfiguration. also without the prefix.

Hi itsberni,

thank you for answer. It worked except for the date field. :frantics:

For now it's perfect! :biggrin:

Share this post


Link to post
Share on other sites

@congomonster: I have to find / provide another solution for this issue. For now it's ok but it shouldn't be the solution to solve it that way...  :mellow:

Share this post


Link to post
Share on other sites

@itsberni: 60 is not enough. Try the following values:

max_execution_time = 240
max_input_time = 240
memory_limit = 1024M 

thanks, justb3a - i've tried this values.

After a very long period of time, the mails are appearing.

I think that's way to long. Could that be caused by the repeater, that slows down everthing in my case?!

the contactform is in a testphase already, so there are a lot of entries ( about 180 ).

If i try to delete data in the repeater, the script tooks again a very long period of time an after that, the tagged

data is not deleted. :(

Any ideas though?

Share this post


Link to post
Share on other sites

Can anybody help me?

I have been trying for two full days to get this module running - thats OK because I am still learning. With everything else so far (e.g. include a simpler contact form and make it work) I was able to figure it out by modifying stuff I found elsewhere but now I am stuck.

I installed the module, set up the template file and the HTML works: I get a page with fields and I can enter data. But when I press „submit“ nothing happens. I get no error message, nothing.

I have tried to address the module through php and through JS, I tried hundreds of variations of syntax, it seems I do something wrong addressing the module.

Could anybody please supply me with an example for a full and correct code and let me know where to insert it?

Thanks A LOT!

Share this post


Link to post
Share on other sites

Using a honeypot I am able to filter out almost all spambots surprisingly, that may just be me, but using this method I have been pretty successful. 

Share this post


Link to post
Share on other sites

@Kami: Please have a look at your log file (simplecontactform-log). 

Edit: Please set $config->debug in site/config.php to true and try again  ^_^

@itsberni: Sorry for answering that late. I guess we must transfer the form action to the frontend by using pagination (20 entrys a page).

Share this post


Link to post
Share on other sites

Thanks, I set $config->debug to "true" and restarted PW but in PW/Setup/Logs I only see a simplecontactform-spam-log, no simplecontactform-log?

Share this post


Link to post
Share on other sites

And no error message appears (frontend or error log). Does it reload the page if you press submit? Is there an entry in  simplecontactform-spam-log? There is a setting called antiSpamTimeMin, if you submit the form really fast, the content will be treated as spam. There should be an entry in the spam log. Try to set this setting (in module settings) to 0.

Share this post


Link to post
Share on other sites

There is an error message but it concerns a template I don´t use (?) so I am not sure it is related: "Error: Call to undefined function renderNav() (line 12 of /Applications/MAMP/htdocs/site/templates/basic-page.php)". Line 12 is: "renderNav($page->children);".

There is an entry in the spam-log but its date is from yesterday: "CSRF Token validation failed."
 

The page seems to reload when I press submit, it keeps the entries in "name" and "email" but not the entry in the message field. AntiSpamTimeMin is set to 0.

Share this post


Link to post
Share on other sites

There is an error message but it concerns a template I don´t use (?) so I am not sure it is related: "Error: Call to undefined function renderNav() (line 12 of /Applications/MAMP/htdocs/site/templates/basic-page.php)". Line 12 is: "renderNav($page->children);".

This is another error message which is not related to this module. Somewhere in your template you call renderNav($page->children) but this function doesn't exist. This function comes with a basic ProcessWire installation and is located in _func.php which is required by _init.php ($config->prependTemplateFile in config.php)

There is an entry in the spam-log but its date is from yesterday: "CSRF Token validation failed."

This module uses CSRF token validation, if you don't know what it's all about, have a look here. In your form there must be an hidden input field, make sure that it's still there (<input type='hidden' name='<?= $input->tokenName; ?>' value='<?= $input->tokenValue; ?>' class='_post_token' />).

Check also that there is another hidden input field: <input type="hidden" name="submitted" value="1">. Do not remove one of them!

Share this post


Link to post
Share on other sites

Hello, I installed this module. I have a problem when submitting the form, I get the error message to verify data. What could be the problem?

Example:

ASBSKSa.jpg

Edited by Bam Bino

Share this post


Link to post
Share on other sites

@Bam Bino: Did you remove some fields? I can't see scf-website as well as submitted. These fields are necessary for validation. If I just install the module without any config / html - css adaptions, it should look like this:

post-2759-0-79695600-1436778971_thumb.pn

Share this post


Link to post
Share on other sites

The scf-date field should be invisible as well. Please add in site/modules/SimpleContactForm/SimpleContactForm.module after line 424 var_dump($field); and paste the output (make sure $config->debug is set to true in site/config.php):

foreach ($form as $field => $value) {
  if (empty($value)) {
    var_dump($field);
    $error = true;
    continue;
  }
}

Share this post


Link to post
Share on other sites

Hi, justb3a. I did as you instructed, but I get zero output of var_dump when I submit the form. It goes like this:

1. I fill the form

lhXkJp7.png

2. When I submit it I get the error message:

yfQaRh8.png

3. When I resubmit the form I am redirected to home page:

pZB6qlt.png

4. As modules documentation says it means that it was marked as spam, so I open simplecontactform-spam-log.txt for the error information"

4gm8Cef.png

Share this post


Link to post
Share on other sites

I've run into an issue where if I trigger an error state (say by leaving the form blank or by skipping a required field) the next submission always redirects to the homepage while generating a "CSRF Token validation failed" message. Everything else is working presently. Any ideas?

(PW 2.6.1)

I have a couple of small feature suggestions that would be nice: 1) The ability to assign a "From" name for generated emails; 2) The ability to send messages to multiple recipients. Thanks!

Share this post


Link to post
Share on other sites

New version 0.1.2

* fixes CSRF token validation (Thanks!)

* adds option to overwrite email message

* adds "from name" for generated email

* allows multiple recipients

  • Like 4

Share this post


Link to post
Share on other sites

Hello,

I just need to setup a simple contact form so, I installed SimpleContactForm.

Then I went to Admin >> ModulesSimple >> Contact Form and followed the instruction.

After I included below code into my contact.php and refresh the page, nothing came out @ blank page.

<?php $modules->get('SimpleContactForm')->render(); ?>

If I have the budget I could buy myself the FormBuilder but sadly not so much at the moment.

Please tell me, is there any way to fix this issue or if there's something I overlooked ?

Thank you.

Edited by kongondo
Merged to SimpleContactForm's support forum

Share this post


Link to post
Share on other sites

I have managed to call the contact form by adding echo

<?php echo $modules->get('SimpleContactForm')->render(); ?> 

 but there are 2 more issues :

1) How do you replace unordered list bullets which appear near the form label ?

post-3657-0-81343700-1439976399_thumb.pn

2) When I submitted the form my browser got redirected to the Home page and found out the simple_contact_form.php don't have any value in action="./" . How to fix this ?

post-3657-0-75658500-1439976609_thumb.pn

Thank you

Share this post


Link to post
Share on other sites

@kradzcalypse:

1) A new template called simple_contact_form.php will be created in your site/templates directory. Once created you can/should modify the template as well as the fields to your own needs, just make sure to maintain the names of the fields. So you can substitute the list (<ul> <li>..) tags with divs or adapt your css and set "list-style: none;" for this list.

To hide the fields adapt the css using for example "display: none;".

2) The action is not empty. action="./" refers to the current page. Have a look at your log file (Admin > Setup > Logs > simplecontactform-log). I guess the spam protection applies here and redirects you to the home page.

----------------------------------------------------

PS: These are simple basics of CSS and HTML.  ^_^ 

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

Thanks for your reply. 

Please have a look at my contact page : http://pesisirbrand.com/contact/

After filling up the contact form and press submit button the browser return the Home page but data never got submitted

to inbox here : http://pesisirbrand.com/scf-messages/

Admin > Setup > Logs > simplecontactform-log returned :

 

[FAILURE] Honeypot field was filled.

Share this post


Link to post
Share on other sites

The field you named "Web Url (Optional)" is not allowed to be filled. This field should be invisible. Spam boots are used to fill every field and the honey pot technique is one way to keep them out. Hide this field, add one field more to get a web url field if needed.

Share this post


Link to post
Share on other sites

Thanks justb3a,

It works. 

I tried adding 3 more input fields into the form (Address, Telephone Number & Identification) and then created 3 new fields in the admin section but where can I define the input id ( e.g : Inputfield_Alamat ) for those 3 new form fields ?

Here are things that I've done so far ..

simple_contact_form.php

<div class="form-group">
		<label class="col-md-3 control-label" for='Inputfield_Alamat'>Alamat<i class='toggle-icon fa fa-angle-down' data-to='fa-angle-down fa-angle-right'></i></label>
		<div class="col-md-9">

<input id="Inputfield_Alamat" class="form-control" name="Address" value="<?= $input->Alamat; ?>" type="text" maxlength="2048" placeholder="" />
		</div>
            </div>

site/modules/SimpleContactForm/SimpleContactForm.module

protected static $defaults = array(
    'fullName' => '',
    'Address' => '',
    'Telephone Number' => '',
    'Identification' => '',
    'emailTo' => '',
    'emailSubject' => 'New Web Contact Form Submission',
    'successMessage' => 'Thank you, your submission has been sent.',
    'errorMessage' => 'Please verify the data you have entered.',
    'emailMessage' => '',
    'emailServer' => 'noreply@server.com',
    'allFields' => 'fullName,Alamat,Telefon,KadPengenalan,email,message',
    'requiredFields' => 'fullName,Alamat,Telefon,KadPengenalan,email,message',
    'emailField' => 'email',
    'saveMessages' => true,
    'antiSpamTimeMin' => '0',
    'antiSpamTimeMax' => '90',
    'antiSpamPerDay' => '3',
    'antiSpamExcludeIps' => '127.0.0.1',
    'antiSpamCountAdditionalInputs' => '5',
    'useTwig' => false,
    'cleanup' => 0
  );

.....

.....

public static function getModuleConfigInputfields(array $data) {
    $fields = new InputfieldWrapper();
    $modules = wire('modules');

    // default config values
    $data = array_merge(self::$defaults, $data);

......
.......

     'Address' => array(
        'type' => 'InputfieldText',
        'description' => 'Fallback: Alamat',
        'size' => 45,
        'placeholder' => 'Alamat',
        'columnWidth' => 50
      ),
      'Telephone Number' => array(
        'type' => 'InputfieldText',
        'description' => 'Fallback: Telefon',
        'size' => 45,
        'placeholder' => 'Telefon',
        'columnWidth' => 50
      ),
      'Identification' => array(
        'type' => 'InputfieldText',
        'description' => 'Fallback: Kad Pengenalan',
        'size' => 45,
        'placeholder' => 'Kad pengenalan',
        'columnWidth' => 50
      ),

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 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!
    • By Robin S
      After forgetting the class name of the wonderful AdminPageFieldEditLinks module for what feels like the 100th time I decided I needed to give my failing memory a helping hand...
      Autocomplete Module Class Name
      Provides class name autocomplete suggestions for the "Add Module From Directory" and "Add Module From URL" fields at Modules > New.
      Requires ProcessWire >= v3.0.16.
      Screencast

      Installation
      Install the Autocomplete Module Class Name module.
      Configuration
      Add Module From Directory
      Choose the type of autocomplete suggestions list: "Module class names from directory" or "Custom list of module class names". The latter could be useful if you regularly install some modules and would prefer a shorter list of autocomplete suggestions. The list of class names in the modules directory is generated when the Autocomplete Module Class Name module is installed. It doesn't update automatically (because the retrieval of the class names is quite slow), but you can use the button underneath when you want to retrieve an updated list of class names from the directory. Add Module From URL
      If you want to see autocomplete suggestions for the "Add Module From URL" field then enter them in the following format:
      [autocomplete suggestion] > [module ZIP url]
      Example: RepeaterImages > https://github.com/Toutouwai/RepeaterImages/archive/master.zip Awesomplete options
      The "fuzzy search" option uses custom filter and item functions for Awesomplete so that the characters you type just have to exist in the autocomplete suggestion item and occur after preceding matches but do not need to be contiguous. Uncheck this option if you prefer the standard Awesomplete matching. Custom settings for Awesomplete can be entered in the "Awesomplete options" field if needed. See the Awesomplete documentation for more information.  
      https://github.com/Toutouwai/AutocompleteModuleClassName
      https://modules.processwire.com/modules/autocomplete-module-class-name/
×
×
  • Create New...