Timeline for How can I get useful error messages in PHP?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 19, 2019 at 19:16 | history | post merged (destination) | |||
| Jan 16, 2019 at 10:58 | comment | added | Tom | If you cannot modify php.ini, create a .htaccess file with php_flag display_errors 1 in it. | |
| Mar 22, 2017 at 8:19 | history | edited | Jens | CC BY-SA 3.0 | added 6 characters in body |
| Aug 10, 2015 at 15:09 | history | edited | Muhammad Reda | CC BY-SA 3.0 | Fix a typo. |
| May 30, 2011 at 23:44 | comment | added | Matthew Scharley | Coming back to this, I recently had a stack overflow issue that wasn't generating any errors, even in the logs and didn't manifest itself as such till I installed xdebug into the server. Gah. | |
| Sep 25, 2009 at 7:00 | vote | accept | Matthew Scharley | ||
| S Nov 19, 2019 at 19:16 | |||||
| Sep 25, 2009 at 6:51 | comment | added | Guss | Parse errors should be visible in the Apache's error log, regardless of what setting you have anywhere else. If you don't have control over the server then getting the apache error log might be difficult, but I suggest you talk with your provider and there are ways to expose the error log to you. Other then that, I can only suggest what other have - vet your code for parsing errors in your local development server before you deploy to production. Also, a validating IDE such as Eclipse's PDT might be of great help. | |
| Sep 25, 2009 at 4:40 | comment | added | Matthew Scharley | Sadly, view page source displays nothing too. | |
| Sep 25, 2009 at 4:22 | history | answered | James Anderson | CC BY-SA 2.5 |