Legacy scope: This article is retained for documented CentOS 7 or AlmaLinux 8 environments. It is not a current, universal Imagick installation procedure. Do not assume an older package path, PHP build, or configuration applies to a current server; use the applicable vendor documentation and a maintenance plan for the environment you actually administer.
Confirm the intended PHP runtime first
On cPanel/WHM systems, a domain can use a PHP version that differs from another domain or from the system default. Before any approved maintenance work, identify the affected domain or application, confirm the PHP runtime it uses, and make sure the check is performed in that same context. cPanel's EasyApache 4 PHP version and extension guide and its PHP inheritance documentation explain why this scope matters.
Use approved maintenance guidance for the actual platform
PHP's Imagick documentation is the extension reference. For a cPanel/WHM server, follow the current cPanel documentation that matches the installed PHP runtime and hosting configuration. If you do not administer the server, ask the hosting provider or qualified administrator to confirm the supported path rather than applying an older tutorial to a newer platform.
Verify safely without a public diagnostic page
Do not leave a PHP diagnostic page in a public web directory. Instead, use owner-approved administrative checks or a tightly controlled temporary process, then remove any temporary diagnostic immediately. A loaded module by itself is not enough proof that the intended site is ready.
Test the media workflow that matters
After an approved change, use a safe test image in the affected application or WordPress media workflow. Confirm that the intended PHP context can process the image, that a thumbnail or other expected derivative is created when appropriate, and that the resulting image displays correctly on the affected page. Review the relevant application and server logs for warnings or permission errors, then repeat the original reader-facing task.
Plan the rollback and follow-up
Before a production change, record the approved maintenance window and the post-specific rollback method. If the change affects a WordPress site, watch the affected media pages and other customer-facing paths after the test. For adjacent reading, see the current Imagick WHM/cPanel guide, the Imagick Linux hosting guide, and the WHM/cPanel Redis guide when those topics match the actual environment. For WordPress-specific triage, use the FixItPhill WordPress Support Guide; the existing managed WordPress product hub is a separate destination, not proof of an active service.
