Applicable to:
- Plesk Obsidian for Linux
- Plesk Onyx for Linux
- Plesk for Linux
Question
How to enable imagick support in CMS or website in Plesk?
Answer
It is not required to set anything on Plesk side.
imagick module can be used in CMS if it supports it. CMS should automatically detect that imagick is installed or some configuration can be done using additional scripts like WordPress - https://wordpress.org/plugins/imagemagick-engine/. For the support of imagick module contact the corresponding CMS technical support.
For the other websites, website code should be adjusted.
Additional information
More information about imagick usage can be found here: http://php.net/imagick
Comments
2 comments
The PHP-Imagick module seems to be install by the provided Plesk php versions, but Wordpress PDF thumbnail generation (which uses Imagick) doesn't work. Is there a way to get this to work properly?
Hello,
The issue with plugin is being discussed on WordPress support forum:
https://wordpress.org/support/topic/bropken-pdf-thumbnail-generation/
So, please test your installation using `PDF thumbnails support test` plugin and in case everything is ok, please contact plugin's developers.
Plesk only provides module for PHP and I could confirm that the module is working on test installation:
# cat imagicktest.php
<?php
//This function prints a text array as an html list.
function alist ($array) {
$alist = "<ul>";
for ($i = 0; $i < sizeof($array); $i++) {
$alist .= "<li>$array[$i]";
}
$alist .= "</ul>";
return $alist;
}
//Try to get ImageMagick "convert" program version number.
exec("convert -version", $out, $rcode);
//Print the return code: 0 if OK, nonzero if error.
echo "Version return code is $rcode <br>";
//Print the output of "convert -version"
echo alist($out);
?>
# /opt/plesk/php/7.1/bin/php imagicktest.php
Version return code is 0 <br><ul><li>Version: ImageMagick 6.7.8-9 2019-02-01 Q16 http://www.imagemagick.org<li>Copyright: Copyright (C) 1999-2012 ImageMagick Studio LLC<li>Features: OpenMP<li></ul>
So, I suppose that the issue is on plugin's side.
Please sign in to leave a comment.