plav

In your shoes, @kevanp, I wouldn’t be comfortable either, although I doubt it could bring trouble from which an easy recovery isn’t possible.

I just might be in a similar situation, even though I was clear to my hosting company that I was using PHP 7.1. I’ve done a bit more fooling around with this and here’s what I’m seeing, with my php.ini file as described earlier.

• imagick module version is 3.4.3, according to phpinfo()
• with PHP 7.1.14 the WP Site Health warning appears
• with PHP 7.0.25 the WP Site Health warning appears
• with PHP 5.6.30 the WP Site Health does not appear

This leads me to believe that either 1) my host is like yours the tech didn’t know that or didn’t tell me that or didn’t pay attention when I said PHP 7.1, or 2) what I put in my php.ini file at the suggestion of my host didn’t point to the correct imagick version.

For now I’m going to ignore the WP recommendation and get on with life. I’m not falling back to PHP 5.6 just to get over it. I’ll put off until later going back to this host with my findings so far. I’ve got other WP installations to upgrade, some on different hosts as well as different hosting packages on this host. I’ll keep an eye on what works and what doesn’t and, with luck, figure out a solution along the way.

Y’know, WP 5.2 is new so there could always be a bug in Site Health that doesn’t handle certain cases like these. Never know. There’s an awful lot of variety across hosting companies and their packages.

I’m seeing this message from Site Health as well. My PHP version is 7.1 – the latest my hosting company offers right now. Looking at the results from phpinfo() did not indicate imagick.

I got hold of my hosting company and they advised me to add this line to my php.ini file:

extension=imagick.so

After doing that, phpinfo() indicates imagick as available. Yet, WP Site Health continues to deliver the recommended improvement message. I’m continuing to look for a solution but since no one’s mentioned this I figured to throw in my two cents.