At 7:04 PM + 12/8/10, Ashley Sheridan wrote:
I'd also check any errors logs for this site made by Apache, as that
will tell you where PHP is falling over. If you have access to the
whole server run a 'tail -f' command in a terminal and go to your
site again in the browser, that way, you'll
On Wed, 2010-12-08 at 13:16 -0500, tedd wrote:
> At 2:07 AM +0100 12/8/10, Rico Secada wrote:
> >Hi.
> >
> >What can cause that no parse error gets displayed (blank page/no output
> >at all) even though error reporting is set to "-1"?
> >
> >I have run the script through php lint on the console an
At 2:07 AM +0100 12/8/10, Rico Secada wrote:
Hi.
What can cause that no parse error gets displayed (blank page/no output
at all) even though error reporting is set to "-1"?
I have run the script through php lint on the console and it comes up
with no errors.
I have run into this problem the la
wats the setting of display_errors php.net/display_errors ?
if you are not getting any output it might be because of a simple
parse error (mismatched brackets, misplaced semicolon etc) or an
exit/die command
Kranthi.
http://goo.gl/e6t3
--
PHP General Mailing List (http://www.php.net/)
To unsubs
Hi.
What can cause that no parse error gets displayed (blank page/no output
at all) even though error reporting is set to "-1"?
I have run the script through php lint on the console and it comes up
with no errors.
I have run into this problem the last couple of days making debugging a
nightmare
GOT IT,
basically in a script like this
php treats these as contants, and issues a notice saying that undefined
constants are being used. The default setting for the php.ini file is :
error_reporting = E_ALL &~E_NOTICE
thus all notices are not displayed. setting error_reporting to E_ALL s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
Check these three ini settings,
log_errors
display_errors
error_log
My guess is the you have log_errors on, display_errors off, & error_log as
your apache access log.
HTH!
~Pauly
On Thursday 03 October 2002 04:20 am, gamin wrote:
> Yes,
>
>
Yes,
Short tags should be On, cause
results in the exptected page.
Still unable to understand why this is happening, here are some of the
following code snippets with the errors:
NO ERROR REPORTED FROM PHP
[results in the Apache/access.log] 127.0.0.1 - - [03/Oct/2002:13:33:49
+0530] "G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
Is short_tags on?
~Pauly
On Wednesday 02 October 2002 05:51 pm, gamin wrote:
> hi,
>
> i'm running PHP 4.0.6 with apache on RedHat 7.2 , error_reporing is set
> to default(2039) in the php.ini file :
> my script is as follows :
>
> qwe;
>
>
>
I noticed that by default, my display_errors was actually OFF, and the
only way to see my errors was through Apache's error.log file
I don't know if that's already been checked, but... figured I'd try to help.
-Jason
Gamin wrote:
> Yes,
>
> On both my development machine and implmetation ma
Yes,
On both my development machine and implmetation machine i have the same
error_reporting.
error_reporing = 2039 (that is what phpinfo() gives me ) is equivalent
to E_ALL^E_NOTICE. And still i cant seem to get any error, even on a winxp
system running Apache and PHP 4.2.1 (from the php.i
Shot in the dark that may or may not help... Look into display_errors
and log_errors. I think those are the names. They control where error
output goes.
Cheers,
Rob.
gamin wrote:
>
> hi,
>
> i'm running PHP 4.0.6 with apache on RedHat 7.2 , error_reporing is set to
> default(2039) in the php
inal Message -
From: "gamin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 02, 2002 3:51 PM
Subject: [PHP] no errors ?
> hi,
>
> i'm running PHP 4.0.6 with apache on RedHat 7.2 , error_reporing is set
to
> default(2039) in t
hi,
i'm running PHP 4.0.6 with apache on RedHat 7.2 , error_reporing is set to
default(2039) in the php.ini file :
my script is as follows :
But i dont get even a parse error or anything
Any clues to what is going wrong ?
thx
gamin.
--
PHP General Mailing List (http://www.php.net/)
To
14 matches
Mail list logo