justb3a

Simple Contact Form

Recommended Posts

On 07/01/2018 at 6:10 PM, justb3a said:

this is a really huge difference.. You could try to update version by version and always make sure to save module settings. Otherwise you could try to update the module settings json manually

Thanks for replying.  I tred updating the JSON manually to change allFields from a simple string to an array, which solved the initial problem, but then I got other errors with the scf-messages page in particular... I seem to have got my system into a proper mess so will probably need to reinstall from scratch.

One thing that puzzles me is that the documentation has changed a lot since version 0.2.1 - I can't see any reference to the scf-messages page at all in version 1.07 for example.

Share this post


Link to post
Share on other sites

@dougwoodrow It changed a lot, for example in the initial version the module generated a template file, so that everybody could adapt the html (form) structure as needed. But it turned out that this led to a lot overhead for me to support it. Furthermore I lost the possibility to use the ProcessWire way of handling form inputs, setting error messages, validation, form processing and so on. Therefore I decided to generate the complete form and offer as many options as possible to be able to adapt the markup / classes. Saving messages is still possible – with the difference that you're able to define the `save-messages-template` as well as the `parent`. So handling multiple (different) forms  isn't a problem...

  • Like 1

Share this post


Link to post
Share on other sites

Hi there, 

I was wondering if it is possible to use an image field with the popular "Simple Contact Form" of @justb3a

When I tried I got the following error message (without even "uploading" an image):

Call to a member function path() on null in C:\xampp\htdocs\pw2\wire\modules\Fieldtype\FieldtypeFile.module on line 184


As I don't want to save messages on the server (so just sending an image), it shouln't be a security issue, I guess.

But is it possible to use an image field with the SimpleContactForm module? 

Share this post


Link to post
Share on other sites

Is it possible to create a custom spam message?  Along the lines of:

$modules->get('SimpleContactForm')->render(array(
	'spamMessage' => 'Custom Spam Message'
));

 

Share this post


Link to post
Share on other sites

Hi all. Great module, Justb3a. It was easy to set up and get working, submitting to the same page without Ajax. Now I'm trying to do it with Ajax but something's not right: when I submit a blank form (expecting errors for required fields), the form disappears from the page without any notice (and without refreshing, so it's sort of working). Same if I submit the form with all the fields filled-in (I expect a Success message and no form, as without Ajax). I don't get any console errors.

I've included the simplecontactform.js and initialised it per the instructions. My contact-page.php looks something like this:

<?php
if ($config->ajax) {
	$modules->get('SimpleContactForm')->render();
} else {
include("./includes/head.inc");
?>
... 
<div class="row row-2">
    <div class="col">
        <?php echo $page->body; ?>
        <div><!-- if I remove this div, the entire .col div disappears -->
            <?php echo $modules->get('SimpleContactForm')->render(); ?>
        </div>
    </div>
...
<?php
include("./includes/foot.inc");
} ?>

Am I doing something wrong here? Any suggestions are greatly appreciated.

Share this post


Link to post
Share on other sites

hi all,

i've got some trouble submitting the form.
in the logs i've got a "Date difference is out of range" - notification, every time a form has been submitted.

i double checked all available and required fields.

Do you have any idea?

Thanks

CF: 0.1.0
PW: 2.6.10

Share this post


Link to post
Share on other sites

Ok, I'm revisiting this. I guess I need to echo the form when I use Ajax:

if ($config->ajax) {
	echo $modules->get('SimpleContactForm')->render();
} else {

Now the form works fine with one exception: when I submit the form with required fields empty, ajax works and I get the red 'Missing required field' text, but when I submit a second time (with or without entering data in a required field), the page submits without Ajax (i.e., it refreshes). I suspect it's a jquery thing; any suggestions?

Here's the work-in-progress: http://bullocks-ley.strandoo.com/contact-us/. Thanks in advance.

 

Share this post


Link to post
Share on other sites

I'm trying to install the module on PW 3.0.42 but get an error:

Parse Error: syntax error, unexpected '[', expecting '}' (line 182 of /var/www/clubmoral_com/site/modules/SimpleContactForm/SimpleContactForm.module) 
 

Share this post


Link to post
Share on other sites

maybe you are using an old php version that does not support short array syntax [ ] ?

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

is there a clean way (not touching the module) to get fields labels instead of fields name in the email content text?

//Line 464
foreach ($this->allFields as $inputfield) {
	$message[] = $inputfield .': ' . $this->sanitizer->textarea($this->input->post->{$inputfield});
}

to something like this (not working...)?

//Line 464
foreach ($this->allFields as $inputfield) {
	$message[] = $inputfield->label .': ' . $this->sanitizer->textarea($this->input->post->{$inputfield});
}

thanks!

---

Amendment: Here's how I've approached to get this done, maybe someone else might be interested:

$message = array();
$message[] ='Some description...';
$message[] = '---';
$message[] = 'Name Surname: ' . $input->post->mail_name;
$message[] = 'Partecipa il 7 Luglio? ' . ($input->post->mail_option_01 == 1 ? 'Si.' : 'No.');
$date = new \DateTime();
$message[] = 'Date: ' . $date->format('Y-m-d');
$emailText = implode("\r\n", $message);

// in option array 
'emailMessage' => $emailText,

Cheers!

Share this post


Link to post
Share on other sites
On 7/19/2017 at 9:58 PM, szabesz said:

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.

I had a vicious [] operator not supported for strings (line 133 ….) - problem, after casually upgrading the module. I could not access the backend anymore. I had PHP 5.6 running and tried out 7.0 and 7.1 without success. Then in my desperation I resolved to fiddling the module code (I have pretty weak PHP knowledge).  In simplecontactform.module, line 133 , I changed

foreach (self::$additionalFields as $f) $allFieldsExtended[] = $f;

to

foreach (self::$additionalFields as $f) $allFieldsExtended = (array)$f;

and at least I was again able to keep on working. But I don't know, whether the module is working fine now, as I have my contact form without module.

Might help some poor guy one day...

Share this post


Link to post
Share on other sites

I had the same problem and used the solution above. The module works now without the error, but it just doesn't work. Doesn't send me an email when the form is filled and doesn't save the message as a page.

Share this post


Link to post
Share on other sites

Just a quick question, as I wasn't able to find any answer over this tread: is the scf module capable of manage file uploads (therefore send email with attachments)?

Because my form gets error as soon as I attach a fileUpload fieldtype to the form, so no way for me to manage it

Much appreciated

Share this post


Link to post
Share on other sites
On 6/14/2018 at 4:09 PM, Federico said:

Just a quick question, as I wasn't able to find any answer over this tread: is the scf module capable of manage file uploads (therefore send email with attachments)?

Because my form gets error as soon as I attach a fileUpload fieldtype to the form, so no way for me to manage it

Much appreciated

I've never used this module yet (so I don't know if that is possible or not), but as you didn't get any answer yet, you might be interested in my forms module: 

 

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 thomasaull
      Some time ago I created a site profile for creation of a REST API with ProcessWire. Since I kept struggeling with updating stuff between different projects which use this, I decided to convert it into a module. It is now ready for testing: https://github.com/thomasaull/RestApi
      Additionally I added a few small features:
      automatic creation of JWT Secret at module install routes can be flagged as auth: false, which makes them publicly accessible even though JWT Auth is activated in module settings To check things out, download and install the module and check the folder /site/api for examples.
      If you find any bugs or can think of improvements, please let me know!
    • By kongondo
      Sites Manager
       
      16 September 2018:
      FOR NOW, PLEASE DO NOT USE THIS MODULE IN A PRODUCTION SITE. A  RECENT ProcessWire UPDATE HAS BROKEN THE MODULE. I AM WORKING ON A FIX.
       
      ################
       
      Sites Manager is a module for ProcessWire that allows Superusers to easily create/install ProcessWire sites on the same serverspace the module is running in. Only Superusers can use the module. You can create both stand-alone and multi-sites.
       
      Single/Stand-alone Sites
      Stand-alone or single-sites are sites that will run in their own document root/directory with their own wire and site folders, .htaccess, index.php, etc. In other words, a normal ProcessWire site.
      Multiple Sites
      Multi-sites are sites that will run off one wire folder (shared amongst two or more sites) each having their own site folder and database. In this regard, it is important to note that Sites Manager is not in itself a multiple sites solution! Rather, it is a utility that helps you create multi-sites to be run using the ProcessWire core multiple sites feature. For more on this core feature, see the official ProcessWire documentation, specifically the solution referred to as Option #1.
      Option #1 approach requires the site admin to initially install ProcessWire in a temporary directory for each new site. The directory then needs to be renamed as site-xxx, where ‘xxx’ is any name you want to use to differentiate the installation from other sites, before it is moved to the webroot. For instance, site-mysite, site-another, site-whatever. In addition, the /wire/index.config.php file must be copied/moved to the webroot. Each time a site is added, the index.config.php has to be edited to add ‘domain’ => ‘site-directory’ key=>value pairs for the site. This process can become a bit tedious. This module aims to automate the whole multi-site site creation process.
      The module is based off the official ProcessWire installer. Creating a site is as simple as completing and submitting a single form! You also have the option to type and paste values or reuse a pre-defined install configuration.
       
      The module will:
      Install a ProcessWire site in your named directory, applying chmod values as specified
      Move the directory to your webroot
      Update/Create a Superuser account as per the submitted form, including setting the desired admin theme and colour
      For multi sites, update sites.json (used by index.config.php to get array of installed sites)
       
      For multi sites, the only difference in relation to the core multi-sites index.config.php is that this file is slightly different from the one that ships with ProcessWire.
      Download from GitHub: Sites Manager (Beta Release)
      Features
      Install unlimited number of sites in one (multi-sites) or independent (single-site) ProcessWire installs. Install by completing a Form, Typing or pasting in configurations or using pre-created install configurations. Choose an Admin Theme to auto-install along with the site installation. For single-sites installation, download, save and reuse ProcessWire versions of your choice. Install and maintain site profiles for reuse to create other sites. Create install configurations to speed up installation tasks. Client and server-side validation of site creation values. Edit uploaded profiles (e.g., replace profile file). Lock installed sites, configurations and profiles to prevent editing. Bulk delete items such as site profiles, installed site directories and/or databases (confirmation required for latter two). View important site details (admin login, chmod, etc). Links to installed sites home and admin pages. Timezones auto-complete/-suggest. Pre-requisites, Installation & Usage
      Please see the documentation.
      Technicalities/Issues
      Only Superusers can use the module.
      ProcessWire 2.7 - 3.x compatible
      Currently using ProcessWire 2.7 installer (install.php)
      For multi-sites, potential race condition when sites.json is being updated on a new site install vs. index.config.php accessing the json file?
      Not tested with sub-directory installs (for instance localhost/pw/my-site-here/)
      Currently not doing the extra/experimental database stuff (database charset and engine)
      Future Possibilities
      Install specified modules along with the ProcessWire install
      Profile previews?
      Credits
      @ryan: for the ProcessWire installer
      @abdus: for the index.config.php reading from JSON idea
      @swampmusic: for the challenge
      Video Demo
      Demo  showing how quick module works on a remote server [YMMV!]. Video shows downloading and processing two versions of ProcessWire (~takes 7 seconds) and installing a single/stand-alone ProcessWire 3 site using the new Admin Theme UI Kit (~2 seconds) on a remote server.
       
      Screens
      1

      2

       
       
    • By Robin S
      Breadcrumb Dropdowns
      Adds dropdown menus of page edit links to the breadcrumbs in Page Edit.

      Installation
      Install the Breadcrumb Dropdowns module. The module requires ProcessWire >= v3.0.83 and AdminThemeUikit.
      There is a checkbox option in the module config that determines if the breadcrumb dropdowns will include pages that the user does not have permission to edit.
      Features/details
      The module adds an additional breadcrumb item at the end for the currently edited page. That's because I think it's more intuitive for the dropdown under each breadcrumb item to show the item's sibling pages rather than the item's child pages. In the dropdown menus the current page and the current page's parents are highlighted in a crimson colour to make it easier to quickly locate them in case you want to edit the next or previous sibling page. Unpublished and hidden pages are indicated in the dropdowns with similar styling to that used in Page List. If the option to include uneditable pages is selected then those pages are indicated by italics with a reduced text opacity and the "not-allowed" cursor is shown on hover. There is a limit of 25 pages per dropdown for performance reasons and to avoid the dropdown becoming unwieldy. If the current user is allowed to add new pages under the parent page an "Add New" link is shown at the bottom of the breadcrumb dropdown. If the currently edited page has children or the user may add children, a caret at the end of the breadcrumbs reveals a dropdown of up to the first 25 children and/or an "Add New" link. Overriding the listed siblings for a page
      If you want to override the siblings that are listed in the dropdowns you can hook the BreadcrumbDropdowns::getSiblingsmethod and change the returned PageArray. For most use cases this won't be necessary.
      Incompatibilities
      This module replaces the AdminThemeUikit::renderBreadcrumbs method so will potentially be incompatible with other modules that hook the same method.
       
      https://modules.processwire.com/modules/breadcrumb-dropdowns/
      https://github.com/Toutouwai/BreadcrumbDropdowns
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour (excl vat).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Ken Muldrew
      I'm trying to get a short routine to run once per day that will look at some pages and send a reminder email when that customer's subscription (yearly) is about to expire. When I run the code in a template then it works without issue, but inside my lazycron service routine, I get an "Error: Uncaught Error: Call to a member function get() on null" as if the database cannot be found. My autoload module is just the sample HelloWorld module included with ProcessWire, editted to perform this task. The whole of it is included below (I've stripped out the code that generates the email because it never gets past $pages->find):
       
      <?php namespace ProcessWire;
      /**
       * ProcessWire 'LazyCronLoad'  module
       *
       */
      class LazyCronLoad extends WireData implements Module {
          public static function getModuleInfo() {
              return array(
                  'title' => 'LazyCronLoad', 
                  'version' => 1, 
                  'summary' => 'Just loads a lazy cron callback.',
                  'singular' => true, 
                  'autoload' => true, 
                  );
          }
          public function init() {
              // initialize the hook in the AutoLoad module
              $this->addHook('LazyCron::everyDay', $this, 'myHook');
              
          }
          public function myHook(HookEvent $e) {
              // called once per day
              wire('log')->save('user_activities',' lazy cron service routine');
                  $transport_pages = $pages->find("template=aggregate-entry, aggregate_type.title='Transport'");
                  foreach ($transport_pages as $page) {
                      if (($page->purchase_date + 30325800 < time()) && ($page->purchase_date + 30412600 > time())) { // between 351 and 352 days
                          wire('log')->save('user_activities', $page->id . ' email reminder sent');
                          // send email
                  }
              }
          }        
          
      }
      The first wire('log') shows up but the second one doesn't (the purchase_date condition is met (as demonstrated by running the code in a template close in time to when the lazycron routine executes)). The error log gives the Uncaught Error shown above. 
      I think this is a beginner's mistake with something obvious being missed and would be grateful for any assistance in fixing it.