Jump to content
Wanze

Pages2Pdf

Recommended Posts

I use the module for a german page without multi language support. If I remember right you could do it with the Languagefields which processwire offers. If you need images or repeater or something else just name it with the ending of your language... e.g. if your shortname for english is en the you can name it myImage_en. Hope this will be help for you.

Share this post


Link to post
Share on other sites

hello Henning,

as I understand you correct: you mean to create more than one instance of the pdf creation button depending on the language? Mmmhh, I will try this tomorrow but this could be a possible solution.

It has to create a pdf file for each language - at the moment only on pdf-file is created (independent of the language).

Best regards jürgen

Share this post


Link to post
Share on other sites

Hi Juergen,

I'm the maintainer of the module.

You could solve it by hooking after this method and return a PDF filename that depends on the language of the current user:

https://github.com/wanze/Pages2Pdf/blob/master/Pages2Pdf.module#L454

I could make this method hookable for you. But I think supporting multilang would be a great feature for the module, I might need this myself soon.

I'll find some time this weekend to implement it. :)

My approach would be to create a new configuration option where you can select for what languages the PDFs are generated.

When requesting a download, the PDF in the language of the current user is served.

Cheers

Edit:

Could you post module related questions in the official module thread? Thanks.

I'll try to merge them ;)

Edited by Wanze
  • Like 5

Share this post


Link to post
Share on other sites

Hello Stefan,

thanks for your contribution (and the awesome module too).

Yes it would be great to get the possibility of multilanguage support. At the moment I dont need this function immediately. I am not very familiar with hooks in processwire so I will wait until an update ;)

Next time I will post it under the right section, I`ll swear :)

Thanks and best regards

Jürgen

Share this post


Link to post
Share on other sites

Hi,

I have implemented the feature and it's available in the dev branch: https://github.com/wanze/Pages2Pdf/tree/dev

If anyone has time to test it out, please do so and report any issues back here. I will merge it into the master branch after some more testing :)

How does it work?

First, you need to enable multilanguage support in the module configuration. If enabled, the module creates a PDF in the language of the current user. The same is true when downloading a PDF. If the PDFs are pre-generated when saving pages in the admin, a PDF for each language is created.

The language name is appended to the PDF filename in order to distinguish between files of different languages. In addition, if the module "LanguageSupportPageNames" is installed, the local page name is used for the filename.

At the same time I added the newest version of mPDF to the module WirePDF. As always, please check that your PDFs are still rendered correctly after updating!

Good night to everyone from Switzerland

  • Like 6

Share this post


Link to post
Share on other sites

Stefan,

this is awesome. I have updated the module and at the moment I have not detected any problems. I am still testing it further more.

Thanks so much!!!!

Share this post


Link to post
Share on other sites

Thanks for your feedback Jürgen!

I've tested myself and didn't find any bugs, so i merged into master. Meaning that v. 1.1.2 is now official ;)

As described two posts above, this version adds support for multilanguage PDF files.

Please make sure that your PDF files are still generated correctly before you update on a live site!

Cheers

  • Like 2

Share this post


Link to post
Share on other sites

Wazne - I was trying Pages2PDF for the first time after recommendations from the guys and was getting an error as follows.

 

Error: Call to a member function get() on a non-object (line 453 of /var/www/vhosts/pdf-tester.com/httpdocs/site/modules/WirePDF/Pages2Pdf.module)
This error message was shown because you are logged in as a Superuser. Error has been logged.

 

Looking at line 453 of /modules/WirePDF/Pages2PDF/ I see a reference to MultiLanguage Support.

If I check the Multilanguage support checkbox in the Module settings, my error disappears and my PDF is working.

Share this post


Link to post
Share on other sites

Hi Wanze,
thanks for the module. I use it the first time. While testing in devmode I am getting the following error:
Warning: Invalid argument supplied for foreach() in /site/modules/Pages2Pdf/Pages2Pdf.module on line 182

method                      | called from
----------------------------+-------------
Wire->__call( )             | ../Page.php
Wire->runHooks( )           | ../Wire.php
Pages2Pdf->hookDeletePDF( ) | ../Wire.php

After a quick look. Maybe something like this could help. Not tested! (Line 182)

       // Delete PDF for each language
       $languages  =(wire('modules')->isInstalled('LanguageSupport'))?wire('languages'):array(wire('user')->language);
         foreach ($languages as $language) {

Edit:
I should read preceding posts first ... Maybe you made already an update and call determineLanguage() method in hookDeletePDF(). If not you should. :)

 
 

Share this post


Link to post
Share on other sites

Hi Wanze,

thanks for the module. I use it the first time. While testing in devmode I am getting the following error:

Warning: Invalid argument supplied for foreach() in /site/modules/Pages2Pdf/Pages2Pdf.module on line 182

method                      | called from
----------------------------+-------------
Wire->__call( )             | ../Page.php
Wire->runHooks( )           | ../Wire.php
Pages2Pdf->hookDeletePDF( ) | ../Wire.php

After a quick look. Maybe something like this could help. Not tested! (Line 182)

       // Delete PDF for each language
       $languages  =(wire('modules')->isInstalled('LanguageSupport'))?wire('languages'):array(wire('user')->language);
         foreach ($languages as $language) {

Edit:

I should read preceding posts first ... Maybe you made already an update and call determineLanguage() method in hookDeletePDF(). If not you should. :)

Had something similar. I think you need to enable multi-lingual support even if you're not using it.

Share this post


Link to post
Share on other sites

Hi guys,

Thanks for reporting the problems.

You're right, the problem is that if language support is not enabled, the langauges API variable is not available. I wasn't aware of that and of course only tested when language support was enabled.  I'll push a fix this afternoon!

Cheers

  • Like 2

Share this post


Link to post
Share on other sites

The bug is fixed with the latest commits, please upgrade the module.

Thanks again for finding and posting this here :)

  • Like 2

Share this post


Link to post
Share on other sites

hey wanze, looks great and could help me a lot if i find time to code some day for what is in my head for a long time ^^

https://github.com/wanze/Pages2Pdf/blob/master/Pages2Pdf.module#L97

shouldn't it check if the user has at least viewing access for the page with the given ID because i think $pages->get(id) via API returns the page independent of its current publishing/hidden state and access?

maybe anyone could easyly change the page id and download pdfs of pages he is not allowed to see?

  • Like 2

Share this post


Link to post
Share on other sites

Hi BernhardB,

Thanks :)

shouldn't it check if the user has at least viewing access for the page with the given ID because i think $pages->get(id) via API returns the page independent of its current publishing/hidden state and access?

maybe anyone could easyly change the page id and download pdfs of pages he is not allowed to see?

You are right, thanks for mentioning this. I'll add the check!

The current system is secured that you must choose the templates allowed to generate PDF files. If a user does change the page ID and the template of the requested page is not allowed to create PDF's, nothing happens. However, if the template can generate PDFs and at the same time has restricted access, then this is a problem.

  • Like 1

Share this post


Link to post
Share on other sites

It seems like I'm to stupid to change the font. I followed the instructions for mpdf but I can only set default fonts like Helvetica, Times. The given example dejavu also don't work. I have converted an oft-font to ttf and put everything in the right place. Any hints how to change to individual fonts?

Share this post


Link to post
Share on other sites

OK. I got it. I used the switch in the wirepdf modul configuration and set it from core fonts "c" so "s". Now it works.

Share this post


Link to post
Share on other sites

Thanks for your information hheyne, glad it works!

Share this post


Link to post
Share on other sites

Hi Wanze,

is it possible to add additional / custom css files instead of change the styles.css file?

I know there is a global configuration, but is it possible in template context?

Regards

Share this post


Link to post
Share on other sites

Hi pwFoo,

It should be possible with an autoload module that hooks before Pages2Pdf::createPDF.

  1. Delete the styles.css file in /site/templates/Pages2Pdf folder, so that the module does not add styles from this file
  2. Create a new autoload module (or use an existing one) and add the following code into the init method.
// Inside an autoload module

public function init() {
  $this->addHookBefore('Pages2Pdf::createPDF', function($event) { 
    $pages2pdf = $event->object;
    $page = $event->arguments('page');
    // Set a custom css file for the template of the page where the PDF is generated
    $cssFile = wire('config')->paths->templates . 'pages2pdf/' . $page->template . '.css';
    $pages2pdf->wirePDF->set('cssFile', $cssFile); 
  });
}

I did not test this code, please report if it does work or not work :)

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

Thanks!

At the moment I have no time to test it, but I'll report back then...

Make css file a module configuration isn't needed in every use case but would be nice. Any plans to change it?

Share this post


Link to post
Share on other sites

Make css file a module configuration isn't needed in every use case but would be nice. Any plans to change it?

What kind of configuration do you have in mind? There is a setting to specify the path to a css file. When it comes down to change the configuration dynamically to have multiple CSS files, it's hard to introduce a config setting that would fit everyone's needs. That's where Pws hooking system is the best solution IMO.

Share this post


Link to post
Share on other sites

Ok, should also be fine ;)

If I really need this modification I use a hook / autoload module. 

Thanks for this awesome module. It makes life easier ;) 

Share this post


Link to post
Share on other sites

@pwFoo

Report back here if you have any issue with the hook. :)

Another possibility would be to prefix your styles with the template and put everything in one CSS file, e.g.

.home.style1 {
  background-color: green;
}
.contact.style1 {
  background-color: red;
}

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

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