I've run into a bit of a dead end on something. I have two servers, one development (Mac) and the other production (Linux), both running Silverstripe on Apache. On Linux, Firefox returns an XML Parsing Error on a number of my pages, but cannot specify where the error is.

It will say the error is located at Line 1, Column 1 and the error is: 208f (or some other hex value). I've attempted to remove the <?xml> header at the beginning of the Page.ss, however Firefox will still return the characters to the top of the screen as if it was part of the output.

Any thoughts would be greatly appreciated.

Kendall Buchanan

Thanks a lot for the response.

I really don't think so, because I can artificially create an unclosed tag error with the parser. On the development environment, it works perfectly given identical content on the page.

I can reproduce it by putting an anchor in the $Content section of a page that points to an outside URL on the production site.

If I turn off ContentNegotiation, it will just put a hex code at the top of the page, and a 0 at the bottom of the page. Is there a way this could be caused by Apache on the Linux box?

These issues are almost certainly related to the following (solved) ticked: http://open.silverstripe.com/ticket/2529

This will be fixed in the next release, but the actual solution is quite simple if you follow the instructions at the bottom.