Rickard Westerlind

Are you running a self-hosted server? Since the PHP extension is not recognized it could be something with multiple PHP-versions on the server?

WP is now using ImageMagick as default. However it does not allow settings to quality etc so therefore this plugin still has a purpose.

Ok!

How do I get more information about the vulnerability?

There must be some other permissions error in your WordPress. The user needs to be administrator (“manage_options” capability) but that should not give that kind of error.

Thanks for reporting. I’ll add it to the feature requests and see if I can fix this in the future. Please follow on https://github.com/orangelabweb/imagemagick-engine/issues

Very little difference. PHP module is of course a middle step. Command line is more direct. But nothing you will notice or should notice regarding the performance of the server either.

Hi,

1. This plugin makes use of ImageMagick when it is installed on the server. It can be installed and executed via the command line or via a PHP module. This plugin supports both ways.

2. You don’t have to run anything on the command line. That is what this plugin does for you when images are uploaded to the media library.

Hi,

ImageMagick is something that needs to be installed on the server. This plugin only makes it possible to use ImageMagick if present on server. Not possible to install via a plugin in WordPress.

So contact your hosting provider and see if they can install this for you or activate it so you can use it.

Can we move this to here?

https://github.com/orangelabweb/imagemagick-engine/issues/27

This plugin only hooks in when the images are actually generated. It’s not a custom image editor for WordPress so it’s not visible on the health monitor screen.

However, there might be something wrong with your ImageMagick setup as you say because WP should use WP_Image_Editor_Imagick when that is available. But might be so that ImageMagick Engine is better of finding that so it might be active even though you don’t think so.

Ah, that was a bug and it will be fixed and a new release out very soon. However, it only occurs when wp image editor is not available.

No. This plugin is only built to enable the use of ImageMagick instead of GD. There are other plugins for that use case as this is possible with both image engines.

Hi,

Thanks for the review and glad to hear it has helped you over the years. Do you have any suggestions on why the regeneration should and could be faster?

An improvement where we will use WP_Image_Editor class instead to generate filename will be released in the next version. But, I’ve still not been able to reproduce same error as you as your image file works fine to resize with same filename in some environments and some rename it to “xxxx” etc. So I’m still not sure it’s only because ImageMagick Engine.