HTML has just this:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
Either a fatal error right at the beginning, or, more likely, file got corrupted while being transferred to your server. I would try re-uploading the index file (or the file that is included right at the top). Or post the code of the page, the line that is right below the last line of the code I posted above, if there is an error it would probably be in that one.
You could also try inserting this PHP code somewhere at the top of the page:
error_reporting(E_ALL);
It started working again.........that is strange. I did reboot the computer running the weather software. But I did not think there was anything that edits the index file.
Thank you for the help!
and its down again....I emailed my ISP and godaddy. see if any of them know what is going on.
its strange....
Fatal error caused by PHP errors in testtags.phpWhen index.php is loaded it first start loading a lot of other scripts. Most of them do not change so when they are correct, they remain correct.
index.php loads top.php
top.php loads settings.php and common.php
Then top.php outputs the few lines Jáchym showed .
So we know we are at line 61 of top.php, check here
http://desotowiwx.com/check-fetch-times.php?show=structureAt that line and below your tags file, testtags.php is loaded and a php error kills all subsequent loading of scripts => result a blank page (with some hidden html to inspect).
The blank page occurs as there is a parser error reading the testtags.php file. The error is often caused by
1. special characters (quotes or other special php characters) in forecast texts, names, metar conditions
2. incomplete / no data in fields with missing quotation marks
3. incomplete or yet unfinished upload.
When this blank page happens again:1. make a copy of the testtags.php on your webserver
2. and give it a name such as testtags-error.txt
3. post that file so all of us can check it and see which tag causes the error.
If it is an error 1 or 2: As not all tags are used from the huge testtags.php file, most of the times commenting the offending line in C:\wdisplay\webfiles\testtags.txt is a good solution.
If it is error 3, an incomplete file you should instruct WD to upload the file as testtags-new.php
The template scripts test if that file testtags-new.php exist
and if so it is checked to be complete
and if so the file is renamed to testtags.php
That way an incomplete upload is not used, only completed uploads.
My advice would be, to always upload the file as testtags
-new.php when using a recent Saratoga site.
That removes a lot of blank screens and the like caused by access conflicts when
the
fast web-server wants to read testtags.php
but the always "
slow" FTP uploading is still taking place.
Wim