Jump to content

PDF Fieldtype/Inputfield

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
Link to comment
Share on other sites

  • 1 month later...

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.

Link to comment
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.

Link to comment
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->readimage($this->filename . "[0]");
$imagick->scaleImage($width, $height);

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

Link to comment
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?

Link to comment
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.

Link to comment
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.

Link to comment
Share on other sites

  • 2 weeks later...

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.

Link to comment
Share on other sites

  • 10 months later...

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

Link to comment
Share on other sites

  • 2 months later...

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!


Link to comment
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?


  • Like 2
Link to comment
Share on other sites

  • 4 months later...

Similar problem here: Fatal error: Class 'Pagefile' not found in /home/.../.../site/modules/FieldtypePDF/FieldtypePDF/PagePDF.php on line 40

Using PW 3.0.60; Github devns link is dead...

Link to comment
Share on other sites

  • 5 months later...

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 MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.

      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      ProcessWire module directory
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
  • Create New...