Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Providing ICC profiles to ImageMagick is optional. If these configuration properties are unset, no profiles will be supplied to ImageMagick, and thumbnails produced from PDFs using the CMYK color space will also use CMYK. The transformation from CMYK to RGB is optional, but keep in mind that thumbnails using CMYK will make troubles cause problems if you use JSPUI and display thumbnails within browsing on browse and search pages (see DS-2834).

Additional Customization

...

Note: The PDF thumbnail generator is hard-coded to generate a thumbnail from the first page of the PDF.

Possible Errors / Issues

"convert.im6: not authorized" errors

On Ubuntu (possibly other OSes), you may see errors like these when attempting to generate PDF thumbnails:

Code Block
ERROR filtering, skipping bitstream:
        Item Handle: 1234/5678
        Bundle Name: ORIGINAL
        File Size: 30406135
        Checksum: c1df4b3a4755e9bed956383b61fc5042 (MD5)
        Asset Store: 0
org.im4java.core.CommandException: org.im4java.core.CommandException: convert.im6: not authorized `/tmp/impdfthumb6294641076817830415.pdf' @ error/constitute.c/ReadImage/454.


These may be caused by a change in your ImageMagick policy configuration on your server. 

In Ubuntu, the default "policy.xml" was recently updated to exclude all Ghostscript formats (including PDF, PS, etc).  See this ticket: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1796563

The newly added lines in the /etc/ImageMagick/policy.xml are these ones:

Code Block
<!-- disable ghostscript format types -->
<policy domain="coder" rights="none" pattern="PS" />
<policy domain="coder" rights="none" pattern="EPS" />
<policy domain="coder" rights="none" pattern="PDF" />
<policy domain="coder" rights="none" pattern="XPS" />

If you wish to re-enable ImageMagick to process Ghostscript format types, you can simply comment out those lines in the configuration file.  Be aware that, as the fix to this vulnerability is not yet verified, you should only do so at your own risk.