Composer install reports an unavailable GD extension while a website confirms GD support. The most expensive fix is rarely the best first experiment. Reproduce the exact failed task before changing settings.
Recognize the exact failure
Primary symptom. Composer install reports an unavailable GD extension while a website confirms GD support. Record the precise point of failure and whether the same input, account or connected device succeeds in another supported mode. That working comparison establishes the scope of the repair.
What can produce this behavior
The first hypothesis is a mismatch in the failing path. Compare php –ini and php -m with the actual CLI used by Composer. The second is a lower-level state that the interface may not show: check multiple PHP installations and platform-config overrides in composer.json. A third possibility is a feature or version limitation, which should be checked against supported documentation before a reset.
For this PHP Problems issue, capture PHP SAPI, ini scan directory and reproducible request payload and compare the same request in CLI and web runtimes without changing production settings. Preserve the last known working configuration so you can tell whether a successful retry came from an actual correction or a temporary recovery.
A decision table for this case
| What you observe | What it suggests | Focused response |
|---|---|---|
| Composer install reports an unavailable GD extension while a website confirms GD support | The failure affects the specific workflow described here; the entire system is not necessarily broken. | Compare php –ini and php -m with the actual CLI used by Composer. |
| The basic comparison exposes a difference between a working and failing configuration. | A local setting, version, account context or device route deserves attention. | Enable GD for the specific CLI PHP version or invoke the intended executable. |
| The same failure persists after a reversible correction. | A deeper dependency or compatibility issue may remain. | Check multiple PHP installations and platform-config overrides in composer.json. |
Before changing anything: Do not use –ignore-platform-req as a permanent compatibility fix. Save a screenshot or anonymized log line, record the previous setting, and back up relevant user data. Do not reset every related service just because one test fails.
Choose a recovery route. The Beginner path checks compare php –ini and php -m with the actual CLI used by Composer. The Advanced path investigates check multiple PHP installations and platform-config overrides in composer.json. They address different evidence; use the path that matches your result.
Step-by-Step Troubleshooting
Choose the Beginner route for reversible checks or Advanced for evidence-driven diagnosis.
Check the affected device or service
Composer install reports an unavailable GD extension while a website confirms GD support. Before editing settings, note the exact time, affected account or device, and whether it started after an update, move, hardware change or network change. This is the baseline for the Composer Says ext-gd Is Missing but phpinfo Shows GD Enabled guide.
Check php --ini and php -m with the actual CLI used by Composer
Compare php --ini and php -m with the actual CLI used by Composer. Observe whether the symptom changes. A clean comparison tells you which part of the process is healthy and avoids unnecessary resets.
Adjust gD for the specific CLI PHP version or invoke the intended
Enable GD for the specific CLI PHP version or invoke the intended executable. Change only this variable, record its former value, and try the failing action once. If there is no improvement, restore the prior configuration before exploring the Advanced route.
Verify composer's platform check and the real PHP runtime both
Composer's platform check and the real PHP runtime both report compatible GD support. Repeat using the same account, network, file, title or hardware condition that previously failed. Do not count a different test as confirmation.
Create an evidence baseline
Collect the error text or state relevant to Composer Says ext-gd Is Missing but phpinfo Shows GD Enabled. Record PHP SAPI, ini scan directory and reproducible request payload; anonymize account IDs, public IPs and secret-bearing log fragments before sharing.
Inspect multiple PHP installations and platform-config overrides
Check multiple PHP installations and platform-config overrides in composer.json. Record the difference between successful and failed cases and keep the first meaningful error rather than the last cascade message.
php --ini && php -mRetest the alternative path
Where practical, compare the same request in CLI and web runtimes without changing production settings. If the alternate case works, return to the single configuration difference instead of changing multiple services. Use the vendor-supported method for your current version.
Preserve a reproducible outcome
Composer's platform check and the real PHP runtime both report compatible GD support. Leave the previous value documented for rollback, then monitor one normal operating cycle. If symptoms recur, attach the sanitized evidence to a vendor or administrator support request.
Interpret the results
After the first corrective action, interpret the result carefully. If the original task now works, leave the other settings unchanged. If it still fails, check multiple PHP installations and platform-config overrides in composer.json. Compare the same request in CLI and web runtimes without changing production settings rather than adding random fixes on top of one another.
For escalation, retain PHP SAPI, ini scan directory and reproducible request payload, the original output, and a single before/after comparison. Redact passwords, tokens and personal data. A support agent can then distinguish the same request in CLI and web runtimes without changing production settings from a general outage without repeating risky actions.
Optional targeted diagnostic
Compare the CLI PHP runtime configuration and modules; this does not enable an extension. Commands below are illustrative and must be run only on systems you are authorized to inspect.
php --ini && php -mHow to prove it is fixed
Pass condition: Composer's platform check and the real PHP runtime both report compatible GD support. The validation must exercise the same path that failed originally. A successful settings screen, single ping, application homepage or idle system is not enough if the original failure appears during a different action.
Repeat the test under the original conditions once after a safe relaunch, reconnect or new session. For intermittent failures, record the time and the difference between a clean result and a failed one instead of claiming success from a single attempt.
If the symptom returns
If the problem persists, restore any test-only settings, preserve the evidence and stop before destructive reset, firmware flash or credential recreation. Give official support the exact symptom, the first failing timestamp and what the comparison established. Do not use –ignore-platform-req as a permanent compatibility fix.
Prevent recurrence: Document the working correction: Enable GD for the specific CLI PHP version or invoke the intended executable. Retain the accepted result (composer's platform check and the real PHP runtime both report compatible GD support) as a future regression test after configuration, software or hardware changes.
Solution Checklist
Questions specific to this fault
How do I know the symptom is actually resolved?
Composer's platform check and the real PHP runtime both report compatible GD support. A generic diagnostic test outside the affected workflow is not a substitute.
Should I reset or reinstall everything first?
No. Compare php –ini and php -m with the actual CLI used by Composer. Then choose the smallest supported intervention: enable GD for the specific CLI PHP version or invoke the intended executable. Preserve recoverable settings and user data.
What should I include in a support request?
Provide the exact failing action, product and version, time, non-sensitive log evidence, and this deeper observation: Check multiple PHP installations and platform-config overrides in composer.json. Do not include credentials or private customer data.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.