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
On 10/17/2018 at 7:36 PM, charger said:

Did anyone else encounter problems with `show()` and `download()`? If I use them, all I get is blank pages resulting in an invalid PDF. The `save()` function works as expected though.

I’m running PW 3.0.98 with PHP 7.1.12 and RockPdf 1.0.1

For anybody facing this problem which in my case invalid pdf will generate error  "one or more XREF chunks were not found".
Solved it by placing the rockpdf instance php code block on top of anything else.

Share this post


Link to post
Share on other sites
2 hours ago, pwfans said:

Solved it by placing the rockpdf instance php code block on top of anything else.

Thx for the report. Can you please give us some more details, I don't really understand what you mean 🙂 

Share this post


Link to post
Share on other sites

@bernhard sorry, i make you confuse by my bad english 😭

I mean, try to place this :

<?php
$pdf = $modules->get('RockPdf');
$pdf->write("pdf content");  
$pdf->show();
?>

before any html content, at first line if possible.

Share this post


Link to post
Share on other sites

Hi @bernhard,

thank you for the module, which is helpful in keeping the project structure clean.

I also use the MPDF barcode component to generate QR codes of the page URL.
For this it was necessary to add the MPDF QR Code library to the RockPDF module using following command inside the /site/modules/RockPdf directory:

$ composer require mpdf/qrcode

It would be great if this was already available in the basic version of the module so as not to jeopardize the upgradeability.
What do you think, is it interesting to add or rather an unusual special case?

Share this post


Link to post
Share on other sites

Thx @axelino and welcome to the forum 🙂 

I tried to test the library quickly but could not make it work. Could you please provide a PR and usage instructions for the readme so that I can check it quickly? Then I'm happy to add it to the module 🙂 

Share this post


Link to post
Share on other sites

Hi @bernhard, thanks for the welcome and your fast reply! 🙂
I'm happy you want to add it and try to prepare a PR with usage instructions tomorrow or monday.

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 David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • 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 acronyms 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 tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • 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 Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...