• I’d like to get rid of the 3 issues on my site health screen.

    1: Warning?The optional module, imagick, is not installed, or has been disabled – I’ve installed imagick engine, and checked the “Enable enhanced image engine” option, but I still get the error.

    Image engine is set to “ImageMagick command line”, as when I choose “Imagick PHP Module” it says ”?Imagick PHP module not found”

    ———–

    2: You should use a persistent object cache – I’ve installed the “WP Super Cache” plugin, have “caching image” selected, and have clicked the “test cache” button, and they all come back with a green OK, yet I still get the message on my site health page.

    ———–

    3: Email domain issues detected – The SPF part is okay, it has a green tick, but the DMARC shows an error “It doesn’t look like DMARC has been set up on your domain (djalkemy.co.uk). We recommend using the DMARC protocol because it helps protect your domain from unauthorized use. Please check out this step-by-step guide for details on how to add the DMARC record to your domain’s DNS.” My site is hosted by IONOS, and one of their tech people told me that they both do the same thing, so it’s not an issue. I have OCD and it bugs me when I have errors and such, so I’m wondering, could I just also do the DMARC option to get rid of the issue, or will that cause any conflicts, and am I better just trying to ignore that.

    Any help is greatly appreciated, thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator bcworkz

    (@bcworkz)

    I’m not sure what you did to install Imagick. What to do varies by your server type. You need the PECL PHP extension installed.

    To implement a persistent object cache with WP Super Cache, I recommend asking in their dedicated support forum.

    Both SPF and DMARC help to keep your emails from being treated as spam, but they are not otherwise the same at all. To implement DMARC you need to add a specific TXT record to your domain’s DNS zone file. Determine whose nameservers are used for your domain name. You’d add records through your account with them. This is frequently but not always your host.

    Thread Starter Eughine Dunnion

    (@alkemy007)

    Thanks for the reply. I contacted Ionos, who fixed the DMARC issue I had. I’ve made a thread regarding the cache issue in the dedicated WP Super Cache forum, and now I’m just stuck on the PECL PHP Extension part.

    I’ve looked at some YouTube videos, and they all mention cPanel. I’m not sure if that is a hosting site, but as I mentioned, I use Ionos, and the only settings I can see regarding PHP settings, is the ability to go from version 8.1, to 8.2. That seems like a logical thing to do, although next to 8.1, it says “recommended”, so I’m hesitant to change it, unless I know it’s safe to do so.

    Sorry if this is a real noob response lol, I’m just starting to get to grips with all this.

    Thanks.

    Moderator bcworkz

    (@bcworkz)

    cPanel is a common server management user interface many hosts use. There are a few hosts who do not use cPanel, but similar functionality should be available through whatever user interface they provide. To install PECL modules like Imagick you need terminal access to the server. Not all hosting plans permit terminal access. If you don’t have terminal access you’ll need to ask your host for assistance.

    If you are already on PHP 8.1 that’s good enough. If your site is stable on 8.1, it’ll likely be the same with 8.2. WP is 99.8% compatible with 8.2. Very few users would encounter the 0.2% that’s not yet compatible. The largest risk in updating to 8.2 are themes and plugins that are not fully compatible. You could try 8.2 and see if it causes any trouble. You can always revert back if trouble is encountered.

    Thread Starter Eughine Dunnion

    (@alkemy007)

    I’ll give it a go, and contact Ionos too, see if they can help me with the PHP module. Thanks for your help dude, it’s really appreciated.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Issues on my site health screen’ is closed to new replies.