I just tested notice generation on PHP-GTK 1.0.0 on
Windows by using an undefined variable.
$var = fopen($_GET['test'], 'r');
I have error_reporting set to
error_reporting = E_ALL & ~E_NOTICE
in php.ini, and any notices are suppressed in my custom error log set in php.ini unless I specify error_reporting(E_ALL); earlier in the script. As far as I know, the default PHP-GTK configuration works fine, so I would look towards the script itself.
Do you recall what changes have occurred when the notices were initially being written to the error log? Do you have any error tracking functions/classes in your application that may be sending notices to the log?
Also, do you run this script via command line?
Sorry for the delay on this response. We've been socked in with an ice storm and no power for a few days.
I think I can track the problem back to an attempt to run the new PHP-Gtk release (1.0.0), which is listed on the site. Everything ran okay, but that's when we started seeing the problem with the error file.
We decided that the new release wasn't buying us anything we needed, so we backed it all out and returned to the 0.5.2 version. None of the files from the 1.0.0 are there, but the notice problem is.
We run the app from a bat file, using the PHP/Gtk wrapper. The command is as follows:
cd c:\PM\php4
php_gtk.exe "c:\PM\PracticePlus\PMMain.php"Everything works just fine, except for the notices. The PMMain.php is a simplistic API, with just a few lines: the dll check, some globals, some includes and a call to the main logon screen. The very first notice occurs with the logon screen, when we do a check on a variable that may or may not exist.
thanks, Madeleine D.
-- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
