Jump to content
Wanze

Pages2Pdf

Recommended Posts

The config path variables do update with moving the installation.

Yes. But does the WirePDF input field accept a config path variable?

  • Like 1

Share this post


Link to post
Share on other sites

@Spica

Nope not yet, I will consider this for the next version. Makes sense!

  • Like 1

Share this post


Link to post
Share on other sites

Hi, I'm using multi language support and everything is working well (great module btw) except for the text coming from a TextAreaLanguage field where I get missing characters, like in Portuguese, that are replaced by '?'. Anyone having this problem or know what can be wrong? Thanks.

Share this post


Link to post
Share on other sites

Are those question marks at the frontend? Then you are probably defining wrong character encoding in you template files or you have saved your template files with wrong encoding.

Share this post


Link to post
Share on other sites

Yes, those are on the front-end, but all the other content is ok except for the text coming from the TextAreaLanguage :/.

Are those question marks at the frontend? Then you are probably defining wrong character encoding in you template files or you have saved your template files with wrong encoding.

Share this post


Link to post
Share on other sites

Hi zyON,

I think the problem is that the used fonts don't contain your portuguese characters. Can you try to change your WirePDF settings:

  • Mode: "s" instead of "c"
  • Font: "DejaVuSans"

See this post for more information: https://processwire.com/talk/topic/3008-pages2pdf/page-6#entry96263

If this does not work, you'd probably need to add a font that supports your character set by yourself to mPDF.

  • Like 2

Share this post


Link to post
Share on other sites

Wanze: Thanks. You were right, I had to change it to DejaVuSans (but I also had to to copy the DejaVuSansCondensed family to the module ttfonts folder because it was looking for them somehow and throwing an error.

I was using Helvetica and it should contain Portuguese characters... I'm using it on the site text too. 

Share this post


Link to post
Share on other sites

Hello Wanze,

I'm trying to use your module to send PDF invoices to customers of my store and I was wondering if it was possible to pass an object to the template similar to $template->set() works ...? 

Thanks,

thomas

Share this post


Link to post
Share on other sites

You can use the WirePDF module with any kind of markup you need. I'm using wireRenderFile() to render the html with custom data and then pass it into WirePDF.

  • Like 2

Share this post


Link to post
Share on other sites

Hi

after upgrading from 2.7.x to 3.0.5 I get this error when trying to download a pdf.
Superuser/Admin:
Parse Error: syntax error, unexpected ',' (line 8910 of /www/htdocs/.../site/modules/Pages2Pdf/mpdf/mpdf.php)

User:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Pages2Pdf 1.1.6

Any help would be greatly appreciated.

Share this post


Link to post
Share on other sites

Hi Metaphora,

Well that's strange, I guess this has to do with ProcessWire's FileCompiler in 3.x. I'll take a look at it in the next days.

Cheers

Share this post


Link to post
Share on other sites

Also strange error on saving article in PW 3 (in this case PW 3.0.8):

Parse Error: syntax error, unexpected '.' (line 39 of /home/.sites/......./site/modules/Pages2Pdf/mpdf/mpdf.php) 

Best regards Jürgen

Share this post


Link to post
Share on other sites

I'm also getting a parse error on 3.08:

Parse Error: syntax error, unexpected 'var' (T_VAR) (line 39 of /var/www/example.com/site/modules/Pages2Pdf/mpdf/mpdf.php) 

Share this post


Link to post
Share on other sites

Hi guys,

Thanks for reporting those errors. I'll find some time to make this module 3.x compatible in the next few days, I guess disabling the new FileCompiler for the external mpdf library should do the trick.

  • Like 1

Share this post


Link to post
Share on other sites

Hi folks,

I quickly tested locally with ProcessWire 3.x and it worked by disabling the file compiler for the external mpdf library. I need to test a bit more, especially the multi language support of the module, before I commit a new version. But if you want to make it work in the meantime, here you go:

  1. Add // FileCompiler=0 to the first line after the php opening tag in the file /site/modules/Pages2Pdf/mpdf/mpdf.php
  2. Delete the folder /site/assets/cache/FileCompiler/site/modules/Pages2Pdf to make sure the module files are recompiled

Now generating and downloading PDFs should work :)

Cheers

  • Like 6

Share this post


Link to post
Share on other sites

Is it possible to have the PDF presented as an inline file rather than a download?

Whether a PDF file is downloaded or not depends on server configuration or browser settings and maybe on transferring the document files through PHP should it be the case.

eg.: https://www.devside.net/wamp-server/forcing-a-pdf-or-doc-to-open-in-browser-rather-than-downloading

Personally my Safari is set to force the download of any PHP file by turning off the viewer plugins. So you might need to check the client's setup as well.

  • Like 1

Share this post


Link to post
Share on other sites

@Asmordean

You might want to have a look at https://github.com/mozilla/pdf.js Widely used code for embedding PDFs in a standards-friendly way.

As szabesz said, you still need to check for the client's browser setup and act accordingly if you want to make sure that the PDF is embedded in your HTML. Here's some code to point you in the right direction: https://gist.github.com/falexandrou/9753871

Instead of using an Iframe you could embed it as an object (see the first link above).

  • Like 4

Share this post


Link to post
Share on other sites

I am not sure the best approach for this, but suggestions are appreciated. I have created a members portal that allow each member to select some "nodes" (pages) and stores them in a page field type that I have assigned to the user template which is an admin template. They can then download the pdf containing the pages that they have selected.

The issue is that I need to store the pdf's under each users page instead of the selected page. Is this possible? I would also really like to be able to use $user->name in the naming convention as well. I guess this would be possible using the hook you described here.

I think just appending the user's id to the file name would do the trick for now.

Awesome module by the way. Thanks for sharing it.

Share this post


Link to post
Share on other sites

Hi RyanJ,

I think the problem is that the module does not allow you to select the user template in the settings, am I right?

Probably the simplest way would be to generate and store the PDFs by yourself with the module WirePDF. It's a wrapper around the mPDF library and included in the Pages2Pdf module. Check the examples here how to use the module, and please ask if you need further help in this.

Cheers

Share this post


Link to post
Share on other sites

Hi Wanze, 

Thanks for pointing out the examples. I was hoping I could just append an id, but I have went the route you suggested. The problem I am having is actually getting the document to display. (I am getting a Failed to load PDF document message). I have a get variable set as ?pdf=1 and the pdf is being written to the folder using.

$pdf->save($page->filesManager->path . $file_name);
$pdf->download($file_name);

When I download the pdf, it is perfect, but viewing it in the browser is the issue.

Thanks for your assistance.

Updates:: forcing a download also has the same issue

$pdf->download($file_name, 'D');

Update::

This issue was where I was calling the module. It should go before the header file is included. This may or may not be the right solution, but it did to the trick for me. Although, there is some issues now with images not showing up.

Edited by RyanJ

Share this post


Link to post
Share on other sites

Hi Ryan,

Strange, I've never seen this message before. Do you need to save the file or could you generate it dynamically when a download is requested? I'm thinking that maybe the combination of calling $pdf->save() first and then $pdf->download() afterwards has some issues. You could try these two approaches:

1) Save the PDF to the disk and let ProcessWire download it:

$pdf->save($page->filesManager->path . $file_name);
wireSendFile($page->filesManager->path . $file_name, array('forceDownload' => true));

You can also omit the forceDownload and see if it works.

2) Don't save the PDF to disk, always create it dynamically and download it:

$pdf->download($file_name);

Does any this work? :)

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

Hi Wanze, 

That did the trick. I commented out the saving of the file and all appears to be working now (Virtual Hug). Am I write that the file call's the module needs to be included before any other files? I am assuming this has to do wit the header that has to be sent.

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...