Jump to content
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

Hello,

how can I change the markup for my form from this:

Spoiler

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

$options = array(
  'markup' => array(
    'list' => "<div {attrs}>{out}</div>",
    'item' => "<p {attrs}>{out}</p>"
  ),
  'classes' => array(
    'form' => 'form form__whatever',
    'list' => 'list-item'
  )
);

echo $scf->render($options); ?>

 

to this:

Spoiler

                <form method="post" id="contactform" name="contactform" class="contact-form" action="mail/contact.php">
                  <div class="col-md-6 margin-15">
                    <div class="form-group">
                      <input type="text" id="name" name="name"  class="form-control input-lg" placeholder="Name*">
                    </div>
                    <div class="form-group">
                      <input type="email" id="email" name="email"  class="form-control input-lg" placeholder="Email*">
                    </div>
                    <div class="form-group">
                      <input type="text" id="phone" name="phone" class="form-control input-lg" placeholder="Phone">
                    </div>
                  </div>
                  <div class="col-md-6">
                    <div class="form-group">
                      <textarea cols="6" rows="7" id="comments" name="comments" class="form-control input-lg" placeholder="Message"></textarea>
                    </div>
                  </div>
                  <div class="col-md-12">
                    <input id="submit" name="submit" type="submit" class="btn btn-primary btn-lg pull-right" value="Submit now!">
                  </div>
                </form>

Thank you

R

Share this post


Link to post
Share on other sites

Hi there!

Great module. I'm having trouble submitting it inside of a slide in element. I have the form in a modal window just a overlay div that covers the screen.

Initially I have a div with a width of 0 that expands to 100% when you click a button.

When I submit the form the modal reverts to a width of 0. Not sure why I am submitting by ajax. I have changed the setting to so there is no redirect.

 

Can anyone help?

 

 

 

 

Share this post


Link to post
Share on other sites

Hi again. Great module; I'm using it again and wondered about  this bit of code in your documentation:

$this->addHookBefore('Inputfield::render', function(HookEvent $event) {
  if ($this->page->template->name === 'contact') { // adapt template name to compare with
    $inputfield = $event->object;
    $inputfield->addClass('col-sm-8');
    $event->return = $inputfield;
  }
});

This adds the 'col-sm-8' class to every field input. How can I just single out a specific type of input to add a class to? Specifically, a <select> input. (I need the class for some jquery stuff). Thanks in advance. P

Share this post


Link to post
Share on other sites

@strandoo

You can try this code

$this->addHookBefore('Inputfield::render', function(HookEvent $event) {
  if ($this->page->template->name === 'contact') { // adapt template name to compare with
    $inputfield = $event->object;
    if($inputfield instanceof InputfieldSelect) $inputfield->addClass('col-sm-8');
    $event->return = $inputfield;
  }
});

or this

$this->addHookBefore('InputfieldSelect::render', function(HookEvent $event) {
  //...
}

 

Share this post


Link to post
Share on other sites

@gebeer Wow. That was fast AND very helpful. I just changed 'Inputfield::render' to 'InputfieldSelect::render' as you suggested. I don't know why I didn't try that; I'll try harder next time! Cheers.

  • Like 1

Share this post


Link to post
Share on other sites

i’m using a page reference field (single page) in a dropdown select in my simpleContactForm. in the email I’m sending, the selected page is referenced by its ID … how can i email page->title instead?

i tried two routes:
1. simpleContactForm populates option values with page id’s, if i could replace these with page names; that would be a step in the right direction … but i don’t know how to accomplish this.
2. (preferred) the email I’m sending, outputs: %scf_select_event%, being the pageID … how can i change this to scf_select_event->title

hopefully someone can point me in the right direction
many thanks

Share this post


Link to post
Share on other sites
On 5/3/2018 at 11:59 AM, strandoo said:

when I submit a second time (with or without entering data in a required field), the page submits without Ajax (i.e., it refreshes).

Did you figured it out?

Share this post


Link to post
Share on other sites
Posted (edited)
On 7/6/2019 at 1:03 AM, PWaddict said:

Did you figured it out?

Yeah, pretty much. It's not as clean as I would like it, but it works fine.

I discovered that it works fine if I include the necessary javascript in the $config->ajax part of my page, then it works as expected:

if ($config->ajax) {
	$scf = $modules->get('SimpleContactForm');
	echo "<div>{$scf->render()}</div>"; // if not enclosed in a div, my column formatting was getting lost
	echo "<script src=\"{$config->urls->siteModules}SimpleContactForm/resources/jquery.simplecontactform.js\"></script>";
	echo "<script src=\"{$config->urls->templates}js/main.js\"></script>"; // including the 2 scripts made it work.
} else {
	... // full page with contact form

The only downside is that every time the form submitted with missing required fields (i.e., to throw an error), the 2 script includes get added to the form section. This makes for redundant/duplicate scripts called. Not ideal, but it works. If anyone know why this happens – or a way around it – I'd love to hear it.

Edit: Looking at other sites where I've used this module, I realise that I only need to include the main.js script (where I have the $.simplecontactform($('.js-simplecontactform')); line). Also, if I put that <script ... main.js\"></script> line inside the <div>, it works fine without duplicating the script on every error.

Edited by strandoo
added info to improve post.
  • Thanks 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...