Jump to content

Recommended Posts

Hi, new version is here, as I promised. It's currently on the dev branch: https://github.com/uiii/ProcessWire-FieldtypePDF/tree/dev. The readme is updated so everything should be clear. It contains tests and they successfully passed for PW 2.4, 2.5. If you can try the module, I'd be glad to hear your opinions and suggestions.

  • Like 1

Share this post


Link to post
Share on other sites

Oh yeah, my hosting provider said they couldn't update GS to 9.x...

Thanks for the update - will check it out as soon as I can. :)

Share this post


Link to post
Share on other sites

I'm trying this (dev) on PW 2.6 and it works fine so far but I'm not sure why it's using Image field ... like it has the pdf file but showing an image that in PW 2.6 has a dialog for cropping etc. The file basename is a link that opens a modal where there's an error:

TemplateFile: Field file_pdf is not an instance of FieldtypeImage<pre>#0 /Applications/MAMP/htdocs/verbandsnet/wire/core/Modules.php(441): ProcessPageEditImageSelect->init() #1 /Applications/MAMP/htdocs/verbandsnet/wire/core/Modules.php(1012): Modules->initModule(Object(ProcessPageEditImageSelect), false) #2 /Applications/MAMP/htdocs/verbandsnet/wire/core/Modules.php(919): Modules->getModule('ProcessPageEdit...') #3 /Applications/MAMP/htdocs/verbandsnet/wire/core/ProcessController.php(135): Modules->get('ProcessPageEdit...') #4 /Applications/MAMP/htdocs/verbandsnet/wire/core/ProcessController.php(209): ProcessController->getProcess() #5 [internal function]: ProcessController->___execute() #6 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(387): call_user_func_array(Array, Array) #7 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(325): Wire->runHooks('execute', Array) #8 /Applications/MAMP/htdocs/verbandsnet/wire/core/admin.php(93): Wire->__call('execute', Array) #9 /Applications/MAMP/htdocs/verbandsnet/wire/core/admin.php(93): ProcessController->execute() #10 /Applications/MAMP/htdocs/verbandsnet/wire/modules/AdminTheme/AdminThemeDefault/controller.php(13): require('/Applications/M...') #11 /Applications/MAMP/htdocs/verbandsnet/site/templates/admin.php(15): require('/Applications/M...') #12 /Applications/MAMP/htdocs/verbandsnet/wire/core/TemplateFile.php(169): require('/Applications/M...') #13 [internal function]: TemplateFile->___render() #14 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(387): call_user_func_array(Array, Array) #15 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(325): Wire->runHooks('render', Array) #16 /Applications/MAMP/htdocs/verbandsnet/wire/modules/PageRender.module(385): Wire->__call('render', Array) #17 /Applications/MAMP/htdocs/verbandsnet/wire/modules/PageRender.module(385): TemplateFile->render() #18 [internal function]: PageRender->___renderPage(Object(HookEvent)) #19 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(387): call_user_func_array(Array, Array) #20 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(325): Wire->runHooks('renderPage', Array) #21 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(409): Wire->__call('renderPage', Array) #22 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(409): PageRender->renderPage(Object(HookEvent)) #23 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(325): Wire->runHooks('render', Array) #24 /Applications/MAMP/htdocs/verbandsnet/wire/modules/Process/ProcessPageView.module(187): Wire->__call('render', Array) #25 /Applications/MAMP/htdocs/verbandsnet/wire/modules/Process/ProcessPageView.module(187): Page->render() #26 [internal function]: ProcessPageView->___execute(true) #27 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(387): call_user_func_array(Array, Array) #28 /Applications/MAMP/htdocs/verbandsnet/wire/core/Wire.php(325): Wire->runHooks('execute', Array) #29 /Applications/MAMP/htdocs/verbandsnet/index.php(241): Wire->__call('execute', Array) #30 /Applications/MAMP/htdocs/verbandsnet/index.php(241): ProcessPageView->execute(true) #31 {main}</pre>


When creating the PDF field I'm seeing configurations same like an image field, but it's not. I'm not sure this is the right direction of how this should work.

Share this post


Link to post
Share on other sites

Because I'm not able to download/open the PDF itself in the admin like I expect when clicking on the basename. Maybe I get it wrong, but it's not only about creating an image of a pdf but also having the pdf itself. So there maybe the best way is to introduce your own "renderItem()" method again instead of using the parent method.

Share this post


Link to post
Share on other sites

Hi, thanks for the reply. I haven't tried the PW 2.6 yet. The reason why I used image inputfield is to render the PDF thumbnails exactly the same way as images. But maybe you are right, I should have used my own render method. I'll check it out.

  • Like 1

Share this post


Link to post
Share on other sites

DEV branch is updated, should be PW 2.6 compatible now. And InputfieldImage is not parent of InputfieldPDF anymore. Check it out.

  • Like 1

Share this post


Link to post
Share on other sites

Not sure why this worked, but I had to modify the ImageMagick code in PagePDF.php a bit to get it working on GoDaddy shared hosting (I know, I know...):

$imagick = new Imagick($this->filename . "[0]");
$imagick->setResolution(300, 300);
$imagick->setOption('pdf:use-cropbox', 'true');
//$imagick->setColorspace(Imagick::COLORSPACE_RGB);
//$imagick->readimage($this->filename . "[0]");
$imagick->setImageFormat('png');
$imagick->scaleImage($width, $height);
$imagick->writeImage($filename);

I believe it has to do with GoDaddy running old versions of IM and GhostScript, but I'm not certain.

Share this post


Link to post
Share on other sites

Hi @evan,
yes, it's probably because of the old version of IM and GS. What was the problem exactly (error message, ...), can you post it here? I also find that setColorspace method is supported since IM version 6.5.7, so I should change the code to reflect that. What is the problem with readImage method? Will it work if you comment only setColorspace?

Share this post


Link to post
Share on other sites

It's been a while since I did this, but I think you will have problems with the change to loading the image at the start rather than using readImage. The problem is with setResolution - this needs to happen before the image is read. The image is rasterized as soon as it is read, so setting the resolution afterwards can result in a poorer quality image.

Share this post


Link to post
Share on other sites

The setColorspace() method doesn't exist on my server, as IM is too old (ImageMagick 6.5.4-7):

Error: 	Call to undefined method Imagick::setColorspace() (line 16 of /path/to/public_html/site/modules/FieldtypePDF/PagePDF.php)

When I use readFile(), I get the following error (not the real path, obviously):

- Postscript delegate failed `/path/to/file.pdf': No such file or directory @ pdf.c/ReadPDFImage/611

From what I read this is common if you're using a pre-9.x version of GhostScript (server has 8.70).

I haven't seen any visible quality issues with declaring the image with the Imagick object, but I also haven't been looking too carefully -- mostly glad to get it working at all.

Share this post


Link to post
Share on other sites

Hi, I've been doing some research and testing. But I don't find a way to get it properly working on older versions of ghostscript. But @evan's solution works, it produces low quality images and it's properties cannot be affected because the pdf is read on the Imagick object creating. The readImage method always throws the mentioned exception. Despite of this it is useful where you cannot update GS or IM (e.g. shared hosting). So I added it to the module as fallback mode. It can be turned on in the module's settings. See DEV branch.

Share this post


Link to post
Share on other sites

Any chance to update this module for 2.5+? Aka making the dev to the new master? 

Share this post


Link to post
Share on other sites

Hi, sorry I din't do that yet. I stucked, because I wanted to test it properly first. I wanted to make automated unit tests, but in processwire it isn't (maybe wasn't) so easy, I wanted to use wireshell to help with it, but somehow I moved my activity somewhere else. I can merge the branches, but I would like to have some feedback if it is working correctly or not. Did you try it? I've tried it in PW 2.5 and 2.6 and it looks it's working, but I'm not sure about PW 2.7+. If you can test it a give me feedback I would appreciate it. Thanks

Share this post


Link to post
Share on other sites

Hi Richard,

I've tried out this module on version 2.6 and it works nicely! 

I've tried installing it in version 3.0 and had to restore the database from backup: I got error messages and couldn't reach the PDF-field anymore. 

The information about compatibility is misleading: on the module page it says compatible with version 3.0, but later on it's stated <3.0.

Too bad I can't used it now, I liked it a lot!

Thanks.

Share this post


Link to post
Share on other sites

Hi lenoir,

There is a version compatible with 3.0, it is in devns branch, it is separated because i didn't find a way to have one codebase compatible with PW 2.x and 3.x (I can tell you more if you want).

What happend with your pdf files in 3.0? Why did you have to restore the database? Should I fix something?

Cheers,
Richard

  • Like 2

Share this post


Link to post
Share on other sites

Finally I've found out how to support PW 2.x and PW 3.x with one codebase. So here is a new version 1.1.2 compatible with PW 2.5+. I updated the tests as well, turned the script which runs tests against multiple versions of ProcessWire into standalone tool PW-Test.

  • Like 4

Share this post


Link to post
Share on other sites

@ICF Church Hi, I'm trying to solve your issue, but I can't reproduce the error. What version of PHP are you using? During module installation there is a step where the `use` statemenents in source files under FieldtypePDF folder are prefixed with `Processwire\' namespace if PW 3.x detected. Could you please examine what's wrong? Look into this method https://github.com/uiii/ProcessWire-FieldtypePDF/blob/d11ff962d520782fa25215f5ce606886773a5a44/FieldtypePDF.module#L232. Thanks

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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...