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

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

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