*waves*

Struggling to get WDL to work,

When I try to look at/load your wdlconfig.xml file I get “Parse error: parse error, unexpected T_STRING in /storage3/home2/mardibloke.co.uk/wdlconfig.xml on line 1”. My guess is a typo of some sort in the xml file.

This is the config file location from your weatherindex.html, http://www.mardibloke.co.uk/wdlconfig.xml, is that where wdl files are?

can you copy and paste the first few lines of you wdlconfig.xml file here?

Its unmodified straight from the install zip file…

<?xml version="1.0" encoding="utf-8" ?> evaluation 4 3 dd/mm/yyyy 1

Just installed a local web server here, and works as expected.

Something fishy about the way my ISP is setup I guess.

Real shame as that’s a complete showstopper to me purchasing the software :frowning:

Hey - it works now :lol: #-o

Gosh

Working, when I removed the first line as you suggested

How very odd, I just downloaded the install file and unzipped again - and that first line is certainly there.

Wonder why its not given anyone else grief?

Thanks so much for the prompt and spot on advice [+]

i actually removed my suggestion to remove the xml tag when I realised it was there in my local xml template as well as I thought I was barking up the wrong tree - but it works now so all is well in the end!!

Yes its there in mine too - I just double checked. And it causes me (or should I say my isp) no problems. Maybe Julian has an answer ?

That sounds more like a php error to me. You have some php code parsing stuff there ?



also, though, you need to set the full URL to the clientraw.txt, clientrawextra.txt and clientrawdaily.txt files in this section…

<?xml version="1.0" encoding="utf-8" ?> is part of the specification of xml. It is an XML declaration which specifies the version of XML being used "to indicate conformance to this version of this specification" and the character encoding. According to w3c "Processors may signal an error if they receive documents labeled with versions they do not support" so it may be a problem with the server not understanding xml.

More information can be found at http://www.w3.org for anyone interested.

Julian

If the server is running Apache there might be a problem with the mime types (often /etc/mime.types). If the server was set to say that XML files were to be handled using PHP then this might give an error from PHP.

mardibloke it may be worth asking your ISP how they handle xml? maybe they don’t have any customers using it??

I only say this because not long back I had to deal with my hosting provider to get WAP mime types set up as they did not have them - apparently I was their first customer to ask for WAP functionality !!! :lol: 8O

also, though, you need to set the full URL to the clientraw.txt, clientrawextra.txt and clientrawdaily.txt files in this section..

Oh - I don’t have anything in those tags in mine either and it works just dandy, but then all the files are in the same directory on the server too.

Looking like they have XML associated with PHP - the ISP is not keen to change it in case it causes a problem somewhere else. As its now working just fine for me, no point in me hassling the ISP.

I’d have thought that associating XML with PHP is likely to cause them more problems in the future than dissociating it now. XML is being used more and more these days and as PHP can’t parse XML files I can’t think what benefit they think they’re getting from leaving it as it is.