| print_o | Whoops | |
|---|---|---|
| - | 6 | |
| 142 | 13,128 | |
| - | - | |
| 4.1 | 4.6 | |
| 4 months ago | 6 months ago | |
| PHP | PHP | |
| BSD 3-clause "New" or "Revised" License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
print_o
Posts with mentions or reviews of print_o.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning print_o yet.
Tracking mentions began in Dec 2020.
Whoops
Posts with mentions or reviews of Whoops.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-17.
-
Weekly help thread
To get the full control of the error output (or, rather, of the error message handling) I would suggest to use an exception handling function, set_exception_handler() I've got an example in my article on PHP error reporting. There, instead of just spitting out the raw exception, you can use the Exception class methods to get the relevant parts and either log or echo them out, depends on the server role. Or you can even include a library like Whoops that dramatically improves the output.
- error: there's a bug in your code
-
I hate PHP development
Check out spatie/laravel-ignition (if using Laravel) or filp/whoops
-
spatie/ignition is now framework agnostic and can be used as your local error handler in any PHP project
I've been using whoops but it's a bit stale (not even 7.x or 8.x native, just compatible with those but still very much 5.x code). Might have to explore ignition.
-
Does anyone know of a Go library that provides "helpful" error pages for web apps?
To give an example of what I am looking for, there is this library for PHPT: http://filp.github.io/whoops/
-
Computer crash with a debug console in a Danish public bus.
You're correct about it being a faulty webpage, but that's now what any browsers devtools look like. What you're seeing here is a whoops error page from an older version of Laravel.
What are some alternatives?
When comparing print_o and Whoops you can also consider the following projects:
Token Bucket - Implementation of the Token Bucket algorithm in PHP.
laravel-ignition - A beautiful error page for Laravel apps
PHP PassBook - iOS passbook library for PHP
PHP-GPIO - A PHP library to play with the Raspberry PI's GPIO pins
html2text - A PHP component to convert HTML into a plain text format
Hprose-PHP - Hprose is a cross-language RPC. This project is Hprose 3.0 for PHP
Jumper - PHP remote closure executor
Underscore
PHPVerbalExpressions - PHP Regular expressions made easy
Chief - Command bus package for PHP