Jump to content
Wanze

Pages2Pdf

Recommended Posts

Is it possible to include child pages in the PDF??

I have created a pricelist and each item of the pricelist is a single page. On the pricelist template I output all child pages with a foreach loop. The result is my pricing table.

Unfortunately on the PDF the content of the child pages is not visible, so I have an empty page.

Share this post


Link to post
Share on other sites

I've not used the Pages2PDF module by now, but you can use the WirePDF module, which is part of the installation, to render any html content you pass to it. 

  • Like 1

Share this post


Link to post
Share on other sites

Is it possible to include child pages in the PDF??

I have created a pricelist and each item of the pricelist is a single page. On the pricelist template I output all child pages with a foreach loop. The result is my pricing table.

Unfortunately on the PDF the content of the child pages is not visible, so I have an empty page.

You have the full ProcessWire API available in your Pages2Pdf templates.

Did you output the children also in the template inside "site/templates/pages2pdf"? If so, they should appear in the PDF files.

Only problem I can think of is that the PDF enginge can't handle your markup, you might need to simplify the HTML. But for testing purposes, you can also just list the prices-pages in a simple list. If it does still not work, please post the content of your pages2pdf "pricelist" template.

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

Did you output the children also in the template inside "site/templates/pages2pdf"? If so, they should appear in the PDF files.

This was the problem. I have forgotten to include the child pages template. Thanks Wanze

  • Like 1

Share this post


Link to post
Share on other sites

Hi Wanze,

thanks for this cool module! this really did save some headscratching for a current project I'm working on.

Do you have a tip how I can include my ./template/_init.php file for the "pdf"template? I need to use some vars that are declared site-wide in this _init.php file.

I'm sure this can easily be achived, esp. after seeing that there's a hookable createPDF function… but I'm not sure how this "prepend file to template" would be addressed…? Sorry if this is something totally obvious, I'd glady take a rtfm link, as well ;-)

cheers
Tom

Share this post


Link to post
Share on other sites

Hi Tom,

Thanks. Simplest solution would be to include the file inside your PDF templates, like this:

// We are in a template file under /site/templates/pages2pdf/, include /site/templates/_init.php
include('../_init.php');

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

ok, I forgot to mention that I need to use some of the "_init.php" vars in the _header/_footer.php inside ./pages2pdf.

I tried to include the _init there, and then in the template as you suggested, but a simple var_dump for one of the "_init" variables returns empty.

to give you a bit of background; I use thiis approach: https://processwire.com/talk/topic/10447-using-translatable-strings-across-template-files/#entry99012

for the template translation thing, but somehow the templates inside pages2pdf are ignorant of the "_string.php" file.

I have some "translateble" strings in _header/footer.php, but they're ignorant of the translations. :-)

cheers

Tom

UPDATE: Ok, after some more debugging I see that the  include_once('../_init.php') works like you presumed, the vars are there. something else must interfer with the translation thing, at least it is not caused by a not-working include. sorry for the bother.

UPDATE 2: After even more debugging and testing; the _init needs to be included in all three php files: _header.php, page.php, _footer.php - it seems to be scoped to that file alone where it is included. I somehow was expectng that the incude in the _header.php alone would be enough, but after reflecting how the PDF is looking -- where _header and _footer are repeated on every "page" of the PDF -- it makes sense that this didn't work out. However, I think having three identical includes that are repeatetly called during the creation of the PDF is not really the best way to go about this, even if it now works… :-) ?

  • Like 1

Share this post


Link to post
Share on other sites

@Webrocker

Glad it works for you!

However, I think having three identical includes that are repeatetly called during the creation of the PDF is not really the best way to go about this, even if it now works…  :-) ?

I don't see a problem here if your include does not do some heavy stuff, in this case you should cache the results. But I think there's no easy alternative... ProcessWire does the same for you in the background when you're using the prependTemplate file option, it is just included "automaticaly" in every ProcessWire template. I could check if this setting is enabled and include the prepended file in the background, but this might not be desired in another situation :)

Share this post


Link to post
Share on other sites

WirePdf's $pdf->mpdf doesn't return the mpdf instance for me and a quick look through the code seems to confirm that. 

  • Like 1

Share this post


Link to post
Share on other sites

had also problems with that so i included it manually... i thought i was doing something wrong with those instructions of the module's page

For advanced usage, you can also get the mPDF instance from the module:

$pdf = $modules->get('WirePDF');
// Get mPDF instance
$mpdf = $pdf->mpdf;
// Set back mPDF instance
$pdf->mpdf = $mpdf;

Share this post


Link to post
Share on other sites

Hi Wanze,

It looks like the current version of this can't be installed using PW's built-in by class name feature, because it tries to install Pages2df before WirePDF. It works fine if you use the URL option and point it to the zip on Github though because that way it downloads and extracts and shows you both modules with the option to install WirePDF.

Share this post


Link to post
Share on other sites

Hi Adrian,

Thanks for the information. Do you know if I can solve this somehow? Seems like ProcessWire should look for the missing dependency as well when using the classname installation-mode, but I'm not sure if this is easy possible.

Cheers

Edit: Thanks LostKobrakai for opening the issue

Share this post


Link to post
Share on other sites

You could switch dependencies, where Pages2Pdf installs WirePDF, instead of requiring it to be installed previously.

  • Like 1

Share this post


Link to post
Share on other sites

Hi guys,

This is a bug. It should work if you add $this->initPDF() before this line: https://github.com/wanze/Pages2Pdf/blob/master/WirePDF.module#L91

I will fix it and update the module.

Cheers

That's really a bigger thing, as the whole mpdf instance is being overwritten on save, if one is using pageOrientation or something other "constructor argument".

Share this post


Link to post
Share on other sites

Hi there,

I can't guarantee that this is an issue with pages2pdf, but let me point to my last Forum post : https://processwire.com/talk/topic/11065-urlsegment-issue-string-vs-integer/

Footer inclusion seems to mess things up. Maybe I'm missing something, though. If so, I'm sorry. (It sounds surprising that I would be the only one facing such a problem).

Share this post


Link to post
Share on other sites

It would be a nice addition if one could directly use mpdf's functions on the wirepdf module instead of retrieving and setting the mpdf instance every time one does need a native functionality.

Share this post


Link to post
Share on other sites

I'm having problem with this module not using translations in template __("Text"). It's always default language for those strings. 


Ah sorry, I forgot that the pages2pdf template aren't translated yet :)

Share this post


Link to post
Share on other sites
That's really a bigger thing, as the whole mpdf instance is being overwritten on save, if one is using pageOrientation or something other "constructor argument".

I removed the check to constructor arguments with the latest release on the dev branch. However, you always need to set the config options before saving the PDF file.

It would be a nice addition if one could directly use mpdf's functions on the wirepdf module instead of retrieving and setting the mpdf instance every time one does need a native functionality.

This feature is available on the dev branch, you should now be able to call any method on the mPDF instance directly trough WirePDF (as long as the method does not exist as public method on WirePDF already). Technically setting back the mPDF instance was not needed before, I removed this from the ReadMe.

If you find any time to get a copy from the dev branch and check if everything works for you, that would be great! :)

Cheers

  • Like 2

Share this post


Link to post
Share on other sites

Where to direct a custom PDF File Path in the WirePDF config to, e.g. for folder templates? Don t get it running.

Share this post


Link to post
Share on other sites

@Spica,

I don't understand your question, are you trying to set the path to the template that defines the markup of the PDF?

$pdf = $modules->get('WirePDF');
$pdf->markupMain = $config->paths->templates . 'pdf_template.php';

Share this post


Link to post
Share on other sites

Sorry, typing error. I meant the CSS File Path in the WirePDF config mask declared with "Enter path and filename of a CSS file containing default styles to be used by mPDF for the HTML markup" for substituting the templates/pages2pdf/styles.css.

e.g ../../templates/vendor/my.css, or templates/vendor/my.css does not succeed.

Share this post


Link to post
Share on other sites

I think you need the full path to the file, e.g. /var/www/mysite/site/templates/myCss.css

If you don't know the path, check the output of "$config->paths->templates".

Let me know if it still does not work!

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
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      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 Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...