PHP Troubleshooting
This article provides some of the common issues with getting your applications to work as designed.
If the application exhibits unexpected behavior it is a good habit to check the error logs ( error-log-0 ) in the application's logs directory. The following table also presents some possible causes of errors.
| Symptom | Possible cause(s) | Confirmation | Remediation |
|---|---|---|---|
| None of the files in the application's public directory can be browsed | Application not started or could not start | Application does not appear in process list | See Application Startup issues |
| Application startup issues | Port conflict (default port for all applications is 8080) | Verify address in use error in error-log file | Change the port number in zero.config
[/config] http/port |
| PHP files do not render in Web browser | |||
| Missing zero.php dependency | Verify that there is a dependency in the config/ivy.xml file. Verify that there is an entry for zero.php. | Add a dependency to zero.php | |
| Missing php.ini file | Confirm that there is a FileNotFoundException in logs/error-log-0 file for config/php.ini | Create an empty php.ini file in the config directory and restart app. |
How do I enable logging and tracing ?
Use the/config/logging/levels attribute to configure the logging levels in your zero.config.
As described in the Core troubleshooting article, the value of this attribute is a map of logger names and logging level pairs.
The following example shows how to set the logging levels for zero.php.
/config/logging/levels = {
"zero.php" : "FINEST"
}
