Syntax & Parse
Parser and tokenization failures.
Practical PHP error explanations with causes, diagnosis steps, and modern fixes.
Paste a fatal, warning, SQLSTATE, or cURL message. Paths and line numbers are normalized and are not stored.
PHP errors are often more actionable than they look—if you know which fragment of the message matters. This library focuses on real diagnostic workflows: isolate the message, identify the subsystem, reproduce with the smallest input, then apply a fix that survives PHP upgrades.
Paste a full fatal/warning into the matcher, browse categories such as Composer, Xdebug, PHP-FPM, Apache, nginx, and database/SQLSTATE issues, or filter by PHP version and environment. Every guide starts near the answer—no generic “PHP is popular” filler.
Cross-link into the PHP Error Matcher, Configuration Inspector, and Composer Platform Checker when text analysis helps more than another prose page.
Parser and tokenization failures.
Variable scope and constant lookup.
Array keys, offsets, and shapes.
String operations and encoding.
Function declarations and calls.
Object model and property failures.
Name resolution and loading.
Runtime type contract violations.
Thrown and uncaught exceptions.
Non-fatal runtime diagnostics.
Version migration deprecations.
File paths, permissions, and streams.
HTTP upload handling.
Session persistence and cookies.
HTTP output ordering.
JSON parsing and encoding.
Timezone and date processing.
Resource and execution limits.
Dependency and autoload tooling.
PDO drivers and statements.
Database server errors.
Connection and authentication.
Outbound HTTP transfers.
TLS trust and certificates.
Extension loading and availability.
FastCGI process management.
Apache PHP integration.
nginx FastCGI integration.
Xdebug diagnostics.
Bytecode cache configuration.
Command-line PHP.
Scheduled PHP tasks.
WordPress runtime integration.
Laravel container and runtime.
Symfony services and runtime.
Zend Studio and Laminas runtime.
Removed and historical behavior.
Cross-version migration failures.
PHP configuration directives.
162 matching guides
| Title | Pattern | Severity |
|---|---|---|
| WordPress critical error | There has been a critical error on this website. |
fatal |
| WordPress function undefined | Fatal error: Uncaught Error: Call to undefined function wp_enqueue_script() in %s on line %d |
fatal |
| Xdebug already loaded | Cannot load Xdebug - it was already loaded |
warning |
| Xdebug could not connect to debugging client | Xdebug: [Step Debug] Could not connect to debugging client. Tried: %s:%d |
warning |
| Xdebug Docker client host unreachable | Xdebug: [Step Debug] Could not connect to debugging client. Tried: localhost:%d |
warning |
| Xdebug invalid mode | Xdebug: [Config] Invalid mode 'debugger' set for 'xdebug.mode' configuration setting |
warning |
| Xdebug legacy port 9000 mismatch | Xdebug: [Step Debug] Could not connect to debugging client. Tried: %s:9000 |
warning |
| Xdebug log permission denied | Xdebug: [Log Files] File '/var/log/xdebug.log' could not be opened. |
warning |
| Xdebug maximum function nesting level reached | Fatal error: Maximum function nesting level of '256' reached, aborting! |
fatal |
| Xdebug profiler output could not be opened | Xdebug: [Profiler] File '/tmp/cachegrind.out.123' could not be opened. |
warning |
| Xdebug trace file could not be opened | Xdebug: [Tracing] File '/traces/trace.123.xt' could not be opened. |
warning |
| Zend Studio legacy Xdebug configuration | Xdebug: [Config] The setting 'xdebug.remote_enable' has been renamed |
warning |
Paste the distinctive message fragment or the full fatal/warning line. Dynamic paths and line numbers are normalized automatically.
No. They are practical troubleshooting guides that complement php.net, Composer, Xdebug, and server documentation.