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 bernhard
      --- Please use RockFinder3 ---
    • 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 (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...