According to the error report, you have CDATA littered between your 'many Walls'. Which, since you probably didn't add real CDATA (as it wouldn't make sense), means you have illegal XML in those positions.
Z-Man wrote:According to the error report, you have CDATA littered between your 'many Walls'. Which, since you probably didn't add real CDATA (as it wouldn't make sense), means you have illegal XML in those positions.
Hmm I really have little idea what CDATA means... (character data maybe?)
Since I don't see any problems with walls I am wondering if it is the PHP Backslash expressions I have...
Yeah, CDATA stands for 'character data'. When used intentionally, it's a way to get otherwise illegal texts into XML. However, libxml uses CDATA in parser error messages to denote random junk, like any text between tags.
When I copy that into the body from earlier, I get no errors and a working map. Which is odd. The php looks fine; I wouldn't use \r and \t at all (and you should try without them), but they're legal whitespace and should get ignored completely.
Z-Man wrote:Yeah, CDATA stands for 'character data'. When used intentionally, it's a way to get otherwise illegal texts into XML. However, libxml uses CDATA in parser error messages to denote random junk, like any text between tags.
When I copy that into the body from earlier, I get no errors and a working map. Which is odd. The php looks fine; I wouldn't use \r and \t at all (and you should try without them), but they're legal whitespace and should get ignored completely.
Perhaps it is a previously un-noticed parser error specific to Windows Dedicated Server?
From what I see I am one of the only ones who uses Windows for my "Dedicated" Server... (Not actually Dedicated simply a laptop(with dual core@2.13GHz and 4GB Ram) I leave on that runs other servers)
I use \r\n because while Linux Platforms place only \n in code... I use Windows... and I am Shallow Enough to want all my line breaks to look the same to anyone who knows how to view them...
I use \t purely for easier reading of the map file...
Well, I guess if you attach (not inline-quote) the map and possibly the script, any format errors would survive that. Or, attach the script. I don't think there can be special Windows parser errors, it's the same cross-platform library we're using.