Wanze

Pages2Pdf

Recommended Posts

Hi @dragan

16 minutes ago, dragan said:

Haven't used this module myself yet, but mpdf has a TOC function: https://mpdf.github.io/what-else-can-i-do/table-of-contents.html

looks good, I will play with it and see what I can do 

As of the prepend/append custom php files to the foreach pdf generation, nevermind - I've just found a way which is working just fine:

$pdf->markupMain = '';
$pdf->markupMain .= wireRenderFile($this->config->paths->ProcessBook2pdf . '/templates_book/_coverFront.php'); //front page
foreach($pageArray as $item) {
	$pdf->markupMain .= wireRenderFile($this->config->paths->ProcessBook2pdf . '/templates_book/default.php', ["page" => $item]); //actual book content
}
$pdf->markupMain .= wireRenderFile($this->config->paths->ProcessBook2pdf . '/templates_book/_coverBack.php'); // back page

 

Share this post


Link to post
Share on other sites

Stuck with pw-modal / pw-panel opening of generated pdf.

I have a pageArray containing selected pages, if I export the array in pdf from the current page (thus replacing the custom module page), it is all fine and correct.

If I use the same setting and try to export the pdf in modal window (by adding pw-modal in the button), well the modal window pops up but it show the frontend website 404 page, whereas in panel window (by adding pw-panel in the button) the pdf is rendered in panel but with missing pieces (not reading the $page instance!).

this is how I send the page array to feed the pages2pdf module:

foreach($pageArray as $item) {
	$pdf->markupMain .= wireRenderFile($this->config->paths->ProcessBook2pdf . '/templates_book/default_panel.php', ["page" => $item]);
}

therefore the problem is that even though I state ["page" => $item] from the pageArray, only in both modal and panel windows the $page variable in foreach loop is just the current module page!

@Wanze do you know why I cannot pass the pageArray to the pages2pdf to feed the modal/panel window? thanks

Share this post


Link to post
Share on other sites

Anyone already tried the module with admin page/Process modules ?

I can get it working, but only by hacking the module.

 

On 17/02/2018 at 5:41 PM, Federico said:

therefore the problem is that even though I state ["page" => $item] from the pageArray, only in both modal and panel windows the $page variable in foreach loop is just the current module page!

Not surprised here, did you tried with another var name ? ($page is a reserved word in ProcessWire)

 

 

@Wanze With PHP-7.0.10 I get those warning :

Quote

PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; 
mPDF has a deprecated constructor in .../wwwroot/site/modules/Pages2Pdf/mpdf/mpdf.php:66

PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; 
grad has a deprecated constructor in .../site/modules/Pages2Pdf/mpdf/classes/grad.php:3

PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; 
form has a deprecated constructor in .../site/modules/Pages2Pdf/mpdf/classes/form.php:3

PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; 
cssmgr has a deprecated constructor in .../site/modules/Pages2Pdf/mpdf/classes/cssmgr.php:3

 

Edit:   fixed by replacing mpdf with the version 6.1

Share this post


Link to post
Share on other sites

 

1 hour ago, flydev said:

Not surprised here, did you tried with another var name ? ($page is a reserved word in ProcessWire)

@flydev I've tried with different variable than $page, same results. Please note that ["page" => $item] inside the above foreach loop works correctly if I submit the form, as the pdf is generated correctly in the new browser tab, with all $page as $items taken from the the pageArray. I mean, all php functions are working OK when the form is submitted, but I can't submit the form on a modal window.

The point here is that if I add pw-panel to the button class, then the foreach loop doesn't even fire, totally skipped! so I guess the following argument:

- The pw-panel and pw-modal windows don't let php foreach to fire (most likely because there is no real form submit), they both work just fine with only direct php statements. Moreover, $page variable is just the current module page.

 

Share this post


Link to post
Share on other sites
On 12/26/2017 at 10:10 AM, Macrura said:

For anyone who is having the red x problem with images, I was able to solve these missing images by doing 2 things:

1) If you are on https, convert image references to absolute (i think this is because the library uses http when replacing image references ?)


$rootPath = $pages->get(1)->httpUrl;
$body = str_replace("/site/assets/", $rootPath . "site/assets/" , $page->body);

2) Manually create the temp folder ("WirePDF") inside site/assets/cache/ – this folder did not exist and therefore the core library was throwing image errors.

Once these 2 things were completed, now the PDFs generate with the images correctly

Doesn't work for me :( .. and this doesn't work either:

<img src='<?=$config->urls->templates."images/logo.png"?>'>
/* or usign the url directly either */
<img src='http://www.domain.com/site/templates/images/logo.png'>

Before work's and the path is correct because in the other templates prints well

Everything happened after updating the module.

Share this post


Link to post
Share on other sites

What happens if you exchange the png file with a jpeg file?

Share this post


Link to post
Share on other sites

Did anyone successfully use @page in the stylesheet to e.g. set page size or margins? I don’t see anything happen if I add the following code block to templates/pages2pdf/styles.css:

@page {
    size: A5;
    margin: 10mm;
}

I’m using the dev branch of Pages2Pdf (mPDF v6.1).

Share this post


Link to post
Share on other sites
5 hours ago, charger said:

I don’t see anything happen if I add the following code block to templates/pages2pdf/styles.css:


@page {
    size: A5;
    margin: 10mm;
}

I don't think this works. The size property for @page only accepts the values "auto", "portrait", "landscape" or an absolute width/height tuple. Named page formats aren't listed as supported.

Share this post


Link to post
Share on other sites
16 hours ago, BitPoet said:

I don't think this works. The size property for @page only accepts the values "auto", "portrait", "landscape" or an absolute width/height tuple. Named page formats aren't listed as supported.

You’re right. Bad example. But it also doesn’t work with width and height values like this:

@page {
    size: 100mm 150mm;
}

 

Share this post


Link to post
Share on other sites

@Wanze Would it be possible to support:

$config->pagefileSecure = true;

If it is already supported? What am I supposed to do? I'm getting "missing image" icons only:

496338021_Bildschirmfoto2018-06-20um17_06_20.png.14e862ed671d98916eaca3775e3b8172.png

If i disable `$config->pagefileSecure` everything's working fine and I see the images in the PDF.

Warning:
Don't try to use image resizing and dynamically disable `$config->pagefileSecure` while rendering PDF's.
It will create the image variations in an unprotected directory.

Quick Workaround:

$filePath = $image->size(0, 100)->filename;
$fileType = mime_content_type($filePath);
$fileContents = file_get_contents($filePath);
$base64 = base64_encode($fileContents);
$out[] = "<img src=\"data:image/{$fileType};base64,{$base64}\">";

 

Share this post


Link to post
Share on other sites
On 12/26/2017 at 9:10 AM, Macrura said:

For anyone who is having the red x problem with images, I was able to solve these missing images by doing 2 things:

1) If you are on https, convert image references to absolute (i think this is because the library uses http when replacing image references ?)


$rootPath = $pages->get(1)->httpUrl;
$body = str_replace("/site/assets/", $rootPath . "site/assets/" , $page->body);

2) Manually create the temp folder ("WirePDF") inside site/assets/cache/ – this folder did not exist and therefore the core library was throwing image errors.

Once these 2 things were completed, now the PDFs generate with the images correctly

This is still an issue.

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 bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By OLSA
      Hello for all,
      ConfigurationForm fieldtype module is one my experiment from 2016.
      Main target to build this module was to store multiple setup and configuration values in just 1 field and avoid to use 1 db table to store just single "number of items on page", or another db table to store "layout type" etc. Thanks to JSON formatted storage this module can help you to reduce number of PW native fields in project, save DB space, and reduce number of queries at front-end.
      Install and setup:
      Download (at the bottom ), unzip and install like any other PW module (site/modules/...). Create some filed using this type of field (ConfigurationForm Fieldtype) Go to field setup Input tab and drag some subfields to container area (demo). Set "Name" and other params for subfields Save and place field to templates ("Action tab") How to use it:
      In my case, I use it to store setup and configurations values, but also for contact details, small content blocks... (eg. "widgets").
      Basic usage example:
      ConfigForm fieldtype "setup" has subfields:
      "limit", type select, option values: 5, 10, 15, 20
      "sort", type select, option values: "-date", "date",  "-sort", "sort"
      // get page children (items) $limit = isset($page->setup->limit) ? $page->setup->limit : 10; $sort = isset($page->setup->sort) ? $page->setup->sort : '-sort'; $items = $page->children("limit=$limit, sort=$sort");  
      Screenshots:


       
      Notes:
      Provide option to search inside subfields Provide multilanguage inputs for text and textarea field types Provide option for different field layout per-template basis Do not place/use field type "Button" or "File input" because it won't works. Please read README file for more details and examples Module use JSON format to store values. Text and textarea field types are multilanguage compatible, but please note that main target for this module was to store setup values and small content blocks and save DB space. Search part inside JSON is still a relatively new in MySQL (>=5.77) and that's on you how and for what to use this module.
      Thanks:
      Initial point for this fieldtype was jQuery plugin FormBuiled and thanks to Kevin Chappel for this plugin.
      In field type "link" I use javascript part from @marcostoll module and thanks to him for that part.
      Download:
      FieldtypeConfigForm.zip
      Edit: 14. August 2018. please delete/uninstall previously downloaded zip
      Regards.
         
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
    • By Thomas Diroll
      Hi guys I'm relatively new to PW and just finished developing a page for a client. I was able to include all necessary functionality using the core fieldtypes but now I it seems that I need to extend them with a custom one. What I need is a simple button, that copies the absolute url (frontend not PW-backend) of the page which is currently edited to the clipboard. As this feature is only needed inside a specific template, I tend to use a custom fieldtype which provides this feature. I've been looking inside the core modules code (eg. FieldtypeCheckbox.module) but I don't really get the structure of it and how its rendered to the admin page. I also didn't find a lot of tutorials covering custom fieldtypes.
      Maybe some of you could give me some tips on how to write a basic custom fieldtype that renders a button which copies the value of
      page->httpUrl() to the clipboard using JS. Thanks!
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour.
       
      Changelog
      180730 support subdir installations 180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

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

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