On 12/23/2011 8:13 AM, Floyd Resler wrote:
> I know this is a very basic question and I'm almost embarrassed to ask it,
> but it's something I really struggle with. That is, getting the right
> combination of error reporting options together to report the errors I want.
> Right now, I get the
I know this is a very basic question and I'm almost embarrassed to ask it, but
it's something I really struggle with. That is, getting the right combination
of error reporting options together to report the errors I want. Right now, I
get the errors I want except for parse errors. Basically,
our disabling function is malformed.
>
>
>
> Richard L. Buskirk
>
>
>
> -Original Message-
> From: Mike Mackintosh [mailto:mike.mackint...@angrystatic.com]
> Sent: Monday, May 09, 2011 10:34 PM
> To: php-general@lists.php.net
> Subject: [PHP] Error Report
malformed.
Richard L. Buskirk
-Original Message-
From: Mike Mackintosh [mailto:mike.mackint...@angrystatic.com]
Sent: Monday, May 09, 2011 10:34 PM
To: php-general@lists.php.net
Subject: [PHP] Error Reporting/Display Errors Issues?
Anyone else notice PHP throwing Warning and Notices
You may need to check the running php code, those values can be
changed during runtime.
2011/5/10 Mike Mackintosh :
> Anyone else notice PHP throwing Warning and Notices even when display errors
> and error reporting disabled?
>
> I compiled PHP with the following:
>
> './configure' '--prefix=/
Anyone else notice PHP throwing Warning and Notices even when display errors
and error reporting disabled?
I compiled PHP with the following:
'./configure' '--prefix=/usr/local/php-5.3.3' '--enable-cli' '--disable-debug'
'--disable-rpath' '--disable-static' '--with-pic' '--with-openssl=/usr' '
E_STRICT only shows one type of error. If you want everything than you
need to set E_ALL | E_STRICT
http://usphp.com/manual/en/errorfunc.constants.php#errorfunc.constants.errorlevels.e-strict
Thank you,
Micah Gersten
onShore Networks
Internal Developer
http://www.onshore.com
Naz wrote:
> I am
I am trying to turn on errors in the browser, but for some reason they
are being suppressed.
In php.ini I have display_errors = On and error_reporting = E_STRICT
What else could be suppressing errors?
السلام عليكم
- Naz.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit:
I'm running PHP 5.1 on IIS. My dev environment is all local on my
machine. My php.ini has the following error reporting settings:
error_reporting = E_ALL
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_sou
On Tue, July 25, 2006 10:32 am, James Nunnerley wrote:
> We've created a file manager which allows users to access their web
> space on
> a server. It's working brilliantly, except that it would seem there
> are
> some caching issues, either by the system cache or the web server
> cache that
> are
James Nunnerley wrote:
>> [snip]
>> When the script tries to delete a file, we always check (using
>> file_exists) to see whether the file exists before it's deleted.
>>
>> The check comes back true, but the unlink then fails, saying no file or
>> directory there!
>> [/snip]
>>
>> Could you please
> [snip]
> When the script tries to delete a file, we always check (using
> file_exists) to see whether the file exists before it's deleted.
>
> The check comes back true, but the unlink then fails, saying no file or
> directory there!
> [/snip]
>
> Could you please post the code you are using to c
You could try prefixing the unlink function call with an @:
if (file_exists($fn)) {
@unlink($fn);
}
The @ should suppress any errors.
jon
James Nunnerley wrote:
We've created a file manager which allows users to access their web space on
a server. It's working brilliantly, except that it
We've created a file manager which allows users to access their web space on
a server. It's working brilliantly, except that it would seem there are
some caching issues, either by the system cache or the web server cache that
are causing us a headache.
When the script tries to delete a file, we a
-Original Message-
From: ngwarai zed [mailto:[EMAIL PROTECTED]
Sent: 30 March 2006 13:36
I am using Fedora core 4. yes I stopped and restarted apache
On 3/30/06, Ford, Mike wrote:
On 29 March 2006 15:25, ngwarai zed wrote:
> phpinfo says
>
> Configuration File (php.ini) Path /
On 29 March 2006 15:25, ngwarai zed wrote:
> phpinfo says
>
> Configuration File (php.ini) Path /etc/php.ini
>
> And the file I am editing is /etc/php.ini Is this not the
> one Iam supposed to edit?
On list please!
H'mmm -- file permissions? You've stopped and restarted Apache? Which
oper
On Wed, 2006-03-29 at 16:38 +0300, ngwarai zed wrote:
> I tried changing display_errors = On and error_reporting = On in
> php.ini , restarted httpd but when I check with phpinfo() I still see
> display_errors set to Off and error_reporting set to 2047. My php
> script still does not show any error
On Wed, 2006-03-29 at 18:25 +0300, ngwarai zed wrote:
> But still the problem is not solved. Just to recap on the problem: I
> just want the deliberate php errors Imake to shown as errors on the
> php page when the script runs.
Yes, that should be the normal behaviour. Check your error_reporting
s
Thanks Christopher for your help. I followed you numbered advicestep by
step.
1) I verified that there weren't any typo's that were causing fatal problems
in my php.ini
2) looked at the output of phpinfo() and verified the location of the
php.ini script. /etc/php.ini .This is the file I am modif
> -Original Message-
> From: ngwarai zed [mailto:[EMAIL PROTECTED]
> Sent: 29 March 2006 14:39
> To: Christopher Murtagh
> The problem is I know what the error is. What I want is for
> the error to be shown when I run the script not to be just
> written to the error log. I tried changin
I checked the apache error log and the error is written there just as I
expected like below.
[client 127.0.0.1] PHP Parse error: parse error, unexpected T_STRING,
expecting ',' or ';' on line 90, referer: http://localhost/form.html
The problem is I know what the error is. What I want is for th
At 10:57 AM 3/28/2006, ngwarai zed wrote:
hi, I omitted a semicolon ; at the end of a php statement on purpose to see
what the error looks like. I ran the script and a blank page just came
out.No error message. I then edited php.ini and set Display_errors = On and
errror_reporting = E_ALL then
ngwarai zed wrote:
hi, I omitted a semicolon ; at the end of a php statement on purpose to see
what the error looks like. I ran the script and a blank page just came
out.No error message. I then edited php.ini and set Display_errors = On and
errror_reporting = E_ALL then restarted httpd. Ran t
hi, I omitted a semicolon ; at the end of a php statement on purpose to see
what the error looks like. I ran the script and a blank page just came
out.No error message. I then edited php.ini and set Display_errors = On and
errror_reporting = E_ALL then restarted httpd. Ran the script again and
Bob Hartung wrote:
Jasper
If if make a file containing only
I get what I expected.
take a good look at where php is reading its ini file from
- it may not be where you expect
If I make a file containing
'void' is not a php keyword. that would give a parse error
{
It wasn't what I was looking for but I enable it:
include_path = ".:/php/includes"
This was commented out. After uncommenting it all works as I expected
except that my syntax in the class was wrong. Now I can at least start
to learn.
Thanks Jasper and Derek - you gave me a shove in the
On Sun, 2005-10-23 at 23:01 -0400, Bob Hartung wrote:
> Jasper & Derek
>
>phpinfo() says:
> configuration file path /etc/php.ini
>
>PHP Core
>DirectiveLocal Value Master Value
>
> display_errorsOff Off
> error_log
Jasper & Derek
phpinfo() says:
configuration file path /etc/php.ini
PHP Core
DirectiveLocal Value Master Value
display_errorsOff Off
error_logno value no value
log errorson
Bob Hartung wrote:
Jasper
If if make a file containing only
I get what I expected.
If I make a file containing
I get NO output or errors in the browser window. If I select "view
source" it returns:
Eh? Anyone with any other ideas
Tnx
Bob Hartung
Jasper Bryant-Greene wrot
On Sun, 2005-10-23 at 21:31 -0400, Bob Hartung wrote:
> Jasper
>If if make a file containing only
> phpinfo() ;
>?>
>I get what I expected.
>
>If I make a file containing
>
> phpinfo() ;
>
> // Now a simple class and a call to the class
> class Simple()
Your erro
Jasper
If if make a file containing only
I get what I expected.
If I make a file containing
I get NO output or errors in the browser window. If I select "view
source" it returns:
Eh? Anyone with any other ideas
Tnx
Bob Hartung
Jasper Bryant-Greene wrote:
http://www.php.ne
On Sun, 2005-10-23 at 17:31 -0400, Bob Hartung wrote:
> Hi all,
>Slowly I'm progressing.
>Now how to turn error reporting on for a test apache server.
>
>I have made the following changes to /etc/php.ini:
>
>error_reporting = E_ALL
>display_errors = On
>error_l
Hi all,
Slowly I'm progressing.
Now how to turn error reporting on for a test apache server.
I have made the following changes to /etc/php.ini:
error_reporting = E_ALL
display_errors = On
error_log = /var/log/php_errors
On errors I still have no in browser display nor
I ave a strange problem with my error reporting!
I have set php.ini to: error_reporting = E_ALL but I don't see any
errors.
(After I was happy things were working on my Apache Test Server, I
uploaded
to my web host and discovered errors.)
Make sure that display_errors is on and that you restart
I ave a strange problem with my error reporting!
I have set php.ini to: error_reporting = E_ALL but I don't see any errors.
(After I was happy things were working on my Apache Test Server, I uploaded
to my web host and discovered errors.)
Thanks,
Tom
--
PHP General Mailing List (http://www.php
>
Cc: <>
Sent: Monday, January 19, 2004 2:53 PM
Subject: Re: [PHP] Error Reporting help
> Chris Edwards wrote:
> > but do I need to do something to
> > get PHP to actually work off of these setting once they have been
changed,
>
> Restart your web server.
>
>
On Tuesday 20 January 2004 03:44, Chris Edwards wrote:
> Here's a snippet from my PHI_INI
>
> ; - Show all errors
> ;
> error_reporting = E_ALL
> ;error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING & ~E_CORE_WARNING &
> ~E_USER_WARNING & ~E_USER_NOTICE & ~E_COMPILE_WARNING
>
> display_errors =
Chris Edwards wrote:
but do I need to do something to
get PHP to actually work off of these setting once they have been changed,
Restart your web server.
--
---John Holmes...
Amazon Wishlist: www.amazon.com/o/registry/3BEXC84AB3A5E/
php|architect: The Magazine for PHP Professionals – www.phparch.
Here's a snippet from my PHI_INI
; - Show all errors
;
error_reporting = E_ALL
;error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING & ~E_CORE_WARNING &
~E_USER_WARNING & ~E_USER_NOTICE & ~E_COMPILE_WARNING
display_errors = On
The commented out error_reporting was the original setting and
"dis
On Monday 19 January 2004 22:34, Chris Edwards wrote:
> I retried most of the combinations and still cannot get it to report syntax
> errors. If I have errors, from say undefined variables, the error handler
> catches those just fine.
Again:
> > But if "display_errors" (in php.ini) is disabled t
Thanks for all you replies, most of what you have suggested, I had already
tried, in vain, before joining the list.
I retried most of the combinations and still cannot get it to report syntax
errors. If I have errors, from say undefined variables, the error handler
catches those just fine.
Questi
On Monday 19 January 2004 07:30, Chris Edwards wrote:
> It's almost like it parses it before it tries to execute any lines and if a
> syntax error occurs, it doesn't execute any of the script.
That's right.
> The prior version would run up until the syntax error and then give you the
> line if e
Tried that, thanks, no joy.
It's almost like it parses it before it tries to execute any lines and if a
syntax error occurs, it doesn't execute any of the script.
The prior version would run up until the syntax error and then give you the
line if error, which usually meant the syntax error was on
Chris Edwards wrote:
My hosting company recently upgraded to PHP 4.3.0. Since doing this I no
longer get syntax type errors, from my typo's inside my PHP scripts. These
use to come up in my browser when that page was requested and the script
run.
You probably need to have them turn on display_error
Chris Edwards wrote:
[cut]
> For example if I code
>
> echo "This is a syntax error because of the double quote start and the
> single quote end ';
>
> I just get a blank screen.
>
> I have 14 pages of PHP settings printed out, so for any kind person that can
> help, I can respond wit
My hosting company recently upgraded to PHP 4.3.0. Since doing this I no
longer get syntax type errors, from my typo's inside my PHP scripts. These
use to come up in my browser when that page was requested and the script
run.
I have spent hours going through the online help, trying to set a number
>Heh yes umm i know this. But how i could i catch this before is spits out
>to an ugly error page so i can send to a custom error page.
Why would anyone but you ever see a parse error? It's the sort of thing
you fix before setting up custom error handling. :)
-
> ---John Holmes...
>
> Amazon Wishlist: www.amazon.com/o/registry/3BEXC84AB3A5E/
>
> php|architect: The Magazine for PHP Professionals www.phparch.com
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
Heh yes umm i know this. But how i
[EMAIL PROTECTED] wrote:
on the topic of error reporting, am i able to catch fatal/parse errors yet ?
How could a PHP script catch a Parse Error? The script hasn't started
because there is, ummm, a Parse Error! :)
--
---John Holmes...
Amazon Wishlist: www.amazon.com/o/registry/3BEXC84AB3A5E/
ph
on the topic of error reporting, am i able to catch fatal/parse errors yet ?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
on 10/16/03 16:51, John W. Holmes at [EMAIL PROTECTED] wrote:
> Richard Baskett wrote:
>> If I use:
>>
>> ini_set("error_reporting", 0);
>> ini_set("display_errors", 0);
>>
>> It still shows the errors.. if I use the error_reporting function.. it still
>> shows the errors, no matter what I do..
on 10/16/03 16:51, John W. Holmes at [EMAIL PROTECTED] wrote:
> Richard Baskett wrote:
>> If I use:
>>
>> ini_set("error_reporting", 0);
>> ini_set("display_errors", 0);
>>
>> It still shows the errors.. if I use the error_reporting function.. it still
>> shows the errors, no matter what I do..
Richard Baskett wrote:
If I use:
ini_set("error_reporting", 0);
ini_set("display_errors", 0);
It still shows the errors.. if I use the error_reporting function.. it still
shows the errors, no matter what I do.. it still shows the errors!
What am I missing? I have it set in the php,ini to show err
If I use:
ini_set("error_reporting", 0);
ini_set("display_errors", 0);
It still shows the errors.. if I use the error_reporting function.. it still
shows the errors, no matter what I do.. it still shows the errors!
What am I missing? I have it set in the php,ini to show errors, but I want
to be
Thanks. That did the trick. According to a post from Mike Ford, it was
ini_set( 'display_errors', 1 ); that was messing me up. I have
display_error turrned off in php.ini too, so even though my reporting was
on, nothing was sent to the browser. Thanks for the help guys :)
- Anthony
"Robert C
> -Original Message-
> From: Anthony [mailto:[EMAIL PROTECTED]
> Sent: 25 June 2003 12:36
>
> I have error reporting turned off in my php.ini file on my production
> server. I have an app I'm writing that I need to run on the
> same server (no
> one can see it though). Anyway. I want t
This is hardly perfect since it shows all errors, but it works for me:
ini_set( 'display_errors', 1 );
ini_set( 'log_errors', 1 );
ini_set( 'error_reporting', -1 );
Anthony wrote:
>
> I have error reporting turned off in my php.ini file on my production
> server. I have an
I have error reporting turned off in my php.ini file on my production
server. I have an app I'm writing that I need to run on the same server (no
one can see it though). Anyway. I want to turn on error reporting during
runtime for this particular app while I'm debugging it. so I put
error_repor
Not possible with current php
Bas Jobsen wrote:
Hi,
Running the code below, shows an errror in line 2 as expected.
How do i get the linenumber of the function call? 3 here.
function test($x){if($x!='a')trigger_error('error: call test with argument 1
equals a',E_USER_ERROR);}
test('b');
?>
Best
> -Original Message-
> From: Bas Jobsen [mailto:[EMAIL PROTECTED]
> Sent: 16 June 2003 14:39
>
> > I'm not sure that there is a way beyond this to show the
> line within the
> > function but I don't see that this would be necessary - at
> least not for
> > resolving errors.
>
> i'm buil
which produced the error.
>
> I'm not sure that there is a way beyond this to show the line within the
> function but I don't see that this would be necessary - at least not for
> resolving errors.
>
> HTH,
>
> Michael Egan
>
> -Original Message-
>
Use the predefined constant:
__LINE__
Regards,
Michael Egan
-Original Message-
From: Bas Jobsen [mailto:[EMAIL PROTECTED]
Sent: 16 June 2003 12:50
To: PHP General
Subject: [PHP] error reporting linenumber and filename[Scanned]
Hi,
Running the code below, shows an errror in line 2 as
Hi,
Running the code below, shows an errror in line 2 as expected.
How do i get the linenumber of the function call? 3 here.
Best regards,
Bas
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
start your file with :
error_reporting(E_ALL);
Op woensdag 14 augustus 2002 20:09, schreef Georgie Casey:
> rite,
>
> without access to the php.ini file, how can i get php to print all errors
> on my web server. it runs linux
> --
> Regards,
> Georgie Casey
> [EMAIL PROTECTED]
>
> ***
rite,
without access to the php.ini file, how can i get php to print all errors on
my web server. it runs linux
--
Regards,
Georgie Casey
[EMAIL PROTECTED]
***
http://www.filmfind.tv
Online Film Production Directory
***
--
PHP General Mailing L
On Monday 10 June 2002 09:42, Scott 'INtense!' Reismanis wrote:
> Hey all,
>
> I recently installed Apache2, PHP4.2 on my win2k box as a module. It
> works fine however say a script has a syntax error all that happens is a
> blank screen is displayed. No errors are shown and thus it is very hard
>
Hey all,
I recently installed Apache2, PHP4.2 on my win2k box as a module. It
works fine however say a script has a syntax error all that happens is a
blank screen is displayed. No errors are shown and thus it is very hard
to debug when I don't know what the error is, and what line it occurs
on.
Hi,
On my local test server (PHP4.0.1, FreeBSD, MySQL), when I
get a general error (bad code) it reports "error on
on line 1".
It allways says "line 1", even if it's line 4028.
I've had experience with this happening if there is a
structure problem with { brackets } missing (on any server)
Is there any way to see my errors on he screen. The server has error
reporting turned off.
Ive tried setting error_reporting()function setting it to E_ALL etc. It still
does not work.
Does any one know what I can do?
Clint
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-m
manesh,
its in your php.ini file under error handling and logging...
seek and ye shall find...
-jack
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL
70 matches
Mail list logo
