Jump to content
bernhard

RockPdf - mPDF helper module

Recommended Posts

1 hour ago, dragan said:

Yeah... using inline SVGs works just fine... until you want to style fills or strokes via CSS.

Yeah, I also had this problem. I managed to style the icon using inline styles (doing that manually first), eg <path fill=red ... > but I couldn't find a way to control the size of the icon. I tried several approches. I even used the SVG as <img src=...> but then the coloring part didn't work any more. TTF now works find for both situations except for duotone icons (which would be nice but not necessary).

1 hour ago, dragan said:

I have the fonts both in site/templates/fonts/ as well as in site/assets/RockPDF/fonts/. I have now also placed them in site/modules/RockPdf/vendor/mpdf/mpdf/ttfonts, cleared modules cache, but the error persists.

Please follow the new readme exactly, I'm using the font https://www.fontsquirrel.com/fonts/rock-salt successfully in my PDF:

L8xga4w.png

This is my setup for this font + fontawesome pro:

    /** @var RockPdf $pdf */
    $pdf = $this->modules->get('RockPdf');
    $pdf->settings([
      'mode' => 'utf-8',
      'format' => 'A3-L',
      'dpi' => 300,
      'img_dpi' => 300,

      // fonts
      'fontdata' => (new \Mpdf\Config\FontVariables())->getDefaults()['fontdata'] + [
        'fancy' => [
          'R' => 'RockSalt.ttf',
          'I' => 'RockSalt.ttf',
        ],
        "fab" => [
          'R' => "fa-brands-400.ttf",
          'I' => "fa-brands-400.ttf",
        ],
        "fad" => [
          'R' => "fa-duotone-900.ttf",
          'I' => "fa-duotone-900.ttf",
        ],
        "fal" => [
          'R' => "fa-light-300.ttf",
          'I' => "fa-light-300.ttf",
        ],
        "far" => [
          'R' => "fa-regular-400.ttf",
          'I' => "fa-regular-400.ttf",
        ],
        "fas" => [
          'R' => "fa-solid-900.ttf",
          'I' => "fa-solid-900.ttf",
        ],
      ],
    ]);
    ...

Then I can just add the "fancy" class to get the RockSalt font. Don't forget to define the font in CSS:

.fancy { font-family: fancy; }

Does that help?

  • Like 1

Share this post


Link to post
Share on other sites

I have also recently used https://www.joypixels.com/ for converting emojis from UTF8 into something that works in a PDF. I use this to format messages created in a CkEditor field with the emoji plugin into a PDF summary of messages. It's not perfect, but seems to match almost all emojis from the CkEditor plugin.

Would be curious if anyone has any other suggestions on this front.

Share this post


Link to post
Share on other sites

@bernhard Thanks for the hints. I didn't notice I was uploading .otf files instead of .ttf - my 2nd facepalm moment yesterday...

As to the other issue I mentioned: I found out it's not related to RockPDF at all. I got some really weird issues with render() / wireRenderFile() - but only when I ran my code inside Tracy console. In a regular template everything works as expected. The issue was with matrix repeaters that are called with $child->render('offer_matrix') inside the template, where I use field template files* - suddenly PW wouldn't find these anymore.

* site/templates/fields/matrix.php
site/templates/fields/matrix/body.php
site/templates/fields/matrix/gallery.php
site/templates/fields/matrix/slideshow.php
etc.

Share this post


Link to post
Share on other sites

Did I already mention that I don't like repeaters? 😄 Glad you sorted it out 😉

Share this post


Link to post
Share on other sites
9 hours ago, dragan said:

but only when I ran my code inside Tracy console. In a regular template everyting works as expected.

I think you might have come up against this bug (https://github.com/processwire/processwire-issues/issues/511). If you think it is related, perhaps you could nudge Ryan on that issue as he seems to be ignoring my concerns on this, especially when it's a really easy fix.

  • Like 2

Share this post


Link to post
Share on other sites

Just updated the readme with an example of page cropping marks and bleed margins sometimes necessary for printing:

Page margins for print with cropmarks

// thx to https://stackoverflow.com/a/50245034/6370411
$pdf = $modules->get('RockPdf');
$pdf->settings([
  'mode' => 'utf-8',
  'format' => [214, 301],
  'img_dpi' => 300,
]);
$pdf->write('
<style>
  @page {
    /* regular A4 paper size is 210x297 */
    size: 211mm 298mm; /* trying some weird format to make sure it works */
    marks: crop;
  }
</style>
Content
');
d($pdf->save());

img

img

You see that the Trim Box shows our custom values 211x298 whereas the bounding box would show the paper size (214x301).

Real life example using RockPdf and RockLESS

// parts of RockPdfCalendar module

  public function init() {
    $this->w = $w = 420; // paper width in mm
    $this->h = $h = 297; // paper height in mm
    $this->b = $b = 2; // bleed in mm

    /** @var RockPdf $pdf */
    $pdf = $this->modules->get('RockPdf');
    $pdf->settings([
      'mode' => 'utf-8',
      'format' => [($w+2*$b), ($h+2*$b)],
      'dpi' => 300,
      'img_dpi' => 300,
    ]);
    $this->addBackground($pdf);
    $this->addStyles($pdf);

    $this->pdf = $pdf;
  }

  /**
   * Add Background PDF
   * @return void
   */
  public function addBackground($pdf) {
    $page = $this->pages->get("template=settings");
    $pdfs = $page->getUnformatted('calendarbackground');
    if(!$pdfs OR !$pdfs->count()) return; // no field or no file
    $pdf->set('SetDocTemplate', $pdfs->first()->filename);
  }

  /**
   * Add styles
   */
  public function addStyles($pdf) {
    /** @var RockLESS $less */
    $less = $this->modules->get('RockLESS');
    $less->vars = [
      'w' => $this->w."mm",
      'h' => $this->h."mm",
      'b' => $this->b."mm",
    ];
    $css = $less->getCSS(__DIR__ . "/style.less")->css;
    $pdf->write("<style>\n$css</style>");
  }

Then all you have to do is call $modules->get('RockPdfCalendar')->show() to render the pdf in the browser 🙂

  • Like 1

Share this post


Link to post
Share on other sites

Just discovered a technique that can save you lots of time and headache!

Debugging can be a pain when creating PDFs, but it gets a lot simpler if you use this handy trick. I'm hooking into pageNotFoud to create the pdf:

$this->addHookBefore('ProcessPageView::pageNotFound', $this, 'renderCalendar');

If everything goes right, the calendar shows up in the browser:

xFg5SxG.png

But there's one problem: We don't know anything about errors, warnings, etc. Logging them into the pw logs is a pain compared to the Tracy Debugbar, so here's how you can have both - the generated HTML of the PDF and the debug bar:

We create the PDF BEFORE the 404 is thrown, but we create the HTML AFTER the 404:

$this->addHookBefore('ProcessPageView::pageNotFound', $this, 'renderCalendar');
$this->addHookAfter('ProcessPageView::pageNotFound', $this, 'renderCalendarDebug');

  /**
   * Render PDF calendar
   */
  public function renderCalendar(HookEvent $event) {
    $url = $event->arguments(1);
    $cal = $this->modules->get('RockPdfCalendar');

	// check url etc
    ...
    // generate the PDF
    $pdf = $cal->pdf; /** @var RockPdf $pdf */
    ...

    $title = 'Kaumberg Kalender ' . date("Y-m", $start);
    $pdf->set('setTitle', $title);
    $pdf->write($cal->render());

    // if html get parameter is set we return the html output
    $this->session->calHTML = null;
    if($this->user->isSuperuser() AND $this->input->get->html) {
      $this->session->calHTML = $pdf->html();
      return;
    }
    $pdf->show("$title.pdf");
    die();
  }

  /**
   * Output calendar for debugging
   * @return void
   */
  public function renderCalendarDebug(HookEvent $event) {
    if($this->session->calHTML) $event->return = $this->session->calHTML;
  }

D6vvaPD.png

😎

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for another great module @bernhard

Wanted to share my experiences changing from Pages2PDF to RockPdf. Wasn't quite as straightforward as I'd hoped. Such is life, but I got there. Pages2Pdf uses mPDFv5+ while RockPdf uses mPDFv7+ and I needed some of the newer features.

Things Iearned along the way:

1. If you need to use @page, you lose everything in the template 

$pdf->set('header', '...');

 settings. This has nothing to do with RockPdf but a 'feature' of mPDF

2. It's much easier to add custom fonts to RockPdf than Pages2PDF

3. You can display images in a circle using background-image but they don't print so that's not helpful, LOL

This is NOT a full tutorial but hopefully will give you some pointers on how I got RockPdf working for a fairly specific PDF design.

RockPdf template settings:

<?php

    $pdf = $modules->get('RockPdf');

    $pdf->settings([
        'fontdata' => (new \Mpdf\Config\FontVariables())->getDefaults()['fontdata'] + [
             "montserrat" => [
                'R' => "montserrat-regular.ttf",
                'B' => "montserrat-bold.ttf",
            ],
            "montserratlight" =>[
                'R' => "montserrat-light.ttf"
            ],
            "montserratthin" => [
                'R' => "montserrat-thin.ttf"
            ]
        ],

        'defaultheaderline' => 0,

        'font_size' => 9,
        'mode' => 'utf-8',
        'font' => 'montserrat',
        'page_format' => 'A4',
    ]);

    $css = wireRenderFile($config->paths->templates . 'RockPdf/styles-v3.css');
    $pdf->write("<style>" . $css . "</style>");

    $body = wireRenderFile($config->paths->templates . 'RockPdf/profile_pdf_cv-v3.php');
    $pdf->write($body);

    $pdfFile = $sanitizer->pageName($profile->title) . "-" . $profile->id . ".pdf";

    $pdf->show($pdfFile);
    die();

//    Remove old Pages2PDF settings
//    $mpdf->markupMain   = $config->paths->templates . 'RockPdf/profile_pdf_cv-v3.php';
//    $mpdf->markupHeader = $config->paths->templates . 'RockPdf/_header-v3.php';
//    $mpdf->markupFooter = $config->paths->templates . 'pages2pdf/_footer-v2.php';
//    $mpdf->cssFile = $config->paths->templates . 'RockPdf/styles-v3.css';
//    $mpdf->pageOrientation = 'P';
//    $mpdf->pageFormat = 'A4';
//    $mpdf->topMargin = 9.5;
//    $mpdf->rightMargin = 0;
//    $mpdf->bottomMargin = 9;
//    $mpdf->leftMargin = 0;
//    $mpdf->headerMargin = 0;
//    $mpdf->footerMargin = 0;
//    $mpdf->fontSize = 9;
//    $mpdf->mode = 's';
//    $mpdf->font = 'montserrat';

Header code:

    <div style="
        background-color: #007ee5;
        height: 10mm;
        margin: 0;
        top: 0;
        left: 0;
        right: 0;
        width: 100%;
">
    </div>

Page layout code:

<?php

// header is the same on all pages but need more spacing on all pages except the first
$header = wireRenderFile($config->paths->templates . 'RockPdf/_header-v3.php');
?>
<htmlpageheader name="myHeaderFirst" style="display:none">
    <?=$header?>
</htmlpageheader>

<htmlpageheader name="myHeader" style="display:none">
    <?=$header?>
</htmlpageheader>

<sethtmlpageheader name="myHeaderFirst" value="on" show-this-page="1" />
<sethtmlpageheader name="myHeader" value="on" />



<div class="user-dets">

CSS:

/*
Additional fonts added to:
site/assets/RockPdf/fonts

*/
@page {
    margin: 15mm 0 0 0; /* <any of the usual CSS values for margins> */
    /*(% of page-box width for LR, of height for TB) */
    margin-header: 0; /* <any of the usual CSS values for margins> */
    margin-footer: 9mm; /* <any of the usual CSS values for margins> */
    marks: none;/*crop | cross | none*/
    header: html_myHeader;
}

@page :first {
    margin: 9.5mm 0 0 0; /* <any of the usual CSS values for margins> */
    /*(% of page-box width for LR, of height for TB) */
    margin-header: 0; /* <any of the usual CSS values for margins> */
    margin-footer: 9mm; /* <any of the usual CSS values for margins> */
    marks: none;/*crop | cross | none*/
    header: html_myHeaderFirst;

}

Hope this is useful.

Cheers
psy

 

  • Like 2

Share this post


Link to post
Share on other sites

Thx for sharing your experience @psy 🙂 

43 minutes ago, psy said:

Wasn't quite as straightforward as I'd hoped. Such is life, but I got there.

mPdf is unfortunately not really a pleasure to work with 😞 It feels a bit like designing websites 20 years ago with lots of custom table layouts, custom styles, paddings, margins etc... But as you said: I also got there almost everytime and I didn't find a better solution yet.

Writing your styles as LESS can be helpful because you can create simple custom classes for any element and to the complex styling in CSS. Using LESS ensures that your style stays easy to maintain because you can use class inheritance and variables. RockPdf plays really well together with RockLESS. I added an example to the readme:

Combine RockPdf and RockLESS

$pdf = $modules->get('RockPdf');
$less = $modules->get('RockLESS');
$style = "
@padding-s: 10pt;
.border { border: 1pt solid #afafaf; }
.hello { .border; color: blue; padding-top: @padding-s; }
.world { .border; color: red; padding-top: @padding-s * 2; }
";
$css = "\n".$less->parse($style);
$pdf->write("<style>$css</style>");
$pdf->write("<div class='hello'>hello</div>");
$pdf->write("<div class='world'>world</div>");
d($pdf->save());

img

img

This is the result of $pdf->html()

<style>
.border {
  border: 1pt solid #afafaf;
}
.hello {
  border: 1pt solid #afafaf;
  color: blue;
  padding-top: 10pt;
}
.world {
  border: 1pt solid #afafaf;
  color: red;
  padding-top: 20pt;
}
</style>
<div class='hello'>hello</div>
<div class='world'>world</div>

 

  • Like 3

Share this post


Link to post
Share on other sites
8 hours ago, bernhard said:

mPdf is unfortunately not really a pleasure to work with 😞 It feels a bit like designing websites 20 years ago with lots of custom table layouts, custom styles, paddings, margins etc...

@bernhard Oh so true! Pdf's can look different between browser views and Acrobat Reader too. 

  • Like 1

Share this post


Link to post
Share on other sites
On 4/22/2020 at 10:18 PM, bernhard said:

Writing your styles as LESS can be helpful because you can create simple custom classes for any element and to the complex styling in CSS.

Hi @bernhard

Yes, RockLESS, SCSS and other CSS preprocessors can be useful. One thing I learned the hard way however is that the header is loaded before any HTML or CSS. The only way I could style the header to look as intended was with inline styles. I certainly used classes with the limited CSS styling available from mPDF in the body. Maybe there's a better way, just didn't have the time or patience to explore.

Another limitation was with tables... I needed a centered heading and left aligned text within a table cell. Nope, if the <td> is left aligned, so is everything within the cell. Had to revert to divs which had an impact on the design. Told the graphic designer to live with it - it is what it is! LOL

Having said that, love your module and mPDF, even with its constraints, is still the best HTML to PDF converter.

 

  • Like 2

Share this post


Link to post
Share on other sites

Aligning things is tricky, but most things work using nested tables (that's what I meant when saying "like 20 years ago"). What about this?

$pdf = $modules->get('RockPdf');
$table = '
<style>
td { border: 1pt solid black; }
.center {text-align: center;}
</style>
<table>';
$table .= '<tr><td class="center">foo</td><td>bar</td></tr>';
$table .= '<tr><td>Donec vitae sapien ut libero</td><td>Donec vitae sapien ut libero</td></tr>';

$td = "<table><tr><td class='center'>sub-heading</td></tr><tr><td>Phasellus ullamcorper ipsum rutrum nunc</td></tr></table>";
$table .= "<tr><td>Donec vitae sapien ut libero</td><td>$td</td></tr>";

$table .= '</table>';
$pdf->write($table);
d($pdf->save()); // generate pdf

zEj9LUg.png

  • Like 2

Share this post


Link to post
Share on other sites

Yep, that's a solution - 20yrs ago HTML/CSS 😂 

In my particular case there are other factors. The user can choose to include/exclude bits which makes it an ugly, logistical nightmare.

34 minutes ago, psy said:

Told the graphic designer to live with it - it is what it is! LOL

 

  • Like 1

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 Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...