Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Human readable error_log

20 views
Skip to first unread message

August Karlstrom

unread,
Oct 8, 2008, 6:27:12 PM10/8/08
to
Hi,

I'm looking for a function that *returns* a human readable string
representation of an array rather than prints it so I can use it with
the error_log procedure. Any clues?


August

Curtis

unread,
Oct 8, 2008, 9:06:26 PM10/8/08
to

You can use output buffering, or write a function that suits your own
needs.

<URL:http://php.net/manual/en/ref.outcontrol.php>

--
Curtis

macca

unread,
Oct 8, 2008, 10:10:32 PM10/8/08
to

$string = print_r($array,1);

The second param of print_r() is a bool for return value. If true,
print_r() returns the string to your variable instead of printing to
the screen.

RTM here:

http://uk.php.net/manual/en/function.print-r.php

August Karlstrom

unread,
Oct 9, 2008, 4:09:00 AM10/9/08
to

Thanks. I still have a problem though. For some reason the output
contains sequences of `\n' instead of newlines.

Example:

error_log(print_r(Array(1, 2, 3), 1));

Output:

[Thu Oct 09 10:06:37 2008] [error] [client 127.0.0.1] Array\n(\n [0]
=> 1\n [1] => 2\n [2] => 3\n)\n, referer: ...


August

"Álvaro G. Vicario"

unread,
Oct 9, 2008, 4:37:06 AM10/9/08
to
August Karlstrom escribió:

> Thanks. I still have a problem though. For some reason the output
> contains sequences of `\n' instead of newlines.
>
> Example:
>
> error_log(print_r(Array(1, 2, 3), 1));
>
> Output:
>
> [Thu Oct 09 10:06:37 2008] [error] [client 127.0.0.1] Array\n(\n [0]
> => 1\n [1] => 2\n [2] => 3\n)\n, referer: ...

error_log() sends errors either to a file or to system logging; the
latter might not support multi-line output. I've tried this code in
Windows XP from command line:

<?php
ini_set('log_errors', 1);
ini_set('error_log', 'error.log');
error_log(print_r(Array(1, 2, 3), 1));
?>

It does save line feeds, but it mixes different line endings:
- Lines themselves use Windows line endings (\r\n)
- print_r() uses Unix line endings (\n)

So the log looks ugly in Notepad but looks normal in almost any other
editor. Your customer logger can take care of that. This works for me:

<?php
ini_set('log_errors', 1);
ini_set('error_log', 'error.log');
error_log(
strtr(
print_r(Array(1, 2, 3), 1),
array(
"\r\n" => PHP_EOL,
"\r" => PHP_EOL,
"\n" => PHP_EOL,
)
)
);
?>


--
-- http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web: http://bits.demogracia.com
-- Mi web de humor al baño María: http://www.demogracia.com
--

August Karlstrom

unread,
Oct 10, 2008, 6:48:28 AM10/10/08
to
Álvaro G. Vicario wrote:
> August Karlstrom escribió:
>> Thanks. I still have a problem though. For some reason the output
>> contains sequences of `\n' instead of newlines.
>>
>> Example:
>>
>> error_log(print_r(Array(1, 2, 3), 1));
>>
>> Output:
>>
>> [Thu Oct 09 10:06:37 2008] [error] [client 127.0.0.1] Array\n(\n
>> [0] => 1\n [1] => 2\n [2] => 3\n)\n, referer: ...
>
> error_log() sends errors either to a file or to system logging; the
> latter might not support multi-line output.
[...]

OK, thanks for the information Álvaro.


August

0 new messages