PD Guard groups PHP, extensions and PHP settings so you can identify the runtime issue behind an installation warning. Check the environment used by the application, not just a version displayed elsewhere in your hosting account.

Identify the affected check

1. Open PD Modules → Guard → Report.
2. Review the PHP, Extensions and PHP settings groups.
3. Note the specific value and whether it is a warning, failure or unavailable measurement.
4. Compare the report time with any recent runtime change, then refresh when a fresh result is needed.

The web report inspects the runtime serving that request. A scheduled check can run under the cron runtime, whose version, extensions or limits may differ. Compare both when the panel and background monitoring disagree.

Review current support and compatibility

The module uses bundled version rules. A recognised branch result is not a live check of every newer release or patch. Compare PHP’s current support information with your billing platform’s supported combinations before arranging an upgrade. A minimum-runtime finding is different from a branch’s remaining security support.

Review the specific memory, execution-time, error-display or extension issue with the administrator responsible for that runtime. Do not change a server-wide value solely to clear a warning without checking the application and other hosted workloads.

Recheck the same environment

After an intended runtime change, request a fresh web report and compare the affected row. Compare it with the next relevant scheduled run where monitoring is available and active. Your hosting team should confirm which PHP runtime serves the web application and which runs its cron; one result does not establish the other environment’s configuration. Arrange runtime changes with your own systems administrator or infrastructure provider.

See the PD Guard Blesta guide for related tasks, or explore PD Guard.