Re: [PHP] web browser shows blank page when accessing *.php file

2006-10-02 Thread Anna Barnes
Dear All I just thought I'd drop you a line about how I fixed this in the end. I had an idea that because the ical I was loading had about 24months worth of data it was taking too long so I just created a new one and published that. It now works, however, it does stall sometimes in which

[PHP] web browser shows blank page when accessing *.php file

2006-09-21 Thread Anna Barnes
We are publishing an ical calendar from a mac on a webserver running apache on solaris 8. However, its suddenly stopped working via webrowser. I have tried to stop and start the httpd to get it going again but to no avail. when I access through safari or explorer on OSX.4 the access_log

Re: [PHP] web browser shows blank page when accessing *.php file

2006-09-21 Thread Martin Marques
On Thu, 21 Sep 2006 17:13:44 -0400, Anna Barnes [EMAIL PROTECTED] wrote: and the error_log file says [Tue Sep 19 15:53:57 2006] [error] PHP Fatal error: Maximum execution time of 60 seconds exceeded in /websites/ical/functions/ ical_parser.php on line 494 What is there in line 494 of

Re: [PHP] web browser shows blank page when accessing *.php file

2006-09-21 Thread Curt Zirzow
On 9/21/06, Anna Barnes [EMAIL PROTECTED] wrote: We are publishing an ical calendar from a mac on a webserver running apache on solaris 8. However, its suddenly stopped working via webrowser. I have tried to stop and start the httpd to get it going again but to no avail. when I access through

Re: [PHP] web browser shows blank page when accessing *.php file

2006-09-21 Thread anna barnes
Hi Curt and Martin, Thanks for getting back to me. I'll take a look at the exact line 474 tomorrow. The reason I didn't mention it specifically is that it's only suddenly stopped working and nothing in that code has changed. It doesn't work in any browser, netscape, IE, firefox etc on

Re: [PHP] web browser shows blank page when accessing *.php file

2006-09-21 Thread Curt Zirzow
On 9/21/06, anna barnes [EMAIL PROTECTED] wrote: Hi Curt and Martin, Thanks for getting back to me. I'll take a look at the exact line 474 tomorrow. The reason I didn't mention it specifically is that it's only suddenly stopped working and nothing in that code has changed. It doesn't work in