Bug #66860 [Nab]: Stack traces are unreadable
Edit report at https://bugs.php.net/bug.php?id=66860&edit=1
ID: 66860
User updated by: eldmannen+php at gmail dot com
Reported by: eldmannen+php at gmail dot com
Summary: Stack traces are unreadable
Status: Not a bug
Type: Bug
Package: *General Issues
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
By the way, error_prepend_string and error_append_string ought to be deprecated and removed.
Does it really belong in the ini file?
Is there any reason it should be there?
Previous Comments:
------------------------------------------------------------------------
[2014-03-09 17:27:02] eldmannen+php at gmail dot com
That would be prepend/append <pre> tags around all the errors, not only the stack trace.
I see no reason why not to wrap the stack trace in <pre> or end each stack trace line with
<br>.
Else, I think the error message should have <b> removed to be consistent.
What reason is there not to improve the markup?
Either improve the markup or remove the markup.
------------------------------------------------------------------------
[2014-03-09 17:21:46] rasmus@php.net
Use error_prepend_string/error_append_string in your ini or in an ini_set() in your script if this
bothers you.
------------------------------------------------------------------------
[2014-03-09 17:11:52] eldmannen+php at gmail dot com
@phpmpan,
Yes, and that would be the correct behaviour if I used php-cli, but I used php-cgi.
If I was not supposed to view in a web browser, then why does it contain markup such as <b>
already?
------------------------------------------------------------------------
[2014-03-09 16:57:44] rasmus@php.net
.
------------------------------------------------------------------------
[2014-03-09 16:40:43] phpmpan at mpan dot pl
The stack trace is properly formatted and broken into lines. You don't see it probably because
you view it in a browser which treats this plain-text data as HTML and strips newlines.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=66860
--
Edit this bug report at https://bugs.php.net/bug.php?id=66860&edit=1
Thread (7 messages)